Observed topology

AS197482 DGIS

Hosting RIPE

Upstreams 12 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 12

Adjacent (IPv6) 0

Upstream graph Who carries AS197482, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS197482 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS197482: 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.

AS	Network	Type	Families	Paths seen
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	116
AS9002	RETN Limited	Unclassified	IPv4	98
AS12389	PJSC Rostelecom	Residential	IPv4	64
AS20764	CJSC RASCOM	Unclassified	IPv4	39
AS57304	JSC "RetnNet"	Unclassified	IPv4	35
AS6939	Hurricane Electric LLC	Transit	IPv4	33
AS2854	LLC Orange Business Services	Unclassified	IPv4	20
AS50928	PJSC MegaFon	Unclassified	IPv4	5
AS13094	JSC "ER-Telecom Holding"	Unclassified	IPv4	4
AS25159	PJSC MegaFon	Unclassified	IPv4	4

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS197482 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 12

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

AS	Network	Type	Families	Paths seen
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	116
AS9002	RETN Limited	Unclassified	IPv4	98
AS12389	PJSC Rostelecom	Residential	IPv4	64
AS20764	CJSC RASCOM	Unclassified	IPv4	39
AS57304	JSC "RetnNet"	Unclassified	IPv4	35
AS6939	Hurricane Electric LLC	Transit	IPv4	33
AS2854	LLC Orange Business Services	Unclassified	IPv4	20
AS50928	PJSC MegaFon	Unclassified	IPv4	5
AS13094	JSC "ER-Telecom Holding"	Unclassified	IPv4	4
AS25159	PJSC MegaFon	Unclassified	IPv4	4

All 12 adjacent →

Provenance

Where this comes from

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