MX-IX Route Servers: PeeringDB fix list

AS141539 · peeringdb.com/net/25805

PeeringDB

3 things to fix in MX-IX Route Servers's PeeringDB record, from what its exchanges publish: 3 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

Make the changes on MX-IX 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.

Exchanges that look shut down (3)

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. India MX-IX Chennaighost Chennai, India · PeeringDB 5079

    Only the operator's own networks

    IPv4103.162.76.210
    IPv62001:df5:e880:5::210
    Speed10000 Mbps (10G)
    IPv4103.162.76.220
    IPv62001:df5:e880:5::220
    Speed10000 Mbps (10G)
  2. United Arab Emirates MX-IX Dubaighost Dubai, United Arab Emirates · PeeringDB 4959

    Only the operator's own networks

    IPv4103.162.77.251
    IPv62001:df5:e880:3::251
    Speed10000 Mbps (10G)
    IPv4103.162.77.252
    IPv62001:df5:e880:3::252
    Speed10000 Mbps (10G)
  3. United Arab Emirates MX-IX Fujairahghost Fujairah, United Arab Emirates · PeeringDB 5027

    Only the operator's own networks

    IPv4103.162.76.151
    IPv62001:df5:e880:4::251
    Speed10000 Mbps (10G)
    IPv4103.162.76.152
    IPv62001:df5:e880:4::252
    Speed10000 Mbps (10G)

From ixreport.com/net/141539/: 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.