Dolphin IT-Systeme: PeeringDB fix list
AS204028 · peeringdb.com/net/10576
3 things to fix in Dolphin IT-Systeme's PeeringDB record, from what its exchanges publish: 2 to add, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.
Make the changes on Dolphin IT-Systeme'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 Dolphin IT-Systeme'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:1cfc:1 Speed Not published RS peer Yes -
IPv4 193.189.83.249 IPv6 2001:7f8:33::a120:4028:1 Speed 100 Mbps (100M) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only the operator's own networks
IPv4 185.1.54.1 IPv6 2001:7f8:95::1 Speed 1000 Mbps (1G)
From ixreport.com/net/204028/: 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.