DE-CIX Kuala Lumpur Route Servers: PeeringDB fix list

AS38194 · peeringdb.com/net/27112

PeeringDB

One thing to fix in DE-CIX Kuala Lumpur Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on DE-CIX Kuala Lumpur 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.

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. Malaysia DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia · PeeringDB 3473
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.119.234.252 103.119.234.253103.119.234.66 103.119.234.252 103.119.234.253
    IPv6 address missing from PeeringDB2403:4ac0:1::9532:a:1 2403:4ac0:1::9532:a:22403:4ac0:1::9532:a:1 2403:4ac0:1::9532:a:2 2403:4ac0:1::9532:b:dead
    Port speed differs2 × 1G3 × 20G
    • In the entry with IPv4 103.119.234.252: set Speed to 20000 (20G) (now 1000).
    • In the entry with IPv4 103.119.234.253: set Speed to 20000 (20G) (now 1000).
    • Add an entry: IPv4 103.119.234.66, IPv6 2403:4ac0:1::9532:b:dead, speed 20000 (20G), RS peer no.

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