GNM: PeeringDB fix list

AS31500 · peeringdb.com/net/1423

PeeringDB

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

Make the changes on GNM'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 GNM's PeeringDB record. Add one entry per connection with these values.

  1. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326From its IX-F export
    IPv4–
    IPv62001:7f8:8e:4::4a
    Speed10000 Mbps (10G)
    RS peerYes

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 Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 80.81.192.159: set Speed to 100000 (100G) (now 20000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.224.163 178.18.224.179 178.18.224.186 178.18.224.199 178.18.225.119 178.18.226.55 178.18.226.94 178.18.227.13 178.18.227.14 178.18.227.111 178.18.233.5 178.18.233.10 178.18.236.16 178.18.236.17 178.18.236.18 178.18.236.52 178.18.236.53178.18.224.163 178.18.224.179 178.18.224.186 178.18.224.199 178.18.225.119 178.18.225.161 178.18.226.55 178.18.226.94 178.18.227.13 178.18.227.14 178.18.227.111 178.18.233.5 178.18.233.10 178.18.236.16 178.18.236.17 178.18.236.18 178.18.236.52 178.18.236.53
    Port speed differs6 × 400G + 3 × 200G + 2 × 100G + 40G + 30G + 4 × 10G4 × 400G + 2 × 200G + 2 × 100G + 40G + 30G + 4 × 10G
    • Add an entry: IPv4 178.18.225.161, IPv6 2a03:5f80:4::225:161, speed 40000 (40G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  3. ProblemPeeringDB hasThe export has
    Port speed differs20G40T
    • In the entry with IPv4 194.68.128.195: set Speed to 40000000 (40T) (now 20000).
  4. ProblemPeeringDB hasThe export has
    Port speed differs20G40T
    • In the entry with IPv4 194.68.123.195: set Speed to 40000000 (40T) (now 20000).

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