PF Labs: PeeringDB fix list

AS39282 · peeringdb.com/net/25382

PeeringDB

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

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4185.1.125.196
    IPv62001:7f8:d0::9972:1
    SpeedNot published
    RS peerYes
  2. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.83.162
    IPv62001:7f8:33::a103:9282: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. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
    IPv4193.239.117.75
    IPv62001:7f8:13::a503:9282:1
    SpeedNot published
    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/39282/: 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.