asn.dev

Observed topology

AS204297 BSTK-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204297: 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 RostelecomResidentialIPv487
AS31500Global Network Management IncUnclassifiedIPv439
AS20485Joint Stock Company TransTeleComUnclassifiedIPv426
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv413
AS31133PJSC MegaFonMobileIPv46
AS58002JSC SvyazinformUnclassifiedIPv46
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv43

Transit

Downstream networks

inferred

Networks for which AS204297 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv487
AS31500Global Network Management IncUnclassifiedIPv439
AS20485Joint Stock Company TransTeleComUnclassifiedIPv426
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv413
AS31133PJSC MegaFonMobileIPv46
AS58002JSC SvyazinformUnclassifiedIPv46
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv43

Provenance

Where this comes from

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