asn.dev

Observed topology

AS20485 TRANSTELECOM Moscow, Russia

Unclassified RIPE NSP

Upstreams 31 carry this network
Downstreams 1,788 this network carries
Adjacent (IPv4) 1,863
Adjacent (IPv6) 124
Upstream graph Who carries AS20485, and who carries them, drawn as a map up to the transit-free core. 9 exchanges Where AS20485 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS20485: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,451
AS6939Hurricane Electric LLCTransitIPv4 IPv6527
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6514
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4429
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6256
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6172
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv687
AS24482SG.GSHostingIPv4 IPv687
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv687
AS42708Glesys ABUnclassifiedIPv4 IPv687

All 31 upstreams →

Transit

Downstream networks

All 1,788

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

ASNetworkTypeFamiliesPaths seen
AS15774Limited Liability Company "TTK-Svyaz"UnclassifiedIPv4 IPv620,660
AS47241Joint Stock Company TransTeleComUnclassifiedIPv412,803
AS16509Amazon.com, Inc.HostingIPv45,826
AS7713PT Telekomunikasi IndonesiaResidentialIPv43,490
AS21191Joint Stock Company TransTeleComUnclassifiedIPv4 IPv63,433
AS196797Joint Stock Company TransTeleComUnclassifiedIPv43,363
AS21127Joint Stock Company TransTeleComUnclassifiedIPv4 IPv63,159
AS28745Joint Stock Company TransTeleComUnclassifiedIPv4 IPv63,136
AS49505JSC SelectelHostingIPv43,098
AS50340JSC SelectelHostingIPv43,041

All 1,788 downstreams →

Adjacency

Adjacent networks

All 1,863

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

ASNetworkTypeFamiliesPaths seen
AS49673Truenetwork LLCUnclassifiedIPv4691,491
AS1299Arelion Sweden ABTransitIPv4 IPv6309,309
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv478,865
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv456,564
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv653,829
AS58453China Mobile International LimitedUnclassifiedIPv431,539
AS6461Zayo BandwidthTransitIPv429,232
AS15774Limited Liability Company "TTK-Svyaz"UnclassifiedIPv4 IPv623,301
AS4134No.31,Jin-rong StreetResidentialIPv420,762
AS35168TNS-Plus LLPUnclassifiedIPv4 IPv618,720

All 1,863 adjacent →

Provenance

Where this comes from

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