asn.dev

Observed topology

AS57073 WILDBERRIES-AS

Unclassified APNIC

Upstreams 20 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 20
Adjacent (IPv6) 13
Upstream graph Who carries AS57073, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS57073 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS57073: 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 IPv6268
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6219
AS1299Arelion Sweden ABTransitIPv4 IPv6163
AS31500Global Network Management IncUnclassifiedIPv4 IPv6138
AS8359MTS PJSCMobileIPv4 IPv698
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv688
AS3216PJSC "Vimpelcom"MobileIPv4 IPv683
AS31133PJSC MegaFonMobileIPv4 IPv668
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv666
AS24482SG.GSHostingIPv4 IPv623

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213105LLC WildberriesUnclassifiedIPv463
AS33902ePharmacy LLCUnclassifiedIPv462

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6326
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6219
AS1299Arelion Sweden ABTransitIPv4 IPv6163
AS31500Global Network Management IncUnclassifiedIPv4 IPv6153
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6104
AS8359MTS PJSCMobileIPv4 IPv6100
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv698
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv676
AS31133PJSC MegaFonMobileIPv4 IPv668
AS213105LLC WildberriesUnclassifiedIPv463

Provenance

Where this comes from

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