Julius Wolff: PeeringDB fix list
AS211688 · peeringdb.com/net/26186
3 things to fix in Julius Wolff's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on Julius Wolff's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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.1.147.28 - In the entry with IPv6 2001:7f8:ca:1::28: set IPv4 to 185.1.147.28 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 193.189.83.167 - In the entry with IPv6 2001:7f8:33::a121:1688:1: set IPv4 to 193.189.83.167 (now empty).
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 Julius Wolff has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2602:fed2:fff:ffff:6::70 Speed 1000 Mbps (1G)
From ixreport.com/net/211688/: 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.