asn.dev

Observed topology

AS57073 Wildberries-AS LLC Wildberries

Unclassified APNIC

Upstreams 18 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 18
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 18

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 IPv6287
AS1299Arelion Sweden ABTransitIPv4 IPv6160
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6158
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6104
AS8359MTS PJSCMobileIPv4 IPv6100
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6100
AS31500Global Network Management IncUnclassifiedIPv4 IPv697
AS3216PJSC "Vimpelcom"MobileIPv4 IPv674
AS31133PJSC MegaFonMobileIPv4 IPv664
AS199599Telecom-Birzha, LLCUnclassifiedIPv4 IPv633

All 18 upstreams →

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 WildberriesUnclassifiedIPv462
AS33902ePharmacy LLCUnclassifiedIPv461

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6343
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6168
AS1299Arelion Sweden ABTransitIPv4 IPv6160
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6120
AS31500Global Network Management IncUnclassifiedIPv4 IPv6105
AS8359MTS PJSCMobileIPv4 IPv6102
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6100
AS3216PJSC "Vimpelcom"MobileIPv4 IPv696
AS31133PJSC MegaFonMobileIPv4 IPv664
AS213105LLC WildberriesUnclassifiedIPv462

All 20 adjacent →

Provenance

Where this comes from

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