asn.dev

Observed topology

AS197394 Telecommunications21century CJSC Telecommunications 21

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197394: 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 RostelecomResidentialIPv4778
AS3216PJSC "Vimpelcom"MobileIPv4213
AS31133PJSC MegaFonMobileIPv4174
AS24482SG.GSHostingIPv416
AS49673Truenetwork LLCUnclassifiedIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59418CJSC Telecommunications 21UnclassifiedIPv4126
AS50164PJSC TATNEFT N.A. V.D. SHASHINUnclassifiedIPv4124
AS43265RN Telecom Ltd.UnclassifiedIPv4118
AS28825CJSC Telekommunikacii 21UnclassifiedIPv463
AS198122Digital Technology Ltd.UnclassifiedIPv463
AS57011Information- Analytical Agency IF LTDUnclassifiedIPv461
AS48676LLC "Svyazenergo"UnclassifiedIPv425

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv41,407
AS3216PJSC "Vimpelcom"MobileIPv4580
AS28825CJSC Telekommunikacii 21UnclassifiedIPv4559
AS31133PJSC MegaFonMobileIPv4308
AS59418CJSC Telecommunications 21UnclassifiedIPv4126
AS50164PJSC TATNEFT N.A. V.D. SHASHINUnclassifiedIPv4124
AS57011Information- Analytical Agency IF LTDUnclassifiedIPv4123
AS43265RN Telecom Ltd.UnclassifiedIPv4118
AS198122Digital Technology Ltd.UnclassifiedIPv463
AS48676LLC "Svyazenergo"UnclassifiedIPv425

All 12 adjacent →

Provenance

Where this comes from

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