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

AS38153 · 

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

Warning: AS38153 (UPH-AS-ID) announces 16 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS38153
HolderUPH-AS-ID - Universitas Pelita Harapan
AllocationAPNIC, Indonesia (ID), allocated 2006-07-12
Prefixes (IPv4 / IPv6)16 / 0
RPKI valid0% (0 / 16)
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

    10 of 16 announced prefixes have no ROA (RPKI not found): 122.200.0.0/24, 122.200.1.0/24, 122.200.2.0/24, 122.200.3.0/24, 122.200.4.0/24 (+5).

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

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

    122.200.0.0/24 AS38153 max-length /24
122.200.1.0/24 AS38153 max-length /24
122.200.2.0/24 AS38153 max-length /24
122.200.3.0/24 AS38153 max-length /24
122.200.4.0/24 AS38153 max-length /24
122.200.5.0/24 AS38153 max-length /24
122.200.6.0/24 AS38153 max-length /24
122.200.7.0/24 AS38153 max-length /24
122.200.8.0/24 AS38153 max-length /24
122.200.9.0/24 AS38153 max-length /24

    Open in RPKI / ROA validator Guide

  3. 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: AS38153 announces 16 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 16 announced prefixes have no ROA (RPKI not found): 122.200.0.0/24, 122.200.1.0/24, 122.200.2.0/24, 122.200.3.0/24, 122.200.4.0/24 (+5).
  • Info: The RPKI state of 6 prefixes was not looked up (no ROA of AS38153 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderUPH-AS-ID - Universitas Pelita Harapan
IPv4 prefixes16
IPv6 prefixes0
RPKI10 not found · 6 not looked up
Downstream networks0
Routes to fix
PrefixRPKI
122.200.0.0/24 No ROA
122.200.1.0/24 No ROA
122.200.2.0/24 No ROA
122.200.3.0/24 No ROA
122.200.4.0/24 No ROA
122.200.5.0/24 No ROA
122.200.6.0/24 No ROA
122.200.7.0/24 No ROA
122.200.8.0/24 No ROA
122.200.9.0/24 No ROA

Upstreams and peers seen to the left 2

AS9905 LINKNET-ID-AP AS4761 Indosat Ooredoo

Announced prefixes 16

122.200.0.0/24 122.200.1.0/24 122.200.2.0/24 122.200.3.0/24 122.200.4.0/24 122.200.5.0/24 122.200.6.0/24 122.200.7.0/24 122.200.8.0/24 122.200.9.0/24 122.200.10.0/24 122.200.11.0/24 122.200.12.0/24 122.200.13.0/24 122.200.14.0/24 122.200.15.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.
NameUPH-AS-ID
HandleAS38153
RangeAS38153
CountryID
Statusactive
Registered2019-08-20T06:30:27Z
Last changed2021-07-14T08:57:08Z
Abuse contactabuse@idnic.net
Allocation
Registry (RIR)APNIC
CountryIndonesia (ID)
Delegated on2006-07-12
StatusAllocated
Delegated rangeAS38141 – AS38165

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

Contacts
RoleNameEmail
technical Johanes Surjadi Johanes.surjadi@uph.edu
administrative Tommy Surya infrauph@uph.edu
technical Norbertus Yunendra Liceabilling@uph.edu
abuse IRT-IDNIC-ID abuse@idnic.net

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