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

AS38506 ·

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

Warning: AS38506 (PIKANET-AS-ID) announces 15 IPv4 and 18 IPv6 prefixes. 3 warnings

AS pageAS38506
HolderPIKANET-AS-ID - PT Pika Media Komunika
AllocationAPNIC, Indonesia (ID), allocated 2007-03-28
Prefixes (IPv4 / IPv6)15 / 18
RPKI valid100% (33 / 33)
Upstreams and peers6
Peering policyOpen

What to fix

  1. Warning

    16 of 33 announced prefixes have no IRR route object: 2406:9300:2::/48, 2406:9300::/48, 2406:9300:1::/48, 2406:9300:f::/48, 2406:9300:5::/48 (+11).

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

    route6: 2406:9300:2::/48
    origin: AS38506
    
    route6: 2406:9300::/48
    origin: AS38506
    
    route6: 2406:9300:1::/48
    origin: AS38506

    Open in ASN & BGP prefix lookup

  2. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  3. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 16 of 33 announced prefixes have no IRR route object: 2406:9300:2::/48, 2406:9300::/48, 2406:9300:1::/48, 2406:9300:f::/48, 2406:9300:5::/48 (+11).
  • Pass: AS38506 announces 15 IPv4 and 18 IPv6 prefixes.
  • Pass: All 33 announced prefixes are RPKI valid.
  • Warning: 16 of 33 announced prefixes have no IRR route object: 2406:9300:2::/48, 2406:9300::/48, 2406:9300:1::/48, 2406:9300:f::/48, 2406:9300:5::/48 (+11).
  • Info: 6 upstreams and peers, 4 downstream networks seen.
HolderPIKANET-AS-ID - PT Pika Media Komunika
IPv4 prefixes15
IPv6 prefixes18
RPKI33 valid
Without IRR route object16
Downstream networks4

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.
NamePIKANET-AS-ID
HandleAS38506
RangeAS38506
CountryID
Statusactive
Registered2019-08-20T06:30:27Z
Last changed2016-10-17T00:31:15Z
Abuse contactabuse@idnic.net
Allocation
Registry (RIR)APNIC
CountryIndonesia (ID)
Delegated on2007-03-28
StatusAllocated
Delegated rangeAS38496 – AS38527

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

Contacts
RoleNameEmail
technical, administrative R Made Widyastono madewidya@pika.net.id
abuse IRT-IDNIC-ID abuse@idnic.net

Source: https://rdap.apnic.net/autnum/38506. 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 No IRR as-set is listed.
  • Pass: AS38506 is in PeeringDB as PT. Pika Media Komunika.
  • Info: Peering policy: Open.
  • Info: Present at 4 internet exchanges with 4 ports (31G in total).
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2024-09-26.
NetworkPT. Pika Media Komunika (Pikanet)
AS numberAS38506
TypeCable/DSL/ISP, Regional
Websitehttp://www.pika.net.id
Prefixes (IPv4 / IPv6)16 / 1
Traffic1-5Gbps, Heavy Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-09-26

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup