asn.dev

Observed topology

AS32415 C3-LLC

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32415: 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
AS174Cogent Communications, LLCTransitIPv41,646
AS6939Hurricane Electric LLCTransitIPv41,084
AS46887Crown Castle Fiber LLCUnclassifiedIPv4192
AS23005SWITCH, LTDUnclassifiedIPv4177
AS33154DQE Communications LLCResidentialIPv454
AS3303Swisscom (Schweiz) AGResidentialIPv436
AS24482SG.GSHostingIPv436

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS22150Carrierhouse Corp.UnclassifiedIPv4699
AS26742MaxNOC Communications, LLC.UnclassifiedIPv4130
AS401319TensorWave Inc.UnclassifiedIPv490
AS366444Voice LLCUnclassifiedIPv452

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv41,867
AS6939Hurricane Electric LLCTransitIPv41,805
AS22150Carrierhouse Corp.UnclassifiedIPv4699
AS46887Crown Castle Fiber LLCUnclassifiedIPv4192
AS23005SWITCH, LTDUnclassifiedIPv4177
AS26742MaxNOC Communications, LLC.UnclassifiedIPv4130
AS401319TensorWave Inc.UnclassifiedIPv490
AS33154DQE Communications LLCResidentialIPv454
AS24482SG.GSHostingIPv452
AS366444Voice LLCUnclassifiedIPv452

All 11 adjacent →

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.