ixreport

Aéza: PeeringDB fix list

AS210644 · peeringdb.com/net/28239

PeeringDB

3 things to fix in Aéza's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 18:53 UTC.

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

  1. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789From 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.

  2. Germany ERA-IX Frankfurt Frankfurt, Germany · PeeringDB 4630From its IX-F export and website members list
    IPv4185.0.27.29
    IPv62001:7f8:15e::29
    Speed100000 Mbps (100G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    4 connections, so 4 entries:

    IPv4178.18.224.203
    IPv62a03:5f80:4::224:203
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.225.158
    IPv62a03:5f80:4::225:158
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.225.110
    IPv62a03:5f80:4::225:110
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.236.136
    IPv62a03:5f80:4:2::236:136
    Speed100000 Mbps (100G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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