ixreport

equada network GmbH: PeeringDB fix list

AS25220 · peeringdb.com/net/1201

PeeringDB

3 things to fix in equada network GmbH's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on equada network GmbH'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 (3)

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. Germany BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 193.178.185.90: set Speed to 10000 (10G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs5G10G
    • In the entry with IPv4 80.81.194.140: set Speed to 10000 (10G) (now 5000).
  3. Germany KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    Port speed differs10G100M
    • In the entry with IPv4 193.189.82.43: set Speed to 100 (100M) (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/25220/: 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.