KPMG IT Service: PeeringDB fix list

AS60979 · peeringdb.com/net/22641

PeeringDB

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

Make the changes on KPMG IT Service'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 (4)

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 Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:9e::ee33:0:1
    • In the entry with IPv4 185.1.170.202: set IPv6 to 2001:7f8:9e::ee33:0:1 (now empty).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::ee33:0:1 2001:7f8::ee33:0:2
    • In the entry with IPv4 80.81.196.13: set IPv6 to 2001:7f8::ee33:0:1 (now empty).
    • In the entry with IPv4 80.81.196.15: set IPv6 to 2001:7f8::ee33:0:2 (now empty).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:3d::ee33:0:1
    • In the entry with IPv4 185.1.210.180: set IPv6 to 2001:7f8:3d::ee33:0:1 (now empty).
  4. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:44::ee33:0:1
    • In the entry with IPv4 185.1.208.188: set IPv6 to 2001:7f8:44::ee33:0:1 (now empty).

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