Omonia: PeeringDB fix list

AS44306 · peeringdb.com/net/3471

PeeringDB

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

Make the changes on Omonia's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (2)

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. Croatia CIX Zagreb, Croatia · PeeringDB 303
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 40G2 × 20G
    • In the entry with IPv4 185.1.87.140: set Speed to 20000 (20G) (now 40000).
    • In the entry with IPv4 185.1.87.87: set Speed to 20000 (20G) (now 40000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs100G20G
    • In the entry with IPv4 80.81.194.204: set Speed to 20000 (20G) (now 100000).

Check these entries (1)

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

  1. Hungary BIX Budapest, Hungary · PeeringDB 55Not on its IX-F export
    IPv4193.188.137.33
    IPv62001:7f8:35::4:4306:1
    Speed10000 Mbps (10G)

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