asn.dev

Observed topology

AS211452 KANTONAR

Unclassified RIPE Government

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211452: 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 IPv633
AS8758Iway AGResidentialIPv4 IPv627
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv618
AS51907Kanton ZugUnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv62
AS49432Dominic Schallert trading as schallert.com e.U.UnclassifiedIPv4 IPv62
AS50869IPng Networks GmbHUnclassifiedIPv42
AS34019Hivane AssociationUnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS211452 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv633
AS8758Iway AGResidentialIPv4 IPv627
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv618
AS51907Kanton ZugUnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv62
AS49432Dominic Schallert trading as schallert.com e.U.UnclassifiedIPv4 IPv62
AS50869IPng Networks GmbHUnclassifiedIPv42
AS34019Hivane AssociationUnclassifiedIPv41

Provenance

Where this comes from

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