Wahyu Adidaya Network: PeeringDB fix list
AS140469 · peeringdb.com/net/24142
4 things to fix in Wahyu Adidaya Network's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Wahyu Adidaya Network's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (2)
On the exchange's own member list, but not in Wahyu Adidaya Network's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.101.136.25 IPv6 – Speed Not published RS peer Not published -
IPv4 123.108.8.131 IPv6 2001:7fa:2:5::83 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
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 2401:91e0:31::140:469:1 Port speed differs 10.24G 10G - In the entry with IPv4 43.254.82.69: set IPv6 to 2401:91e0:31::140:469:1 (now empty); set Speed to 10000 (10G) (now 10240).
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 Port speed differs 10.24G 10G - In the entry with IPv4 119.11.184.113: set Speed to 10000 (10G) (now 10240).
From ixreport.com/net/140469/: 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.