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

AS9906 · 

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

Warning: AS9906 (ETNET-HK-AP) announces 12 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS9906
HolderETNET-HK-AP - ETNet Limited
AllocationAPNIC, Hong Kong SAR China (HK), allocated 2000-03-17
Prefixes (IPv4 / IPv6)12 / 0
RPKI valid0% (0 / 12)
Upstreams and peers1

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 12 announced prefixes have no ROA (RPKI not found): 202.62.192.0/24, 202.62.194.0/24, 202.62.195.0/24, 202.62.200.0/24, 202.62.215.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 AS9906 and a max length equal to the prefix length:

    202.62.192.0/24 AS9906 max-length /24
202.62.194.0/24 AS9906 max-length /24
202.62.195.0/24 AS9906 max-length /24
202.62.200.0/24 AS9906 max-length /24
202.62.215.0/24 AS9906 max-length /24
202.62.216.0/24 AS9906 max-length /24
202.62.217.0/24 AS9906 max-length /24
202.62.218.0/24 AS9906 max-length /24
202.62.219.0/24 AS9906 max-length /24
202.62.220.0/24 AS9906 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: AS9906 announces 12 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 12 announced prefixes have no ROA (RPKI not found): 202.62.192.0/24, 202.62.194.0/24, 202.62.195.0/24, 202.62.200.0/24, 202.62.215.0/24 (+5).
  • Info: The RPKI state of 2 prefixes was not looked up (no ROA of AS9906 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS4515): an outage there takes the whole network off the internet.
HolderETNET-HK-AP - ETNet Limited
IPv4 prefixes12
IPv6 prefixes0
RPKI10 not found · 2 not looked up
Downstream networks0
Routes to fix
PrefixRPKI
202.62.192.0/24 No ROA
202.62.194.0/24 No ROA
202.62.195.0/24 No ROA
202.62.200.0/24 No ROA
202.62.215.0/24 No ROA
202.62.216.0/24 No ROA
202.62.217.0/24 No ROA
202.62.218.0/24 No ROA
202.62.219.0/24 No ROA
202.62.220.0/24 No ROA

Upstreams and peers seen to the left 1

AS4515 PCCW IMS

Announced prefixes 12

202.62.192.0/24 202.62.194.0/24 202.62.195.0/24 202.62.200.0/24 202.62.215.0/24 202.62.216.0/24 202.62.217.0/24 202.62.218.0/24 202.62.219.0/24 202.62.220.0/24 202.62.221.0/24 202.62.222.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.
NameETNET-HK-AP
HandleAS9906
RangeAS9906
CountryHK
Statusactive
Registered2008-09-04T06:40:28Z
Last changed2020-07-08T02:03:36Z
Abuse contactrogerwong@etnet.com.hk
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on2000-03-17
StatusAllocated
Delegated rangeAS9906

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

Contacts
RoleNameEmail
administrative, technical Roger Wong rogerwong@etnet.com.hk
abuse IRT-ETNET-HK rogerwong@etnet.com.hk
registrant ETNet Ltd dchoi@etnet.com.hk

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