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

AS17564 ·

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

Warning: AS17564 (GITN-PCN-AS-AP) announces 11 IPv4 and 6 IPv6 prefixes. 3 warnings

AS pageAS17564
HolderGITN-PCN-AS-AP - GITN (M) Sdn. Bhd.
AllocationAPNIC, Malaysia (MY), allocated 2006-01-04
Prefixes (IPv4 / IPv6)11 / 6
RPKI valid0% (0 / 17)
Upstreams and peers2

What to fix

  1. Warning

    10 of 17 announced prefixes have no ROA (RPKI not found): 103.8.144.0/23, 103.8.144.0/24, 103.8.145.0/24, 103.8.147.0/24, 103.8.160.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 AS17564 and a max length equal to the prefix length:

    103.8.144.0/23 AS17564 max-length /23
    103.8.144.0/24 AS17564 max-length /24
    103.8.145.0/24 AS17564 max-length /24
    103.8.147.0/24 AS17564 max-length /24
    103.8.160.0/22 AS17564 max-length /22
    150.242.180.0/23 AS17564 max-length /23
    150.242.182.0/23 AS17564 max-length /23
    163.53.152.0/23 AS17564 max-length /23
    163.53.154.0/24 AS17564 max-length /24
    202.75.4.0/22 AS17564 max-length /22

    Open in RPKI / ROA validator Guide

  2. Warning

    6 of 17 announced prefixes have no IRR route object: 2401:b00:800::/37, 2401:b00:11::/48, 2400:e800:1000::/36, 103.8.160.0/22, 2401:b00::/37 (+1).

    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 AS17564 in your RIR’s IRR database (or RADB).

    route6: 2401:b00:800::/37
    origin: AS17564
    
    route6: 2401:b00:11::/48
    origin: AS17564
    
    route6: 2400:e800:1000::/36
    origin: AS17564

    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 17 announced prefixes have no ROA (RPKI not found): 103.8.144.0/23, 103.8.144.0/24, 103.8.145.0/24, 103.8.147.0/24, 103.8.160.0/22 (+5).
  • Pass: AS17564 announces 11 IPv4 and 6 IPv6 prefixes.
  • Warning: 10 of 17 announced prefixes have no ROA (RPKI not found): 103.8.144.0/23, 103.8.144.0/24, 103.8.145.0/24, 103.8.147.0/24, 103.8.160.0/22 (+5).
  • Info: The RPKI state of 7 prefixes was not looked up (no ROA of AS17564 covers them; only the first 10 are checked).
  • Warning: 6 of 17 announced prefixes have no IRR route object: 2401:b00:800::/37, 2401:b00:11::/48, 2400:e800:1000::/36, 103.8.160.0/22, 2401:b00::/37 (+1).
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderGITN-PCN-AS-AP - GITN (M) Sdn. Bhd.
IPv4 prefixes11
IPv6 prefixes6
RPKI10 not found · 7 not looked up
Without IRR route object6
Downstream networks0
Routes to fix

Upstreams and peers seen to the left 2

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-PCN-AS-AP
HandleAS17564
RangeAS17564
CountryMY
Statusactive
Registered2008-09-04T06:40:39Z
Last changed2021-01-12T22:45:31Z
Abuse contactgitn.pcn@tm.com.my
Allocation
Registry (RIR)APNIC
CountryMalaysia (MY)
Delegated on2006-01-04
StatusAllocated
Delegated rangeAS17564

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

Contacts
RoleNameEmail
registrant GITN Sdn. Bhd. gitn.pcn@tm.com.my
technical Mohd Ridhauddin Amin ridhauddin@gitn.com.my
abuse IRT-GITN-PCN-MY gitn.pcn@tm.com.my
technical Efdza Nizam Hamzah efdza@maxipacific.com
administrative Sapuan Somo sapuan@gitn.com.my

Source: https://rdap.apnic.net/autnum/17564. 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