Observed topology

AS27224 EQUINIX-EC-LA

Unclassified APNIC

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27224: 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 IPv6	90

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS53770	iQor US Inc.	Unclassified	IPv4	116
AS58744	Mirror Tower	Unclassified	IPv4 IPv6	77
AS27349	Definitive Networks, Inc.	Unclassified	IPv4	58
AS25627	Business Telecommunications Services Inc	Unclassified	IPv4	51
AS397849	ZOHO	Hosting	IPv4	47
AS32337	Nowcom Corporation	Unclassified	IPv4	33
AS46665	Applied Statistics & Management, Inc.	Unclassified	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4 IPv6	477
AS53770	iQor US Inc.	Unclassified	IPv4	116
AS58744	Mirror Tower	Unclassified	IPv4 IPv6	77
AS27349	Definitive Networks, Inc.	Unclassified	IPv4	58
AS25627	Business Telecommunications Services Inc	Unclassified	IPv4	51
AS397849	ZOHO	Hosting	IPv4	47
AS32337	Nowcom Corporation	Unclassified	IPv4	33
AS46665	Applied Statistics & Management, Inc.	Unclassified	IPv4	5

Provenance

Where this comes from

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