Docker: PeeringDB fix list
AS21030 · peeringdb.com/net/15199
4 things to fix in Docker's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 18:53 UTC.
Make the changes on Docker'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 (2)
On the exchange's own member list, but not in Docker'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.
-
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 (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 178.18.225.134 178.18.227.10 178.18.233.25 178.18.224.118 178.18.224.174 178.18.225.134 178.18.225.205 178.18.227.10 178.18.233.25 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:118 2a03:5f80:4::224:174 2a03:5f80:4::225:134 2a03:5f80:4::225:205 2a03:5f80:4::227:10 2a03:5f80:4:1::233:25 - In the entry with IPv4 178.18.225.134: set IPv6 to 2a03:5f80:4::225:134 (now empty).
- In the entry with IPv4 178.18.227.10: set IPv6 to 2a03:5f80:4::227:10 (now empty).
- In the entry with IPv4 178.18.233.25: set IPv6 to 2a03:5f80:4:1::233:25 (now empty).
- Add an entry: IPv4 178.18.225.205, IPv6 2a03:5f80:4::225:205, speed 10000 (10G), RS peer yes.
- Add an entry: IPv4 178.18.224.118, IPv6 2a03:5f80:4::224:118, speed 80000 (80G), RS peer yes.
- Add an entry: IPv4 178.18.224.174, IPv6 2a03:5f80:4::224:174, speed 80000 (80G), RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 185.1.118.23 IPv6 – Speed Not published
From ixreport.com/net/21030/: 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.