Zayo Europe: PeeringDB fix list

AS8218 · peeringdb.com/net/1479

PeeringDB

3 things to fix in Zayo Europe's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Zayo Europe'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 Zayo Europe's PeeringDB record. Add one entry per connection with these values.

  1. France Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From its website members list

    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.

  1. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 185.1.208.22: set Speed to 100000 (100G) (now 40000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Zayo Europe has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Germany ERA-IX Frankfurt Frankfurt, Germany · PeeringDB 4630Not on its IX-F export or website members list
    IPv4185.0.27.98
    IPv62001:7f8:15e::98
    Speed100000 Mbps (100G)

From ixreport.com/net/8218/: 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.