asn.dev

Observed topology

AS28709 VKONTAKTE-REGIONAL-CDN Regional CDN vk.com

Unclassified RIPE

Upstreams 9 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 4
Upstream graph Who carries AS28709, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS28709 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28709: 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 IPv6845
AS31133PJSC MegaFonMobileIPv4 IPv691
AS3216PJSC "Vimpelcom"MobileIPv4 IPv679
AS8359MTS PJSCMobileIPv418
AS49673Truenetwork LLCUnclassifiedIPv412
AS20485Joint Stock Company TransTeleComUnclassifiedIPv49
AS9002RETN LimitedUnclassifiedIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS57304JSC "RetnNet"UnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57973LLC VKUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6845
AS31133PJSC MegaFonMobileIPv4 IPv692
AS3216PJSC "Vimpelcom"MobileIPv4 IPv679
AS8359MTS PJSCMobileIPv418
AS49673Truenetwork LLCUnclassifiedIPv413
AS20485Joint Stock Company TransTeleComUnclassifiedIPv49
AS9002RETN LimitedUnclassifiedIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS57304JSC "RetnNet"UnclassifiedIPv43
AS57973LLC VKUnclassifiedIPv42

Provenance

Where this comes from

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