modulus: PeeringDB fix list

AS201494 · peeringdb.com/net/14862

PeeringDB

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

Make the changes on modulus'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 DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 80.81.195.105: set Speed to 100000 (100G) (now 10000).
  2. Greece GR-IX::Athens Athens, Greece · PeeringDB 347
    ProblemPeeringDB hasThe export has
    Port speed differs4 × 10G2 × 1G
    • In the entry with IPv4 176.126.38.20: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 176.126.38.58: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 176.126.38.63: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 176.126.38.64: 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.

  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G500M
    • In the entry with IPv4 195.66.231.147: set Speed to 500 (500M) (now 10000).

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