Observed topology

AS57214 VIDIKON

Unclassified RIPE

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57214: 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
AS58002	JSC Svyazinform	Unclassified	IPv4	602
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	356
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	330
AS50673	Serverius Holding B.V.	Unclassified	IPv4	32
AS24482	SG.GS	Hosting	IPv4	22
AS37721	Virtual Technologies & Solutions	Residential	IPv4	22
AS49673	Truenetwork LLC	Unclassified	IPv4	22

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS207284	Aspect LLC	Unclassified	IPv4	56

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS58002	JSC Svyazinform	Unclassified	IPv4	628
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	369
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	342
AS207284	Aspect LLC	Unclassified	IPv4	56
AS50673	Serverius Holding B.V.	Unclassified	IPv4	34
AS24482	SG.GS	Hosting	IPv4	23
AS37721	Virtual Technologies & Solutions	Residential	IPv4	23
AS49673	Truenetwork LLC	Unclassified	IPv4	23

Provenance

Where this comes from

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