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

AS137375 · 

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

Warning: AS137375 (ISP-NET-AS-ID) announces 3 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS137375
HolderISP-NET-AS-ID - PT Internet Solusi Prima
AllocationAPNIC, Indonesia (ID), allocated 2018-01-03
Prefixes (IPv4 / IPv6)3 / 0
RPKI valid0% (0 / 3)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    3 of 3 announced prefixes have no ROA (RPKI not found): 103.118.184.0/22, 103.118.185.0/24, 103.118.187.0/24.

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

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

    103.118.184.0/22 AS137375 max-length /22
103.118.185.0/24 AS137375 max-length /24
103.118.187.0/24 AS137375 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 3 announced prefixes have no IRR route object: 103.118.187.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 AS137375 in your RIR’s IRR database (or RADB).

    route: 103.118.187.0/24
origin: AS137375

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS137375 announces 3 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 103.118.184.0/22, 103.118.185.0/24, 103.118.187.0/24.
  • Warning: 1 of 3 announced prefixes have no IRR route object: 103.118.187.0/24.
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderISP-NET-AS-ID - PT Internet Solusi Prima
IPv4 prefixes3
IPv6 prefixes0
RPKI3 not found
Without IRR route object1
Downstream networks1
Routes to fix
PrefixRPKI
103.118.184.0/22 No ROA
103.118.185.0/24 No ROA
103.118.187.0/24 No ROA

Upstreams and peers seen to the left 2

AS4787 CBN Internet AS7713 Telekomunikasi Indonesia Int (TELIN)

Announced prefixes 3

103.118.184.0/22 103.118.185.0/24 103.118.187.0/24

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.
NameISP-NET-AS-ID
HandleAS137375
RangeAS137375
CountryID
Statusactive
Registered2019-08-20T06:30:39Z
Last changed2018-08-23T18:25:14Z
Abuse contactinfo@isp.net.id
Allocation
Registry (RIR)APNIC
CountryIndonesia (ID)
Delegated on2018-01-03
StatusAllocated
Delegated rangeAS137359 – AS137384

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

Contacts
RoleNameEmail
abuse IRT-ISP-ID info@isp.net.id
technical, administrative Djainal Djainal abuse@isp.net.id

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