Observed topology

AS58084 NEWCONTACT-AS

Unclassified RIPE

Upstreams 10 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58084: 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
AS57304	JSC "RetnNet"	Unclassified	IPv4	90
AS49063	Data Storage Center JSC	Unclassified	IPv4	79
AS15974	Joint Stock Company TransTeleCom	Unclassified	IPv4	64
AS20632	PJSC MegaFon	Unclassified	IPv4	52
AS35177	PJSC Rostelecom	Unclassified	IPv4	29
AS39442	JSC RDE "Unico"	Unclassified	IPv4	27
AS31261	PJSC MegaFon	Unclassified	IPv4	10
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	7
AS8359	MTS PJSC	Mobile	IPv4	4
AS9002	RETN Limited	Unclassified	IPv4	3

Transit

Downstream networks

inferred

Networks for which AS58084 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 AS58084 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS57304	JSC "RetnNet"	Unclassified	IPv4	90
AS49063	Data Storage Center JSC	Unclassified	IPv4	79
AS15974	Joint Stock Company TransTeleCom	Unclassified	IPv4	64
AS20632	PJSC MegaFon	Unclassified	IPv4	52
AS35177	PJSC Rostelecom	Unclassified	IPv4	29
AS39442	JSC RDE "Unico"	Unclassified	IPv4	27
AS31261	PJSC MegaFon	Unclassified	IPv4	10
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	7
AS8359	MTS PJSC	Mobile	IPv4	4
AS9002	RETN Limited	Unclassified	IPv4	3

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.