Equinix Internet Exchange - MLPE Route Servers
AS24115 · MLPE route server peering
Equinix, Inc.
Tools: Where can I peer with Equinix Internet Exchange - MLPE Route Servers? · Where should Equinix Internet Exchange - MLPE Route Servers peer next? · Compare Equinix Internet Exchange - MLPE Route Servers with another network
PeeringDB fix list Printable page · CSV
7 things to fix in Equinix Internet Exchange - MLPE Route Servers's PeeringDB record, from what its exchanges publish: 4 to add, 1 to check, 2 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.
Make the changes on Equinix Internet Exchange - MLPE Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (4)
On the exchange's own member list, but not in Equinix Internet Exchange - MLPE Route Servers's PeeringDB record. Add one entry per connection with these values.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 185.1.2.4 IPv6 2001:7f8:81::2:4115:1 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Equinix Internet Exchange - MLPE Route Servers has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 192.65.185.251 IPv6 2001:7f8:1c:24a::5e33:1 Speed 10000 Mbps (10G) IPv4 192.65.185.252 IPv6 2001:7f8:1c:24a::5e33:2 Speed 10000 Mbps (10G)
Exchanges that look shut down (2)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only the operator's own networks
IPv4 202.50.242.251 IPv6 2001:def:4000::2:4115:1 Speed 10000 Mbps (10G) IPv4 202.50.242.252 IPv6 2001:def:4000::2:4115:2 Speed 10000 Mbps (10G) -
Only one outside network
IPv4 206.223.115.251 IPv6 2001:504:0:b:0:2:4115:1 Speed 10000 Mbps (10G) IPv4 206.223.115.252 IPv6 2001:504:0:b:0:2:4115:2 Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 49 |
| Nov 18, 2026 | 49 |
| Nov 17, 2026 | 49 |
| Nov 16, 2026 | 49 |
| Nov 15, 2026 | 49 |
| Nov 14, 2026 | 49 |
| Nov 13, 2026 | 49 |
| Nov 12, 2026 | 49 |
| Nov 11, 2026 | 49 |
| Nov 10, 2026 | 49 |
| Nov 9, 2026 | 49 |
| Nov 8, 2026 | 49 |
| Nov 7, 2026 | 49 |
| Nov 6, 2026 | 49 |
| Nov 5, 2026 | 49 |
| Nov 4, 2026 | 49 |
| Nov 3, 2026 | 49 |
| Nov 2, 2026 | 49 |
| Nov 1, 2026 | 49 |
| Oct 31, 2026 | 49 |
| Oct 30, 2026 | 49 |
| Oct 29, 2026 | 49 |
| Oct 28, 2026 | 49 |
| Oct 27, 2026 | 49 |
| Oct 26, 2026 | 49 |
| Oct 25, 2026 | 49 |
| Oct 24, 2026 | 49 |
| Oct 23, 2026 | 49 |
| Oct 22, 2026 | 49 |
| Oct 21, 2026 | 49 |
| Oct 20, 2026 | 49 |
| Oct 19, 2026 | 49 |
| Oct 18, 2026 | 49 |
| Oct 17, 2026 | 49 |
| Oct 16, 2026 | 49 |
| Oct 15, 2026 | 49 |
| Oct 14, 2026 | 49 |
| Oct 13, 2026 | 49 |
| Oct 12, 2026 | 49 |
| Oct 11, 2026 | 49 |
| Oct 10, 2026 | 49 |
| Oct 9, 2026 | 49 |
| Oct 8, 2026 | 49 |
| Oct 7, 2026 | 49 |
| Oct 6, 2026 | 49 |
| Oct 5, 2026 | 49 |
| Oct 4, 2026 | 49 |
| Oct 3, 2026 | 49 |
Map
Where Equinix Internet Exchange - MLPE Route Servers's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | Not in PeeringDB | ||
| 1-IX UA Kyiv, Ukraine | Not in PeeringDB | ||
| AuvernIX Clermont-Ferrand, France | 10G | Not in PeeringDB | |
| CIXP Geneva, Switzerland | 2 × 10G | PeeringDB only | |
| Equinix Amsterdam Amsterdam, Netherlands | 2 × 10G | PeeringDB | |
| Equinix Ashburn Ashburn, United States | 2 × 1G | PeeringDB | |
| Equinix Atlanta Atlanta, United States | 2 × 1G | PeeringDB | |
| Equinix Barcelona Barcelona, Spain | 2 × 10G | PeeringDB | |
| Equinix Bogota Bogota, Colombia | 2 × 10G | PeeringDB | |
| Equinix Chicago Chicago, United States | 2 × 1G | PeeringDB | |
| Equinix Dallas Dallas, United States | 2 × 1G | PeeringDB | |
| Equinix Denver Denver, United States | 2 × 10G | PeeringDB | |
| Equinix Dublin Dublin, Ireland | 2 × 10G | PeeringDB | |
| Equinix Frankfurt Frankfurt, Germany | 2 × 10G | PeeringDB | |
| Equinix Helsinki Helsinki, Finland | 2 × 1G | PeeringDB | |
| Equinix Hong Kong Hong Kong, Hong Kong | 2 × 1G | PeeringDB | |
| Equinix Jakarta Jakarta, Indonesia | 2 × 10G | PeeringDB | |
| Equinix Jeddah Jeddah, Saudi Arabia | 2 × 10G | PeeringDB | |
| Equinix Kuala Lumpurghost Kuala Lumpur, Malaysia | 2 × 10G | PeeringDB | |
| Equinix Lisbon Lisbon, Portugal | 2 × 10G | PeeringDB | |
| Equinix London London, United Kingdom | 2 × 10G | PeeringDB | |
| Equinix Los Angeles Los Angeles, United States | 2 × 1G | PeeringDB | |
| Equinix Madrid Madrid, Spain | 2 × 10G | PeeringDB | |
| Equinix Manchester Manchester, United Kingdom | 2 × 10G | PeeringDB | |
| Equinix Melbourne Melbourne, Australia | 2 × 1G | PeeringDB | |
| Equinix Mexico Mexico City, Mexico | 2 × 10G | PeeringDB | |
| Equinix Miami Miami, United States | 2 × 1G | PeeringDB | |
| Equinix Milan Milan, Italy | 2 × 10G | PeeringDB | |
| Equinix Montrealghost Montreal, Canada | 2 × 10G | PeeringDB | |
| Equinix Mumbai Mumbai, India | 2 × 10G | PeeringDB | |
| Equinix Muscat Muscat, Oman | 2 × 10G | PeeringDB | |
| Equinix New York New York, United States | 2 × 1G | PeeringDB | |
| Equinix Osaka Osaka, Japan | 2 × 1G | PeeringDB | |
| Equinix Palo Alto Palo Alto, United States | 2 × 1G | PeeringDB | |
| Equinix Paris Paris, France | 2 × 10G | PeeringDB | |
| Equinix Perth Perth, Australia | 2 × 1G | PeeringDB | |
| Equinix Rio de Janeiro Rio de Janeiro, Brazil | 2 × 10G | PeeringDB | |
| Equinix San Jose San Jose, United States | 2 × 1G | PeeringDB | |
| Equinix Seattle Seattle, United States | 2 × 1G | PeeringDB | |
| Equinix Seoul Seoul, South Korea | 2 × 1G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 2 × 1G | PeeringDB | |
| Equinix Stockholm Stockholm, Sweden | 2 × 10G | PeeringDB | |
| Equinix Sydney Sydney, Australia | 2 × 1G | PeeringDB | |
| Equinix São Paulo São Paulo, Brazil | 2 × 10G | PeeringDB | |
| Equinix Tokyo Tokyo, Japan | 2 × 1G | PeeringDB | |
| Equinix Toronto Toronto, Canada | 2 × 1G | PeeringDB | |
| Equinix Warsaw Warsaw, Poland | 2 × 10G | PeeringDB | |
| Equinix Zurich Zurich, Switzerland | 2 × 10G | PeeringDB | |
| THINX Warsaw Warsaw, Poland | 20G | Not in PeeringDB |
Equinix Internet Exchange - MLPE Route Servers lists no facilities in PeeringDB.