ixreport

Hetzner Online: PeeringDB fix list

AS24940 · peeringdb.com/net/1766

PeeringDB

11 things to fix in Hetzner Online's PeeringDB record, from what its exchanges publish: 2 to add, 7 to correct, 2 to check. As of 2026-10-08 21:56 UTC.

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

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (7)

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. Spain DE-CIX Barcelona Barcelona, Spain · PeeringDB 3446
    ProblemPeeringDB hasThe export has
    Port speed differs50G1.2T
    • In the entry with IPv4 185.1.119.4: set Speed to 1200000 (1.2T) (now 50000).
  2. Germany DE-CIX Leipzig Leipzig, Germany · PeeringDB 4004
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 1.2T
    • In the entry with IPv4 185.1.245.11: set Speed to 1200000 (1.2T) (now 10000).
    • In the entry with IPv4 185.1.245.12: set Speed to 1200000 (1.2T) (now 10000).
  3. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531
    ProblemPeeringDB hasThe export has
    Port speed differs50G1.2T
    • In the entry with IPv4 185.1.131.55: set Speed to 1200000 (1.2T) (now 50000).
  4. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 1.2T
    • In the entry with IPv4 185.1.192.151: set Speed to 1200000 (1.2T) (now 100000).
    • In the entry with IPv4 185.1.192.204: set Speed to 1200000 (1.2T) (now 100000).
  5. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs50G1.2T
    • In the entry with IPv4 185.1.47.15: set Speed to 1200000 (1.2T) (now 50000).
  6. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs3 × 400G + 200G2 × 400G
    • In the entry with IPv4 178.18.226.223: set Speed to 400000 (400G) (now 200000).

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

  7. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs400G + 100G62.5G
    • In the entry with IPv4 185.0.20.73: set Speed to 62500 (62.5G) (now 400000).
    • In the entry with IPv4 185.0.21.73: set Speed to 62500 (62.5G) (now 100000).

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Hetzner Online has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Germany City-IX Frankfurt Frankfurt, Germany · PeeringDB 4175Not on its IX-F export
    IPv4185.0.10.71
    IPv62001:7f8:e2::a502:4940:1
    Speed400000 Mbps (400G)
  2. Germany OpenCarrier OCIX Duesseldorf, Germany · PeeringDB 170Not on its website members list
    IPv4194.54.92.122
    IPv62001:7f8:3a:e201::a2dc:fe01
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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