ixreport

Helix-ix: PeeringDB fix list

AS211738

2 things to fix in Helix-ix's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 22:13 UTC.

AS211738 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (2)

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

  1. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.83.153
    IPv62001:7f8:33::a121:1738:1
    Speed100 Mbps (100M)
    RS peerYes

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

  2. Netherlands LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From 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.

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