Paradise Telecom: PeeringDB fix list

AS136284 · peeringdb.com/net/15529

PeeringDB

One thing to fix in Paradise Telecom's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Paradise Telecom's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

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 Extreme IX Mumbai Mumbai, India · PeeringDB 1627
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df2:1900:2::1059
    • In the entry with IPv4 103.77.109.59: set IPv6 to 2001:df2:1900:2::1059 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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