flew2: PeeringDB fix list
AS208884 · peeringdb.com/net/25475
2 things to fix in flew2's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on flew2'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 missing from PeeringDB none 193.189.83.140 - In the entry with IPv6 2001:7f8:33::a120:8884:1: set IPv4 to 193.189.83.140 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If flew2 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2001:504:1b:1::65 Speed 1000 Mbps (1G)
From ixreport.com/net/208884/: 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.