World Phone Internet Services: PeeringDB fix list

AS18002 · peeringdb.com/net/10151

PeeringDB

3 things to fix in World Phone Internet Services's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on World Phone Internet Services'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 (1)

On the exchange's own member list, but not in World Phone Internet Services's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Kolkata Kolkata, India · PeeringDB 2589From 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.

Correct these entries (2)

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
    IPv6 address missing from PeeringDBnone2400:d180:68::43
    Port speed differs10G6G
    • In the entry with IPv4 103.228.174.43: set IPv6 to 2400:d180:68::43 (now empty); set Speed to 6000 (6G) (now 10000).
  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:7500:fff6::151
    Port speed differs10G1.5G
    • In the entry with IPv4 103.27.170.151: set IPv6 to 2401:7500:fff6::151 (now empty); set Speed to 1500 (1.5G) (now 10000).

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