asn.dev

Observed topology

AS60486 SNS Swiss Networking Solutions AG

Unclassified RIPE NSP

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS60486: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6152
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv6103
AS24482SG.GSHostingIPv4 IPv672
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv663
AS2914NTT America, Inc.TransitIPv4 IPv656
AS6939Hurricane Electric LLCTransitIPv4 IPv646
AS9002RETN LimitedUnclassifiedIPv4 IPv641
AS174Cogent Communications, LLCTransitIPv4 IPv625
AS5511Orange S.A.TransitIPv419
AS3491PCCW Global (HK) Ltd.TransitIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58193Telecom26 AGUnclassifiedIPv4 IPv6400

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS58193Telecom26 AGUnclassifiedIPv4 IPv6400
AS1299Arelion Sweden ABTransitIPv4 IPv6206
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv6163
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6140
AS6939Hurricane Electric LLCTransitIPv4 IPv695
AS9002RETN LimitedUnclassifiedIPv4 IPv689
AS24482SG.GSHostingIPv4 IPv679
AS2914NTT America, Inc.TransitIPv4 IPv678
AS5511Orange S.A.TransitIPv478
AS174Cogent Communications, LLCTransitIPv4 IPv631

Provenance

Where this comes from

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