Webguru B.V.: PeeringDB fix list

AS201650

One thing to fix in Webguru B.V.'s PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

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

Add these exchanges (1)

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

  1. 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

    3 connections, so 3 entries:

    IPv4193.239.117.229
    IPv62001:7f8:13::a520:1650:1
    SpeedNot published
    RS peerYes
    IPv4193.239.117.230
    IPv62001:7f8:13::a520:1650:2
    SpeedNot published
    RS peerYes
    IPv4193.239.119.60
    IPv62001:7f8:13::a520:1650:3
    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/201650/: 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.