asn.dev

Observed topology

AS209141 CMI-Russia China Mobile International (Russia), LLC

Mobile ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209141: 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
AS31133PJSC MegaFonMobileIPv4155
AS6939Hurricane Electric LLCTransitIPv418
AS24482SG.GSHostingIPv4 IPv63
AS49673Truenetwork LLCUnclassifiedIPv42
AS25091IP-Max SAUnclassifiedIPv61
AS58453China Mobile International LimitedUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9198JSC KazakhtelecomUnclassifiedIPv47,671
AS61010IPNET OOOUnclassifiedIPv410

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv69,131
AS3216PJSC "Vimpelcom"MobileIPv4 IPv68,173
AS61010IPNET OOOUnclassifiedIPv41,292
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv61,291
AS34927iFog GmbHHostingIPv4957
AS31133PJSC MegaFonMobileIPv4155
AS6939Hurricane Electric LLCTransitIPv418
AS24482SG.GSHostingIPv4 IPv64
AS49673Truenetwork LLCUnclassifiedIPv43
AS25091IP-Max SAUnclassifiedIPv61

All 11 adjacent →

Provenance

Where this comes from

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