EdgeNext: PeeringDB fix list
AS139057 · peeringdb.com/net/25380
3 things to fix in EdgeNext's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on EdgeNext'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 EdgeNext's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 100G 800G + 100G - In the entry with IPv4 119.11.185.23: set Speed to 800000 (800G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G + 10G 200G + 100G - In the entry with IPv4 185.1.8.97: set Speed to 200000 (200G) (now 10000).
From ixreport.com/net/139057/: 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.