M EAST: PeeringDB fix list
AS132531 · peeringdb.com/net/19269
2 things to fix in M EAST's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on M EAST'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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:df6:480:0:2:5b3:0:1 Port speed differs 1G 10G - In the entry with IPv4 103.162.254.80: set IPv6 to 2001:df6:480:0:2:5b3:0:1 (now empty); set Speed to 10000 (10G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If M EAST has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia · PeeringDB 3474Not on its IX-F exportIPv4 103.119.232.5 IPv6 – Speed 1000 Mbps (1G)
From ixreport.com/net/132531/: 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.