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

AS149963 ·

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

Warning: AS149963 (XNETWORK-AS-ID) announces 2 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS149963
HolderXNETWORK-AS-ID - PT Layanan Internet Sakti
AllocationAPNIC, Indonesia (ID), allocated 2022-06-16
Prefixes (IPv4 / IPv6)2 / 0
RPKI valid50% (1 / 2)
Upstreams and peers2
Peering policyOpen

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

    1 of 2 announced prefixes have no ROA (RPKI not found): 202.47.89.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 AS149963 and a max length equal to the prefix length:

    202.47.89.0/24 AS149963 max-length /24

    Open in RPKI / ROA validator Guide

  3. 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

  4. 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 No IPv6 prefixes announced.
  • Pass: AS149963 announces 2 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 2 announced prefixes have no ROA (RPKI not found): 202.47.89.0/24.
  • Info: 1 of 2 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderXNETWORK-AS-ID - PT Layanan Internet Sakti
IPv4 prefixes2
IPv6 prefixes0
RPKI1 valid · 1 not found
Downstream networks0
Routes to fix
PrefixRPKI
202.47.89.0/24 No ROA

Upstreams and peers seen to the left 2

Announced prefixes 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.
NameXNETWORK-AS-ID
HandleAS149963
RangeAS149963
CountryID
Statusactive
Registered2022-08-22T02:56:25Z
Last changed2023-12-05T03:17:42Z
Abuse contactnoc@xnetwork.id
Allocation
Registry (RIR)APNIC
CountryIndonesia (ID)
Delegated on2022-06-16
StatusAllocated
Delegated rangeAS149877 – AS149976

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

Contacts
RoleNameEmail
technical, administrative Ronald Umar ronald@xnetwork.id
abuse IRT-XNET-ID noc@xnetwork.id

Source: https://rdap.apnic.net/autnum/149963. 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: AS149963 is in PeeringDB as PT Layanan Internet Sakti.
  • Info: Peering policy: Open.
  • Info: Present at 7 internet exchanges with 7 ports (34G in total).
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
NetworkPT Layanan Internet Sakti (xnet)
AS numberAS149963
Type, Asia Pacific
Websitehttps://xnetwork.net.id
Prefixes (IPv4 / IPv6)23 / 32
Traffic1-5Gbps, Balanced
Peering policyOpen
Policy URLhttps://xnetwork.net.id/contact
LocationsNot Required
Ratio requiredNo
ContractsPrivate Only
Last updated2025-07-11

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup