214757 - Jakub Krsa: PeeringDB fix list

AS214757 · peeringdb.com/net/36428

PeeringDB

6 things to fix in 214757 - Jakub Krsa's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on 214757 - Jakub Krsa'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 (1)

On the exchange's own member list, but not in 214757 - Jakub Krsa'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
    IPv4–
    IPv62001:7f8:d0::3:46e5:1
    SpeedNot published
    RS peerYes

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 178.18.237.48: set Speed to 10000 (10G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. ProblemPeeringDB hasThe export has
    Port speed differs100M100G
    • In the entry with IPv4 194.68.128.38: set Speed to 100000 (100G) (now 100).
  3. ProblemPeeringDB hasThe export has
    Port speed differs100M100G
    • In the entry with IPv4 195.69.119.38: set Speed to 100000 (100G) (now 100).
  4. ProblemPeeringDB hasThe export has
    Port speed differs100M100G
    • In the entry with IPv4 194.68.123.38: set Speed to 100000 (100G) (now 100).
  5. ProblemPeeringDB hasThe export has
    Port speed differs100M100G
    • In the entry with IPv4 195.245.240.38: set Speed to 100000 (100G) (now 100).

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