ixreport

Frys-IX Route Servers: PeeringDB fix list

AS56393 · peeringdb.com/net/26884

PeeringDB

3 things to fix in Frys-IX Route Servers's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Frys-IX Route Servers'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 (2)

On the exchange's own member list, but not in Frys-IX Route Servers's PeeringDB record. Add one entry per connection with these values.

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From 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. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326From its IX-F export
    IPv4–
    IPv62001:7f8:8e:4::2d
    Speed10000 Mbps (10G)
    RS peerYes

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. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512
    ProblemPeeringDB hasThe export has
    Port speed differs3 × 10G2 × 10G + 1G
    • In the entry with IPv4 185.1.160.255: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 185.1.161.0: set Speed to 1000 (1G) (now 10000).

    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/56393/: 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.