1&1 Versatel Deutschland: PeeringDB fix list
AS8881 · peeringdb.com/net/684
4 things to fix in 1&1 Versatel Deutschland's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on 1&1 Versatel Deutschland'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 1&1 Versatel Deutschland's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.18.60 IPv6 2001:67c:2b9c::100:60 Speed 100000 Mbps (100G) 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.
Correct these entries (3)
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 Port speed differs 100G 200G - In the entry with IPv4 185.1.170.109: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 500G + 2 × 100G 2 × 500G + 200G + 100G - In the entry with IPv4 80.81.196.22: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 200G 50G - In the entry with IPv4 185.0.20.140: set Speed to 50000 (50G) (now 200000).
- In the entry with IPv4 185.0.20.194: set Speed to 50000 (50G) (now 200000).
From ixreport.com/net/8881/: 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.