ixreport

UWV: PeeringDB fix list

AS213065 · peeringdb.com/net/23912

PeeringDB

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

Make the changes on UWV'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 (1)

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

  1. Netherlands NL-ix 2 Amsterdam, Netherlands · PeeringDB 2569From its IX-F export
    IPv4185.1.122.31
    IPv62001:7f8:cd::a521:3065: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.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If UWV has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64Not on its IX-F export or website members list
    IPv4193.239.118.247
    IPv62001:7f8:13::a521:3065
    Speed10000 Mbps (10G)
    IPv4193.239.118.248
    IPv62001:7f8:13::a521:3065:2
    Speed10000 Mbps (10G)

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