ixreport

KPMG IT Service

AS60979

KPMG IT Service GmbH

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
4Using the route servers
4To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with KPMG IT Service? · Where should KPMG IT Service peer next? · Compare KPMG IT Service with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in KPMG IT Service's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-11-19 12:40 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).

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where KPMG IT Service's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 50G across 4 exchanges.

Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.170.202 10G 5 routes Both IPv6 not in PeeringDB
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.196.13
80.81.196.15
2 × 10G 10 routes Both IPv6 not in PeeringDB
Germany DE-CIX Hamburg Hamburg, Germany 185.1.210.180 10G 5 routes Both IPv6 not in PeeringDB
Germany DE-CIX Munich Munich, Germany 185.1.208.188 10G 5 routes Both IPv6 not in PeeringDB

KPMG IT Service lists no facilities in PeeringDB.