Zona Sejahtera Mandiri: PeeringDB fix list
AS134127 · peeringdb.com/net/40005
3 things to fix in Zona Sejahtera Mandiri's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Zona Sejahtera Mandiri'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 (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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:df5:7880:0:2:bef:0:1 Port speed differs 1G 10G - In the entry with IPv4 49.213.56.131: set IPv6 to 2001:df5:7880:0:2:bef:0:1 (now empty); set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:2:5::3c7 - In the entry with IPv4 123.108.11.183: set IPv6 to 2001:7fa:2:5::3c7 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Zona Sejahtera Mandiri has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 103.162.254.169 IPv6 – Speed 1000 Mbps (1G)
From ixreport.com/net/134127/: 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.