asn.dev

Observed topology

AS20612 SWISSIX

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20612: 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
AS8758Iway AGResidentialIPv4 IPv690
AS6939Hurricane Electric LLCTransitIPv4 IPv637
AS1299Arelion Sweden ABTransitIPv4 IPv626
AS174Cogent Communications, LLCTransitIPv4 IPv612
AS9044BSE Software GmbHResidentialIPv411
AS24482SG.GSHostingIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS1836green.ch AGResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8758Iway AGResidentialIPv4 IPv693
AS6939Hurricane Electric LLCTransitIPv4 IPv637
AS1299Arelion Sweden ABTransitIPv4 IPv626
AS174Cogent Communications, LLCTransitIPv4 IPv612
AS9044BSE Software GmbHResidentialIPv411
AS24482SG.GSHostingIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63
AS1836green.ch AGResidentialIPv42

Provenance

Where this comes from

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