CYBEREVO: PeeringDB fix list
AS152787 · peeringdb.com/net/37152
5 things to fix in CYBEREVO's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on CYBEREVO'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 CYBEREVO'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 (4)
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:df6:480:0:2:54d3:0:1 Port speed differs 500M 10G - In the entry with IPv4 103.162.254.145: set IPv6 to 2001:df6:480:0:2:54d3:0:1 (now empty); set Speed to 10000 (10G) (now 500).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:df5:7880:0:2:54d3:0:2 - In the entry with IPv4 49.213.56.74: set IPv6 to 2001:df5:7880:0:2:54d3:0:2 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:2:5::34b Port speed differs 10G 1G - In the entry with IPv4 123.108.11.59: set IPv6 to 2001:7fa:2:5::34b (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:15:2787:1 - In the entry with IPv4 119.11.186.206: set IPv6 to 2404:c8:0:a:0:15:2787:1 (now empty).
From ixreport.com/net/152787/: 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.