asn.dev

Observed topology

AS9231 IPEOPLESNET-AS-AP China Mobile Hong Kong Company Limited

Mobile APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9231: 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.TransitIPv42,235
AS58453China Mobile International LimitedUnclassifiedIPv4742
AS6939Hurricane Electric LLCTransitIPv4686
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4132
AS24482SG.GSHostingIPv470
AS38001NewMedia Express Pte LtdHostingIPv462
AS132132MyRepublic Ltd.ResidentialIPv462
AS7473Singapore Telecommunications LtdUnclassifiedIPv48
AS17639Converge ICT Solutions Inc.UnclassifiedIPv48
AS33891Core-Backbone GmbHHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS137872China Mobile Hong Kong Company LimitedUnclassifiedIPv44,861

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv45,583
AS137872China Mobile Hong Kong Company LimitedUnclassifiedIPv44,861
AS6939Hurricane Electric LLCTransitIPv41,649
AS58453China Mobile International LimitedUnclassifiedIPv4742
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4267
AS24482SG.GSHostingIPv4182
AS132132MyRepublic Ltd.ResidentialIPv4172
AS38001NewMedia Express Pte LtdHostingIPv4149
AS17639Converge ICT Solutions Inc.UnclassifiedIPv484
AS9002RETN LimitedUnclassifiedIPv430

All 12 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.