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

AS38144 ·

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

Warning: AS38144 (JALAWAVE-AS-ID) announces 44 IPv4 and 0 IPv6 prefixes. 2 warnings

AS pageAS38144
HolderJALAWAVE-AS-ID - PT Jalawave Cakrawala
AllocationAPNIC, Indonesia (ID), allocated 2006-07-12
Prefixes (IPv4 / IPv6)44 / 0
RPKI valid100% (44 / 44)
Upstreams and peers3

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

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameJALAWAVE-AS-ID
HandleAS38144
RangeAS38144
CountryID
Statusactive
Registered2019-08-20T06:30:27Z
Last changed2025-12-28T00:25:13Z
Abuse contacthostmaster@jalawave.net.id
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, administrative Hostmaster Jalawave hostmaster@jalawave.net.id
abuse IRT-JALAWAVE-ID hostmaster@jalawave.net.id

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