ixreport

Christian Vonderstein: PeeringDB fix list

AS211715 · peeringdb.com/net/26154

PeeringDB

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

Make the changes on Christian Vonderstein'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 (3)

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

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From 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. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.83.224
    IPv62001:7f8:33::a121:1715: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.

  3. Egypt PyramIX Cairo, Egypt · PeeringDB 3302From its IX-F export and website members list
    IPv4–
    IPv62a0e:46c4:102::211:715: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.

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