asn.dev

Observed topology

AS57629 IVI-RU LLC IVI.RU

Hosting RIPE Content

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

Transit

Upstream networks

All 32

Networks observed carrying traffic for AS57629: 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
AS12389PJSC RostelecomResidentialIPv4 IPv6424
AS31133PJSC MegaFonMobileIPv4 IPv6295
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6261
AS8359MTS PJSCMobileIPv4 IPv6141
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6128
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv692
AS197068HLL LLCHostingIPv460
AS12494OOO "Post ltd"UnclassifiedIPv636
AS41704JSC "Ufanet"UnclassifiedIPv636
AS47165Omskie kabelnye seti Ltd.UnclassifiedIPv636

All 32 upstreams →

Transit

Downstream networks

inferred

Networks for which AS57629 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 32

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6424
AS31133PJSC MegaFonMobileIPv4 IPv6295
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6261
AS8359MTS PJSCMobileIPv4 IPv6141
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6128
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv692
AS197068HLL LLCHostingIPv460
AS12494OOO "Post ltd"UnclassifiedIPv636
AS41704JSC "Ufanet"UnclassifiedIPv636
AS47165Omskie kabelnye seti Ltd.UnclassifiedIPv636

All 32 adjacent →

Provenance

Where this comes from

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