Observed topology

AS32323 EQUINIX-EC-TR

Unclassified ARIN

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

Upstream graph Who carries AS32323, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS32323 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32323: 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.

AS	Network	Type	Families	Paths seen
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	290

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS27301	Cerner Corporation	Unclassified	IPv4	58
AS40286	Banque Laurentienne du Canada	Unclassified	IPv4	58
AS55117	Long View Systems Corporation (USA)	Unclassified	IPv4	58
AS62685	OrionVM Inc	Unclassified	IPv4	58
AS26211	Proofpoint, Inc.	Unclassified	IPv4 IPv6	37

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4 IPv6	559
AS27301	Cerner Corporation	Unclassified	IPv4	58
AS40286	Banque Laurentienne du Canada	Unclassified	IPv4	58
AS55117	Long View Systems Corporation (USA)	Unclassified	IPv4	58
AS62685	OrionVM Inc	Unclassified	IPv4	58
AS26211	Proofpoint, Inc.	Unclassified	IPv4 IPv6	37

Provenance

Where this comes from

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