ixreport

DE-CIX Mumbai Route Servers: PeeringDB fix list

AS59200 · peeringdb.com/net/18630

PeeringDB

5 things to fix in DE-CIX Mumbai Route Servers's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on DE-CIX Mumbai 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 (2)

On the exchange's own member list, but not in DE-CIX Mumbai Route Servers's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Chennai Chennai, India · PeeringDB 2588From its IX-F export

    2 connections, so 2 entries:

    IPv4103.228.174.64
    IPv62400:d180:68::64
    Speed1000 Mbps (1G)
    RS peerNo
    IPv4103.228.174.65
    IPv62400:d180:68::65
    Speed1000 Mbps (1G)
    RS peerNo
  2. India DE-CIX Delhi Delhi, India · PeeringDB 2587From its IX-F export

    2 connections, so 2 entries:

    IPv4103.27.168.64
    IPv62400:d180:67::64
    Speed1000 Mbps (1G)
    RS peerNo
    IPv4103.27.168.65
    IPv62400:d180:67::65
    Speed1000 Mbps (1G)
    RS peerNo

Correct these entries (3)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. India DE-CIX Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB103.228.174.64 is AS24470 DE-CIX Chennai Route Servers103.228.174.64
    Address belongs to another network in PeeringDB103.228.174.65 is AS24470 DE-CIX Chennai Route Servers103.228.174.65
    Address belongs to another network in PeeringDB2400:d180:68::64 is AS24470 DE-CIX Chennai Route Servers2400:d180:68::64
    Address belongs to another network in PeeringDB2400:d180:68::65 is AS24470 DE-CIX Chennai Route Servers2400:d180:68::65

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

  2. India DE-CIX Delhi Delhi, India · PeeringDB 2587
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB103.27.168.64 is AS24457 DE-CIX Delhi Route Servers103.27.168.64
    Address belongs to another network in PeeringDB103.27.168.65 is AS24457 DE-CIX Delhi Route Servers103.27.168.65
    Address belongs to another network in PeeringDB2400:d180:67::64 is AS24457 DE-CIX Delhi Route Servers2400:d180:67::64
    Address belongs to another network in PeeringDB2400:d180:67::65 is AS24457 DE-CIX Delhi Route Servers2400:d180:67::65

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

  3. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.27.170.64 103.27.170.65103.27.170.64
    IPv6 address in PeeringDB, not in the export2401:7500:fff6::64 2401:7500:fff6::652401:7500:fff6::64
    Port speed differs2 × 1G10G
    • In the entry with IPv4 103.27.170.64: set Speed to 10000 (10G) (now 1000).
    • The entry with IPv4 103.27.170.65, IPv6 2401:7500:fff6::65 isn't in the export: delete it if that connection is gone.

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