4ALL: PeeringDB fix list
AS50316 · peeringdb.com/net/4001
3 things to fix in 4ALL's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on 4ALL'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 (3)
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 4G 800G - In the entry with IPv4 80.81.193.99: set Speed to 800000 (800G) (now 4000).
-
Problem PeeringDB has The export has Port speed differs 20G 2 × 20G - Add an entry: IPv4 –, IPv6 2001:7f8:b:100:1d1:a5d5:316:110, speed 20000 (20G), RS peer yes.
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:7f8:5f:ffff::22 none Port speed differs 20G 40G - In the entry with IPv4 185.1.115.22: set IPv6 to (empty) (now 2001:7f8:5f:ffff::22); set Speed to 40000 (40G) (now 20000).
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/50316/: 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.