PLTPRO Data Centre: PeeringDB fix list

AS131310 · peeringdb.com/net/4355

PeeringDB

3 things to fix in PLTPRO Data Centre's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on PLTPRO Data Centre'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 (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. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100M20G + 1G
    • In the entry with IPv4 103.162.254.21: set Speed to 1000 (1G) (now 100).
    • In the entry with IPv4 103.162.254.22: set Speed to 20000 (20G) (now 100).
  2. Malaysia DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia · PeeringDB 3473
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 1G20G + 1G
    • In the entry with IPv4 103.119.234.18: set Speed to 20000 (20G) (now 1000).
  3. Malaysia DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia · PeeringDB 3474
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100M20G + 1G
    • In the entry with IPv4 103.119.232.17: set Speed to 1000 (1G) (now 100).
    • In the entry with IPv4 103.119.232.18: set Speed to 20000 (20G) (now 100).

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