Zayo: PeeringDB fix list
AS6461 · peeringdb.com/net/541
6 things to fix in Zayo's PeeringDB record, from what its exchanges publish: 3 to add, 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Zayo'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 Zayo's PeeringDB record. Add one entry per connection with these values.
-
Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From its website members listThe 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 IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
IPv4 149.112.104.44 IPv6 – Speed Not published RS peer Not published
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 Port speed differs 30G 100G - In the entry with IPv4 195.66.244.191: set Speed to 100000 (100G) (now 30000).
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 62.69.146.131 62.69.146.139 62.69.146.139 IPv6 address in PeeringDB, not in the export 2001:7f8:8:20:0:193d:0:1 2001:7f8:8:20:0:193d:0:2 2001:7f8:8:20:0:193d:0:1 - The entry with IPv4 62.69.146.131, IPv6 2001:7f8:8:20:0:193d:0:2 isn't in the export: delete it if that connection is gone.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Zayo has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.0.27.97 IPv6 2001:7f8:15e::97 Speed 100000 Mbps (100G)
From ixreport.com/net/6461/: 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.