Deutsche Telekom: PeeringDB fix list
AS3320 · peeringdb.com/net/196
3 things to fix in Deutsche Telekom's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Deutsche Telekom'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 Deutsche Telekom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 192.65.185.135 IPv6 2001:7f8:1c:24a::cf8:1 Speed Not published RS peer No -
Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From its website members listThe 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 (1)
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 110G 10G - In the entry with IPv4 80.81.194.95: set Speed to 10000 (10G) (now 110000).
From ixreport.com/net/3320/: 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.