ixreport

Apple Cache Initiative: PeeringDB fix list

AS214622 · peeringdb.com/net/37453

3 things to fix in Apple Cache Initiative's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-11-12 18:41 UTC.

Make the changes on Apple Cache Initiative'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 (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. Germany BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs200G10G
    • In the entry with IPv4 193.178.185.36: set Speed to 10000 (10G) (now 200000).

    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 (2)

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

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31Not on its IX-F export or website members list
    IPv480.81.197.72
    IPv62001:7f8::3:465e:0:1
    Speed200000 Mbps (200G)
  2. Germany DE-CIX Munich Munich, Germany · PeeringDB 248Not on its IX-F export or website members list
    IPv4185.1.208.177
    IPv62001:7f8:44:0:3:465e:0:1
    Speed200000 Mbps (200G)

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