Curug Lintas Indonesia: PeeringDB fix list
AS150197 · peeringdb.com/net/31512
3 things to fix in Curug Lintas Indonesia'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 Curug Lintas Indonesia'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::256 Port speed differs 10G 1G - In the entry with IPv4 123.108.10.70: set IPv6 to 2001:7fa:2:5::256 (now empty); set Speed to 1000 (1G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2404:c8:0:a:0:15:197:1 - In the entry with IPv4 119.11.185.171: set IPv6 to 2404:c8:0:a:0:15:197:1 (now empty).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Curug Lintas Indonesia has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 49.213.56.35 IPv6 2001:df5:7880:0:2:4ab5:0:1 Speed 1000 Mbps (1G)
From ixreport.com/net/150197/: 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.