ixreport

Aéza (RU): PeeringDB fix list

AS216246 · peeringdb.com/net/38806

PeeringDB

One thing to fix in Aéza (RU)'s PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 22:13 UTC.

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

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

    2 connections, so 2 entries:

    IPv4178.18.225.240
    IPv62a03:5f80:4::225:240
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.225.199
    IPv62a03:5f80:4::225:199
    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/216246/: 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.