Alida: PeeringDB fix list
AS56376 · peeringdb.com/net/19646
2 things to fix in Alida's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Alida'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 Alida's PeeringDB record. Add one entry per connection with these values.
-
IPv4 217.29.67.223 IPv6 2001:7f8:b:100:1d1:a5d5:6376:223 Speed 10000 Mbps (10G) RS peer Yes
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 IPv6 address in PeeringDB, not in the export 2001:7f8:10::5:6376 none - In the entry with IPv4 193.201.28.81: set IPv6 to (empty) (now 2001:7f8:10::5:6376).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/56376/: 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.