SOLUSI TRIMEGAH PERSADA: PeeringDB fix list
AS136065 · peeringdb.com/net/21826
2 things to fix in SOLUSI TRIMEGAH PERSADA's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on SOLUSI TRIMEGAH PERSADA'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::176 Port speed differs 10G 1G - In the entry with IPv4 123.108.9.118: set IPv6 to 2001:7fa:2:5::176 (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:13:6065:1 - In the entry with IPv4 119.11.184.138: set IPv6 to 2404:c8:0:a:0:13:6065:1 (now empty).
From ixreport.com/net/136065/: 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.