atom86: PeeringDB fix list
AS8455 · peeringdb.com/net/4158
3 things to fix in atom86's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on atom86'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 atom86's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.94.31 IPv6 2001:7f8:b6::2107:1 Speed 10000 Mbps (10G) RS peer No
Correct these entries (2)
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 80.249.211.217 80.249.211.217 80.249.214.171 IPv6 address missing from PeeringDB 2001:7f8:1::a500:8455:1 2001:7f8:1::a500:8455:1 2001:7f8:1::a500:8455:2 Port speed differs 100G 100G + 10G - Add an entry: IPv4 80.249.214.171, IPv6 2001:7f8:1::a500:8455:2, speed 10000 (10G), RS peer no.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 800G - In the entry with IPv4 80.81.195.22: set Speed to 800000 (800G) (now 10000).
From ixreport.com/net/8455/: 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.