Equinix Internet Exchange - MLPE Route Servers: PeeringDB fix list

AS24115 · peeringdb.com/net/3658

PeeringDB

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-10-08 20:58 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. Poland 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.

  2. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From 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.

  3. France AuvernIX Clermont-Ferrand, France · PeeringDB 1019From its IX-F export
    IPv4185.1.2.4
    IPv62001:7f8:81::2:4115:1
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  4. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481From its IX-F export

    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.

  1. Switzerland CIXP Geneva, Switzerland · PeeringDB 33Not on its IX-F export
    IPv4192.65.185.251
    IPv62001:7f8:1c:24a::5e33:1
    Speed10000 Mbps (10G)
    IPv4192.65.185.252
    IPv62001:7f8:1c:24a::5e33:2
    Speed10000 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.

  1. Malaysia Equinix Kuala Lumpurghost Kuala Lumpur, Malaysia · PeeringDB 4490

    Only the operator's own networks

    IPv4202.50.242.251
    IPv62001:def:4000::2:4115:1
    Speed10000 Mbps (10G)
    IPv4202.50.242.252
    IPv62001:def:4000::2:4115:2
    Speed10000 Mbps (10G)
  2. Canada Equinix Montrealghost Montreal, Canada · PeeringDB 3814

    Only one outside network

    IPv4206.223.115.251
    IPv62001:504:0:b:0:2:4115:1
    Speed10000 Mbps (10G)
    IPv4206.223.115.252
    IPv62001:504:0:b:0:2:4115:2
    Speed10000 Mbps (10G)

From ixreport.com/net/24115/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.