asn.dev

Observed topology

AS57512 SPORTMASTER

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS57512: 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
AS197068HLL LLCHostingIPv4118
AS3216PJSC "Vimpelcom"MobileIPv479
AS35598INETCOM CARRIER LLCUnclassifiedIPv462
AS20485Joint Stock Company TransTeleComUnclassifiedIPv424
AS15672OOO Telecom TZUnclassifiedIPv46
AS34549meerfarbig GmbH & Co. KGHostingIPv46
AS24482SG.GSHostingIPv42
AS34019Hivane AssociationUnclassifiedIPv42
AS37100SEACOM LimitedUnclassifiedIPv42
AS48362Stadtwerke FeldkirchResidentialIPv42

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS57512 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 11

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

ASNetworkTypeFamiliesPaths seen
AS197068HLL LLCHostingIPv4118
AS3216PJSC "Vimpelcom"MobileIPv479
AS35598INETCOM CARRIER LLCUnclassifiedIPv462
AS20485Joint Stock Company TransTeleComUnclassifiedIPv424
AS15672OOO Telecom TZUnclassifiedIPv46
AS34549meerfarbig GmbH & Co. KGHostingIPv46
AS24482SG.GSHostingIPv42
AS34019Hivane AssociationUnclassifiedIPv42
AS37100SEACOM LimitedUnclassifiedIPv42
AS48362Stadtwerke FeldkirchResidentialIPv42

All 11 adjacent →

Provenance

Where this comes from

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