ixreport

TKRZ Stadtwerke: PeeringDB fix list

AS42184 · peeringdb.com/net/1937

PeeringDB

5 things to fix in TKRZ Stadtwerke's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on TKRZ Stadtwerke'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 (5)

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
    Port speed differs10G100G
    • In the entry with IPv4 185.1.170.16: set Speed to 100000 (100G) (now 10000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs25G100G
    • In the entry with IPv4 80.81.192.178: set Speed to 100000 (100G) (now 25000).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs2G100G
    • In the entry with IPv4 185.1.210.102: set Speed to 100000 (100G) (now 2000).
  4. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs2G100G
    • In the entry with IPv4 185.1.208.147: set Speed to 100000 (100G) (now 2000).
  5. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs10G1.25G
    • In the entry with IPv4 185.0.21.15: set Speed to 1250 (1.25G) (now 10000).

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