NET Super Cepat: PeeringDB fix list
AS138838 · peeringdb.com/net/20613
2 things to fix in NET Super Cepat's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on NET Super Cepat'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:7fa:2:5::165 - In the entry with IPv4 123.108.9.101: set IPv6 to 2001:7fa:2:5::165 (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.
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2404:c8:0:a:0:13:8838:1 none Port speed differs 10G 1G - In the entry with IPv4 119.11.184.160: set IPv6 to (empty) (now 2404:c8:0:a:0:13:8838:1); set Speed to 1000 (1G) (now 10000).
From ixreport.com/net/138838/: 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.