Equinix IP Ranges
Equinix, Inc. runs AS14609 as its own North America corporate network, not the colocation and interconnection business the Equinix name usually means to a network engineer. ARIN names the autnum EQUINIX-CORP-NETWORK with a registration date of 12 January 2000 and Equinix, Inc. as the registrant organisation, and RIPEstat currently counts 22 announced IPv4 prefixes covering 6,656 addresses and zero IPv6. PeeringDB records the network's type as Enterprise and its scope as North America rather than service provider, and its operator note says the Equinix corporate network is being integrated into AS15830, with existing exchange connections replaced by new ones to that ASN - an Equinix ASN announcing 1,074 IPv4 prefixes against this network's 22.
- Provider
- Equinix
- Primary ASN
- AS14609
- Category
- Hosting
- Headquarters
- Redwood City, USA
- Announced IPv4 prefixes
- 22
- Registry
- ARIN
Known IP ranges
These prefixes are currently announced to the global routing table by AS14609 (EQUINIX-CORP-NETWORK - Equinix, Inc.). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
64.191.238.0/23
64.191.206.0/23
208.115.142.0/23
64.191.248.0/23
64.191.204.0/24
206.223.135.0/24
206.223.132.0/24
216.221.224.0/24
206.223.133.0/24
64.191.195.0/24
What does an Equinix IP mean in a privacy test?
An address on AS14609 is not a customer's server and not a VPN exit - it is Equinix's own infrastructure. The ARIN registrations back that up on 21 of the 22 announced prefixes, every one of them naming Equinix, Inc. as registrant: EQUINIX-EDMA-CORP-4 on a /23, -7 and -12 on /24s, EQUINIX-IBX-SANDBOX-1 on a /22 that is announced as four separate /24s, EQUINIX-WIFI-INTERCONNECT-US on another /24, plus further EDMA-CORP entries and blocks named EQUINIX-REMOTE-KIOSK-1 and EQUINIX-CORP-DR - internal offices, lab systems and guest network gear inside Equinix's own facilities, not tenant equipment. One block breaks the pattern: 206.184.17.0/24 sits inside a /16 that ARIN's registry assigns to NTT America, Inc., not Equinix, though a ROA does authorise AS14609 to originate it. None of this is Equinix's data centre colocation business; colocation tenants route their own address space under their own ASNs.
What ARIN and PeeringDB register for AS14609, and what is changing
ARIN's record for AS14609 carries a registration date of 12 January 2000 and an autnum name of EQUINIX-CORP-NETWORK, with Equinix, Inc. as the registrant organisation, and RIPEstat's routing-status data currently puts what it announces at 22 IPv4 prefixes covering 6,656 addresses, with no IPv6 announced at all. Checking the ARIN registration behind every one of those prefixes turns up internal naming rather than customer records on 21 of the 22: EQUINIX-EDMA-CORP-4 on 208.115.142.0/23, EQUINIX-EDMA-CORP-7 on 64.191.195.0/24, EQUINIX-EDMA-CORP-12 on 216.221.224.0/24, EQUINIX-IBX-SANDBOX-1 on the /22 at 206.223.132.0/22 that is announced as four separate /24s, and EQUINIX-WIFI-INTERCONNECT-US on 67.223.178.0/24, alongside further EDMA-CORP entries and objects named EQUINIX-REMOTE-KIOSK-1 and EQUINIX-CORP-DR - IBX is Equinix's own term for its data centre buildings, and all 21 name Equinix, Inc. as registrant, a few of them through ARIN customer objects that still carry the Equinix name. One prefix does not fit the pattern: 206.184.17.0/24 sits inside a /16 that ARIN's registry assigns to NTT America, Inc. under the netname NTTA-206-184, not to Equinix. RIPEstat's rpki-validation endpoint makes it the only one of the 22 that validates at all, on a ROA authorising origin AS14609 for exactly 206.184.17.0/24 at max length 24 - so the address holder has signed off on the arrangement, even though no public record says why it exists.
Equinix's own PeeringDB record for AS14609, net ID 1466, names it Equinix Corpnet - NAMER, records its network type as Enterprise and its scope as North America rather than service provider, sets a general peering policy of No, and lists eight connections across six of Equinix's own exchange points: Ashburn, Chicago, Dallas, Los Angeles, New York and San Jose. That record also carries an operator note, last updated 6 August 2024, stating that the Equinix corporate network is being integrated into AS15830 and that its existing IX connections are being replaced by new connections to that ASN. The prefix figures on that same record - 20 for IPv4 and 1 for IPv6 - are not announcement counts and do not contradict RIPEstat: they are the recommended maximum-prefix limits Equinix asks peers to configure on sessions with this ASN, a ceiling rather than a measurement.
Why an Equinix data centre tenant is never on this ASN
Equinix's actual business - selling rack space, cross-connects and interconnection inside its IBX data centres - does not run on AS14609 at all. A company that colocates equipment in an Equinix facility brings its own ASN and announces its own address space from inside the building; Equinix does not route customer traffic under its own name. AS14609 is the opposite case: PeeringDB records it as an Enterprise-type network scoped to North America, and the ARIN registrations behind 21 of its 22 announced prefixes read as internal infrastructure - a sandbox network, a wifi-interconnect block, a disaster-recovery block, a remote-kiosk block and a long EDMA-CORP naming series - rather than anything a customer would touch. Seeing this specific ASN in a lookup result points at Equinix itself, not at whoever happens to be renting a cage nearby.
That still leaves two things this ASN cannot tell a reader. It cannot confirm which Equinix facility or system originated a given connection: the registered names describe function, not location, and none of the Equinix RDAP records checked publish a geofeed. The one record that does publish one is NTT America's, on the 206.184.0.0/16 covering the odd prefix out, and that feed carries no entry anywhere inside 206.184.0.0/16, so it yields no location either. And that odd prefix, 206.184.17.0/24, is registered in ARIN's database to NTT America, Inc. rather than Equinix despite being announced under AS14609 - a ROA does authorise AS14609 to originate it, so the arrangement is sanctioned, but registry ownership and BGP origin still diverge here. Equinix's own PeeringDB entry is meanwhile explicit that AS14609 is being folded into AS15830, an Equinix ASN announcing 1,074 IPv4 prefixes against this network's 22.
Related tools
Frequently asked questions
What is AS14609?
It is an autonomous system number registered with ARIN under the autnum name EQUINIX-CORP-NETWORK, with Equinix, Inc. as the registrant organisation and a registration date of 12 January 2000. It is Equinix's North America corporate network, not the ASN behind its colocation and data centre business.
How large is the network behind AS14609?
Small, and shrinking by design. RIPEstat currently counts 22 announced IPv4 prefixes totalling 6,656 addresses and no IPv6. PeeringDB's own record for the ASN says the Equinix corporate network is being integrated into AS15830, which announces 1,074 IPv4 prefixes and about 1.5 million addresses by comparison.
If an IP is in this range, does that guarantee it belongs to Equinix?
Almost certainly yes for the address itself, though not for what sits behind it. ARIN's registrations for 21 of the 22 announced prefixes carry Equinix's internal naming - EDMA-CORP, IBX-SANDBOX, WIFI-INTERCONNECT, REMOTE-KIOSK, CORP-DR - and every one of them names Equinix, Inc. as registrant. One exception exists: 206.184.17.0/24 is announced under AS14609 but registered in ARIN's database to NTT America, Inc., inside their 206.184.0.0/16.
How do I look up an IP against AS14609?
Query RIPEstat's announced-prefixes and routing-status endpoints for resource AS14609 to see the current prefix list, or look up the address directly at ARIN's RDAP service to see which named registration object covers it. PeeringDB's record for net ID 1466 gives the operator-published side: peering policy, exchange presence and the note about the move to AS15830.
My connection or a lookup shows an Equinix AS14609 address - what does that prove?
That the address belongs to Equinix's own North America corporate network - offices, lab systems, guest network gear - not to a customer colocating equipment in an Equinix data centre; tenants announce their own ASNs from inside Equinix facilities instead. It does not identify which Equinix site or system originated the connection, and one of the 22 announced prefixes, 206.184.17.0/24, is registered in ARIN's database to NTT America rather than Equinix - a ROA authorises AS14609 to originate it, but registry ownership and BGP origin still are not the same thing here.