asn.dev

Observed topology

AS137263 NETEASE-AS-AP NETEASE HONG KONG LIMITED

Unclassified APNIC

Upstreams 13 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 4
Upstream graph Who carries AS137263, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS137263 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS137263: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv61,369
AS6939Hurricane Electric LLCTransitIPv4 IPv6403
AS136897Enjoyvc Cloud Group Limited.HostingIPv4357
AS21859Zenlayer IncHostingIPv4168
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv643
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv435
AS8359MTS PJSCMobileIPv431
AS9002RETN LimitedUnclassifiedIPv4 IPv628
AS17639Converge ICT Solutions Inc.UnclassifiedIPv412

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS137263 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

Every AS seen directly next to AS137263 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv61,369
AS6939Hurricane Electric LLCTransitIPv4 IPv6403
AS136897Enjoyvc Cloud Group Limited.HostingIPv4357
AS21859Zenlayer IncHostingIPv4168
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv643
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv435
AS8359MTS PJSCMobileIPv431
AS9002RETN LimitedUnclassifiedIPv4 IPv628
AS17639Converge ICT Solutions Inc.UnclassifiedIPv412

All 13 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.