Airbeam: PeeringDB fix list
AS50877 · peeringdb.com/net/12537
4 things to fix in Airbeam's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Airbeam'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 (3)
On the exchange's own member list, but not in Airbeam's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.46.21 IPv6 2001:7f8:32::c6bd:0:1 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 193.201.28.150 IPv6 2001:7f8:10::5:877 Speed Not published RS peer Yes 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.
-
The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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.
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 Port speed differs 20G 10G - In the entry with IPv4 217.29.66.225: set Speed to 10000 (10G) (now 20000).
From ixreport.com/net/50877/: 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.