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

AS137263 ·

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

Warning: AS137263 (NETEASE-AS-AP) announces 43 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS137263
HolderNETEASE-AS-AP - NETEASE HONG KONG LIMITED
AllocationAPNIC, Hong Kong SAR China (HK), allocated 2017-12-21
Prefixes (IPv4 / IPv6)43 / 1
RPKI valid95% (42 / 44)
Upstreams and peers16
Peering policyOpen

What to fix

  1. Warning

    2 of 44 announced prefixes have no ROA (RPKI not found): 154.18.236.0/24, 154.18.237.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 AS137263 and a max length equal to the prefix length:

    154.18.236.0/24 AS137263 max-length /24
    154.18.237.0/24 AS137263 max-length /24

    Open in RPKI / ROA validator Guide

  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 2 of 44 announced prefixes have no ROA (RPKI not found): 154.18.236.0/24, 154.18.237.0/24.
  • Pass: AS137263 announces 43 IPv4 and 1 IPv6 prefixes.
  • Warning: 2 of 44 announced prefixes have no ROA (RPKI not found): 154.18.236.0/24, 154.18.237.0/24.
  • Info: 42 of 44 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 16 upstreams and peers, 0 downstream networks seen.
HolderNETEASE-AS-AP - NETEASE HONG KONG LIMITED
IPv4 prefixes43
IPv6 prefixes1
RPKI42 valid · 2 not found
Downstream networks0
Routes to fix
PrefixRPKI
154.18.236.0/24 No ROA
154.18.237.0/24 No ROA

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.
NameNETEASE-AS-AP
HandleAS137263
RangeAS137263
CountryHK
Statusactive
Registered2017-12-20T23:32:34Z
Last changed2020-11-18T13:06:36Z
Abuse contactnoc@service.netease.com
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on2017-12-21
StatusAllocated
Delegated rangeAS137263

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

Contacts
RoleNameEmail
registrant NETEASE (HONG KONG) LIMITED sa@corp.netease.com
administrative, technical NETEASE HONG KONG LIMITED administrator noc@service.netease.com
abuse IRT-NETEASE-HK noc@service.netease.com

Source: https://rdap.apnic.net/autnum/137263. 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: AS137263 is in PeeringDB as NETEASE.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 4 ports (220G in total).
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
NetworkNETEASE
AS numberAS137263
Type, Global
Websitehttps://www.netease.com/
Prefixes (IPv4 / IPv6)1000 / 50
Traffic100-200Gbps, Mostly Inbound
Peering policyOpen
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Last updated2025-09-05

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup