ixreport

Aéza

AS210644

3Exchanges
3On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
2Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Aéza? · Where should Aéza peer next? · Compare Aéza with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Aéza's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-11-19 12:40 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.

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20262
Oct 26, 20262
Oct 25, 20262
Oct 24, 20262
Oct 23, 20262
Oct 22, 20262
Oct 21, 20262
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Aéza's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 310G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands ERA-IX Amsterdam Amsterdam, Netherlands Website list only
Germany ERA-IX Frankfurt Frankfurt, Germany 185.0.27.29 2001:7f8:15e::29 100G Yes Not in PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.203
178.18.225.110
178.18.225.158
178.18.236.136
2a03:5f80:4::224:203
2a03:5f80:4::225:110
2a03:5f80:4::225:158
2a03:5f80:4:2::236:136
2 × 100G + 10G Yes Not in PeeringDB

Aéza lists no facilities in PeeringDB.