asn.dev

Observed topology

AS21217 SAFEHOSTNET Infrastructure Switzerland Colo Sarl

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21217: 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
AS25091IP-Max SAUnclassifiedIPv4 IPv6533
AS3356Level 3 Parent, LLCTransitIPv4 IPv689
AS3342Cibicom A/SUnclassifiedIPv460
AS47176GAS&COM AGUnclassifiedIPv4 IPv659
AS13237euNetworks GmbHUnclassifiedIPv4 IPv650
AS20932Services Industriels de GeneveUnclassifiedIPv4 IPv648

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42600Global Message Services Ukraine LLCUnclassifiedIPv445
AS50350MKS Pamp SAUnclassifiedIPv424

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS25091IP-Max SAUnclassifiedIPv4 IPv6580
AS3356Level 3 Parent, LLCTransitIPv4 IPv693
AS47176GAS&COM AGUnclassifiedIPv4 IPv666
AS3342Cibicom A/SUnclassifiedIPv460
AS13237euNetworks GmbHUnclassifiedIPv4 IPv657
AS20932Services Industriels de GeneveUnclassifiedIPv4 IPv652
AS42600Global Message Services Ukraine LLCUnclassifiedIPv445
AS50350MKS Pamp SAUnclassifiedIPv424

Provenance

Where this comes from

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