Observed topology

AS213452 PIO LLC

Unclassified RIPE Enterprise

Upstreams 0 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 18

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS56634	Fly-Tech Ltd.	Unclassified	IPv4	271
AS214077	Limited Liability Company "Sumtel"	Unclassified	IPv4	130

Adjacency

Adjacent networks

All 18

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

AS	Network	Type	Families	Paths seen
AS56634	Fly-Tech Ltd.	Unclassified	IPv4	393
AS50509	Transroute Telecom LTD	Unclassified	IPv4	158
AS214077	Limited Liability Company "Sumtel"	Unclassified	IPv4	130
AS12389	PJSC Rostelecom	Residential	IPv4	91
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	86
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	65
AS6939	Hurricane Electric LLC	Transit	IPv4	29
AS8732	JSC Comcor	Unclassified	IPv4	25
AS9002	RETN Limited	Unclassified	IPv4	15
AS50673	Serverius Holding B.V.	Unclassified	IPv4	15

All 18 adjacent →

Provenance

Where this comes from

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