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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS137263 (NETEASE-AS-AP) announces 43 IPv4 and 1 IPv6 prefixes. 3 warnings
| AS page | AS137263 |
|---|---|
| Holder | NETEASE-AS-AP - NETEASE HONG KONG LIMITED |
| Allocation | APNIC, Hong Kong SAR China (HK), allocated 2017-12-21 |
| Prefixes (IPv4 / IPv6) | 43 / 1 |
| RPKI valid | 95% (42 / 44) |
| Upstreams and peers | 16 |
| Peering policy | Open |
What to fix
-
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
-
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.
-
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.
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.
| Holder | NETEASE-AS-AP - NETEASE HONG KONG LIMITED |
|---|---|
| IPv4 prefixes | 43 |
| IPv6 prefixes | 1 |
| RPKI | 42 valid · 2 not found |
| Downstream networks | 0 |
| Prefix | RPKI |
|---|---|
| 154.18.236.0/24 | No ROA |
| 154.18.237.0/24 | No ROA |
Upstreams and peers seen to the left 16
Announced prefixes 44
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.apnic.net.
- Pass: Found at rdap.apnic.net.
| Name | NETEASE-AS-AP |
|---|---|
| Handle | AS137263 |
| Range | AS137263 |
| Country | HK |
| Status | active |
| Registered | 2017-12-20T23:32:34Z |
| Last changed | 2020-11-18T13:06:36Z |
| Abuse contact | noc@service.netease.com |
| Registry (RIR) | APNIC |
|---|---|
| Country | Hong Kong SAR China (HK) |
| Delegated on | 2017-12-21 |
| Status | Allocated |
| Delegated range | AS137263 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| 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 lookupPeeringDB 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.
| Network | NETEASE |
|---|---|
| AS number | AS137263 |
| Type | , Global |
| Website | https://www.netease.com/ |
| Prefixes (IPv4 / IPv6) | 1000 / 50 |
| Traffic | 100-200Gbps, Mostly Inbound |
| Peering policy | Open |
| Locations | Preferred |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2025-09-05 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup