Druifje: PeeringDB fix list
AS215216 · peeringdb.com/net/35747
4 things to fix in Druifje's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Druifje'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 (2)
On the exchange's own member list, but not in Druifje's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 – IPv6 2001:7f8:d0::3:48b0:1 Speed Not published RS peer Yes -
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (2)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.0.27.61 - In the entry with IPv6 2001:7f8:15e::61: set IPv4 to 185.0.27.61 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.0.30.66 - In the entry with IPv6 2001:7f8:11c:1:0:21:5216:1: set IPv4 to 185.0.30.66 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/215216/: 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.