ixreport

Lars Ewald: PeeringDB fix list

AS200372

3 things to fix in Lars Ewald's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 18:53 UTC.

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

Add these exchanges (3)

On the exchange's own member list, but not in Lars Ewald'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
    IPv4–
    IPv62001:7f8:d0::3:eb4:1
    SpeedNot published
    RS peerYes
  2. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:ca:1:0:20:372:1
    Speed1000 Mbps (1G)
    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.119.126
    IPv62001:7f8:13::a520:372: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/200372/: 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.