One.com: PeeringDB fix list
AS51468 · peeringdb.com/net/3411
6 things to fix in One.com's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on One.com'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 One.com'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.
-
IPv4 195.69.119.221 IPv6 2001:7f8:d:fb::221 Speed Not published RS peer Yes -
IPv4 195.245.240.221 IPv6 2001:7f8:d:fc::221 Speed Not published RS peer Yes
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 5G 100G - In the entry with IPv4 185.1.170.78: set Speed to 100000 (100G) (now 5000).
-
Problem PeeringDB has The export has Port speed differs 5G 100G - In the entry with IPv4 185.1.210.91: set Speed to 100000 (100G) (now 5000).
-
Problem PeeringDB has The export has Port speed differs 5G 100G - In the entry with IPv4 185.1.208.86: set Speed to 100000 (100G) (now 5000).
From ixreport.com/net/51468/: 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.