asn.dev

Observed topology

AS205638 TM-AS-MSK

Unclassified RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS205638: 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
AS12389PJSC RostelecomResidentialIPv4262
AS29076Citytelecom LLCHostingIPv4244
AS1299Arelion Sweden ABTransitIPv4196
AS31133PJSC MegaFonMobileIPv4176
AS31500Global Network Management IncUnclassifiedIPv4128
AS20764CJSC RASCOMUnclassifiedIPv4113
AS6939Hurricane Electric LLCTransitIPv450
AS3216PJSC "Vimpelcom"MobileIPv446
AS8359MTS PJSCMobileIPv424
AS24482SG.GSHostingIPv415

All 19 upstreams →

Transit

Downstream networks

inferred

Networks for which AS205638 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 19

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4262
AS29076Citytelecom LLCHostingIPv4244
AS1299Arelion Sweden ABTransitIPv4196
AS31133PJSC MegaFonMobileIPv4176
AS31500Global Network Management IncUnclassifiedIPv4128
AS20764CJSC RASCOMUnclassifiedIPv4113
AS6939Hurricane Electric LLCTransitIPv450
AS3216PJSC "Vimpelcom"MobileIPv446
AS8359MTS PJSCMobileIPv424
AS24482SG.GSHostingIPv415

All 19 adjacent →

Provenance

Where this comes from

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