asn.dev

Observed topology

AS47541 VKONTAKTE-SPB-AS vk.com

Hosting RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS47541: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6447
AS12389PJSC RostelecomResidentialIPv4 IPv6427
AS31133PJSC MegaFonMobileIPv4 IPv6322
AS6939Hurricane Electric LLCTransitIPv468
AS60476Digital Transformation Plus LLCUnclassifiedIPv452
AS50673Serverius Holding B.V.UnclassifiedIPv433
AS24482SG.GSHostingIPv4 IPv627
AS9002RETN LimitedUnclassifiedIPv421
AS37721Virtual-Technologies-Solutions-SAResidentialIPv421
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv421

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207581LLC VKUnclassifiedIPv4124
AS62243LLC VKUnclassifiedIPv462
AS57973LLC VKUnclassifiedIPv41

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6551
AS1299Arelion Sweden ABTransitIPv4 IPv6514
AS31133PJSC MegaFonMobileIPv4 IPv6322
AS207581LLC VKUnclassifiedIPv4124
AS6939Hurricane Electric LLCTransitIPv468
AS62243LLC VKUnclassifiedIPv462
AS60476Digital Transformation Plus LLCUnclassifiedIPv452
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv640
AS24482SG.GSHostingIPv4 IPv630
AS47764LLC VKHostingIPv629

All 19 adjacent →

Provenance

Where this comes from

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