asn.dev

Observed topology

AS32575 DIGICERT

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32575: 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 IPv6423
AS3356Level 3 Parent, LLCTransitIPv4273
AS13767DataBank Holdings, Ltd.HostingIPv4104
AS3257GTT Communications Inc.TransitIPv466
AS13415FirstDigital Communications, LLCUnclassifiedIPv463
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv454
AS1299Arelion Sweden ABTransitIPv446
AS2914NTT America, Inc.TransitIPv4 IPv632
AS6461Zayo BandwidthTransitIPv47
AS7385Allstream Business US, LLCUnclassifiedIPv42

Transit

Downstream networks

inferred

Networks for which AS32575 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 AS32575 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6423
AS3356Level 3 Parent, LLCTransitIPv4273
AS13767DataBank Holdings, Ltd.HostingIPv4104
AS3257GTT Communications Inc.TransitIPv466
AS13415FirstDigital Communications, LLCUnclassifiedIPv463
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv454
AS1299Arelion Sweden ABTransitIPv446
AS2914NTT America, Inc.TransitIPv4 IPv632
AS6461Zayo BandwidthTransitIPv47
AS7385Allstream Business US, LLCUnclassifiedIPv42

Provenance

Where this comes from

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