Sano Komunikasi: PeeringDB fix list
AS131713 · peeringdb.com/net/20211
3 things to fix in Sano Komunikasi's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Sano Komunikasi'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 (1)
On the exchange's own member list, but not in Sano Komunikasi's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.122.64.51 IPv6 – Speed Not published RS peer Yes
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 Port speed differs 10G 1G - In the entry with IPv4 123.108.8.225: 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 IPv4 address in PeeringDB, not in the export 119.11.184.161 119.11.186.19 119.11.186.19 IPv6 address in PeeringDB, not in the export 2404:c8:0:a:0:13:1713:1 2404:c8:0:a:0:13:1713:2 2404:c8:0:a:0:13:1713:2 Port speed differs 2 × 10G 10G - The entry with IPv4 119.11.184.161, IPv6 2404:c8:0:a:0:13:1713:1 isn't in the export: delete it if that connection is gone.
From ixreport.com/net/131713/: 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.