asn.dev

Observed topology

AS20412 CLARITY-TELECOM - Clarity Telecom LLC

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20412: 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 IPv618,993
AS1299Arelion Sweden ABTransitIPv4 IPv62,644
AS174Cogent Communications, LLCTransitIPv4912
AS46692City of WindomUnclassifiedIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS399204White Iron LLCUnclassifiedIPv4 IPv6101
AS54639Apogee Telecom Inc.UnclassifiedIPv466
AS401873UNIVERSAL HEALTH SERVICESUnclassifiedIPv446

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv619,170
AS1299Arelion Sweden ABTransitIPv4 IPv62,668
AS174Cogent Communications, LLCTransitIPv4924
AS399204White Iron LLCUnclassifiedIPv4 IPv6101
AS54639Apogee Telecom Inc.UnclassifiedIPv466
AS401873UNIVERSAL HEALTH SERVICESUnclassifiedIPv446
AS46692City of WindomUnclassifiedIPv412

Provenance

Where this comes from

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