SYNLINQ: PeeringDB fix list

AS44486 · peeringdb.com/net/22724

PeeringDB

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

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

  1. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789From 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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.237.117
    IPv62a03:5f80:4:2::237:117
    Speed400000 Mbps (400G)
    RS peerYes

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

Correct these entries (1)

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
    IPv4 address missing from PeeringDB80.81.194.12080.81.194.120 80.81.197.45
    IPv6 address missing from PeeringDB2001:7f8::adc6:0:12001:7f8::adc6:0:1 2001:7f8::adc6:0:3
    • Add an entry: IPv4 80.81.197.45, IPv6 2001:7f8::adc6:0:3, speed 10000 (10G), RS peer yes.

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