asn.dev

Observed topology

AS62512 SANDWICH-NET

Hosting ARIN Content

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS62512: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6122
AS30176Priority Colo IncHostingIPv4113
AS54527Astute InternetHostingIPv4 IPv691
AS15576NTS workspace AGUnclassifiedIPv4 IPv670
AS22652Videotron LteeResidentialIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv67
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS1403EBOXResidentialIPv64
AS1836green.ch AGResidentialIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS62512 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 13

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6122
AS30176Priority Colo IncHostingIPv4113
AS54527Astute InternetHostingIPv4 IPv691
AS15576NTS workspace AGUnclassifiedIPv4 IPv670
AS22652Videotron LteeResidentialIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv67
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS1403EBOXResidentialIPv64
AS1836green.ch AGResidentialIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

All 13 adjacent →

Provenance

Where this comes from

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