Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS38044 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS38044"
JSON Docs

Warning: AS38044 (GITN-NETWORK) announces 10 IPv4 and 2 IPv6 prefixes. 3 warnings

AS pageAS38044
HolderGITN-NETWORK - GITN-NETWORK
AllocationAPNIC, Malaysia (MY), allocated 2006-05-31
Prefixes (IPv4 / IPv6)10 / 2
RPKI valid0% (0 / 12)
Upstreams and peers1

What to fix

  1. Warning

    10 of 12 announced prefixes have no ROA (RPKI not found): 43.252.232.0/22, 43.252.233.0/24, 43.252.235.0/24, 103.245.88.0/22, 175.28.12.0/22 (+5).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS38044 and a max length equal to the prefix length:

    43.252.232.0/22 AS38044 max-length /22
43.252.233.0/24 AS38044 max-length /24
43.252.235.0/24 AS38044 max-length /24
103.245.88.0/22 AS38044 max-length /22
175.28.12.0/22 AS38044 max-length /22
202.60.56.0/22 AS38044 max-length /22
202.60.57.0/24 AS38044 max-length /24
202.60.59.0/24 AS38044 max-length /24
203.12.220.0/24 AS38044 max-length /24
203.62.1.0/24 AS38044 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    4 of 12 announced prefixes have no IRR route object: 2400:7400:8000::/33, 2400:7400::/33, 202.60.57.0/24, 202.60.59.0/24.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS38044 in your RIR’s IRR database (or RADB).

    route6: 2400:7400:8000::/33
origin: AS38044

route6: 2400:7400::/33
origin: AS38044

route: 202.60.57.0/24
origin: AS38044

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 12 announced prefixes have no ROA (RPKI not found): 43.252.232.0/22, 43.252.233.0/24, 43.252.235.0/24, 103.245.88.0/22, 175.28.12.0/22 (+5).
  • Pass: AS38044 announces 10 IPv4 and 2 IPv6 prefixes.
  • Warning: 10 of 12 announced prefixes have no ROA (RPKI not found): 43.252.232.0/22, 43.252.233.0/24, 43.252.235.0/24, 103.245.88.0/22, 175.28.12.0/22 (+5).
  • Info: The RPKI state of 2 prefixes was not looked up (no ROA of AS38044 covers them; only the first 10 are checked).
  • Warning: 4 of 12 announced prefixes have no IRR route object: 2400:7400:8000::/33, 2400:7400::/33, 202.60.57.0/24, 202.60.59.0/24.
  • Info: One upstream or peer seen (AS4788): an outage there takes the whole network off the internet.
HolderGITN-NETWORK - GITN-NETWORK
IPv4 prefixes10
IPv6 prefixes2
RPKI10 not found · 2 not looked up
Without IRR route object4
Downstream networks1
Routes to fix
PrefixRPKI
43.252.232.0/22 No ROA
43.252.233.0/24 No ROA
43.252.235.0/24 No ROA
103.245.88.0/22 No ROA
175.28.12.0/22 No ROA
202.60.56.0/22 No ROA
202.60.57.0/24 No ROA
202.60.59.0/24 No ROA
203.12.220.0/24 No ROA
203.62.1.0/24 No ROA

Upstreams and peers seen to the left 1

AS4788 Telekom Malaysia Berhad (TM)

Announced prefixes 12

43.252.232.0/22 43.252.233.0/24 43.252.235.0/24 103.245.88.0/22 175.28.12.0/22 202.60.56.0/22 202.60.57.0/24 202.60.59.0/24 203.12.220.0/24 203.62.1.0/24 2400:7400:8000::/33 2400:7400::/33

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameGITN-NETWORK
HandleAS38044
RangeAS38044
CountryMY
Statusactive
Registered2008-09-04T06:40:39Z
Last changed2021-01-18T03:49:23Z
Abuse contactplanning@gitn.com.my
Allocation
Registry (RIR)APNIC
CountryMalaysia (MY)
Delegated on2006-05-31
StatusAllocated
Delegated rangeAS38044

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
administrative, technical Mohd Hafizul Hasnan hafizul@gitn.com.my
abuse IRT-GITN-MY planning@gitn.com.my
registrant GITN-SCHOOLNET planning@gitn.com.my
technical Muhammad Romdzi Ahamed Rahimi romdzi@gitn.com.my

Source: https://rdap.apnic.net/autnum/38044. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup