ixreport

IT-SERVICE: PeeringDB fix list

AS34681 · peeringdb.com/net/22357

PeeringDB

5 things to fix in IT-SERVICE's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on 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.

Add these exchanges (2)

On the exchange's own member list, but not in IT-SERVICE's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4185.1.125.194
    IPv62001:7f8:d0::8779:1
    SpeedNot published
    RS peerYes
  2. Egypt PyramIX Cairo, Egypt · PeeringDB 3302From its website members list
    IPv4–
    IPv62a0e:46c4:102::346:81:1
    SpeedNot published
    RS peerNot published

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 Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.170.122: set Speed to 10000 (10G) (now 1000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.210.132: set Speed to 10000 (10G) (now 1000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.208.114: set Speed to 10000 (10G) (now 1000).

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