asn.dev

Observed topology

AS207978 KSC-SB-RAS-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207978: 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
AS33991IGRA-SERVICE LLCUnclassifiedIPv430
AS3216PJSC "Vimpelcom"MobileIPv429
AS44206Sibirskie Seti Ltd.UnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12828Federal State Budgetary Scientific Institution "Federal Research Center "Krasnoyarsk Scientific Center of the Siberian Branch of the Russian Academy of Sciences"UnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12828Federal State Budgetary Scientific Institution "Federal Research Center "Krasnoyarsk Scientific Center of the Siberian Branch of the Russian Academy of Sciences"UnclassifiedIPv463
AS33991IGRA-SERVICE LLCUnclassifiedIPv460
AS3216PJSC "Vimpelcom"MobileIPv458
AS44206Sibirskie Seti Ltd.UnclassifiedIPv48

Provenance

Where this comes from

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