Mediana: PeeringDB fix list

AS56347 · peeringdb.com/net/26535

PeeringDB

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

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

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

    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, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

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

  1. Ukraine UA-IX Kiev, Ukraine · PeeringDB 184Not on its website members list
    IPv4185.1.50.34
    IPv62001:7f8:5d::34
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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