Rajasa (PT.Raja Sepadan Abadi): PeeringDB fix list
AS45146 · peeringdb.com/net/24498
2 things to fix in Rajasa (PT.Raja Sepadan Abadi)'s PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 21:56 UTC.
Make the changes on Rajasa (PT.Raja Sepadan Abadi)'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:7fa:2:5::1d4 Port speed differs 10G 1G - In the entry with IPv4 123.108.9.212: set IPv6 to 2001:7fa:2:5::1d4 (now empty); set Speed to 1000 (1G) (now 10000).
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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Rajasa (PT.Raja Sepadan Abadi) has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 119.11.187.194 IPv6 – Speed 1000 Mbps (1G)
From ixreport.com/net/45146/: 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.