Atha Media Prima: PeeringDB fix list
AS139989 · peeringdb.com/net/22386
2 things to fix in Atha Media Prima's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 21:35 UTC.
Make the changes on Atha Media Prima'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 IPv4 address in PeeringDB, not in the export 119.11.185.6 119.11.185.93 119.11.185.93 IPv6 address in PeeringDB, not in the export 2404:c8:0:a:0:13:9989:1 2404:c8:0:a:0:13:9989:2 2404:c8:0:a:0:13:9989:1 Port speed differs 200G + 100G 100G - The entry with IPv4 119.11.185.6, IPv6 2404:c8:0:a:0:13:9989:2 isn't in the export: delete it if that connection is gone.
- In the entry with IPv4 119.11.185.93: set Speed to 100000 (100G) (now 200000).
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 45.137.96.11 IPv6 2a10:cc40:111::1399:89 Speed 10000 Mbps (10G) IPv4 45.137.96.9 IPv6 2a10:cc40:111::1399:89:2 Speed 40000 Mbps (40G)
From ixreport.com/net/139989/: 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.