Problem with login to Zwift via German Telekom

Ja, könnten sie.
Ist aber der falsche Ansatz, schließlich zahlen deutsche Internetkunden der Telekom schon genug Geld, und sie kriegen auch noch Millionen Fördergelder vom Staat für den Ausbau des Netzes.

Mercedes/VW/BMW könnten auch die deutsche Straßeninfrastruktur ausbauen… aber auch hier: Ist der falsche Ansatz.

1 Like

Seems that Telekom is working on the issue. Other gaming platforms (PSN, Nintendo, Twitch) have the same issues via Telekom networks. A quick Twitter search shows a lot of complaints:

https://twitter.com/search?q=psn%20telekom&src=typed_query&f=live

https://twitter.com/search?q=telekom%20twitch&src=typed_query&f=live

https://twitter.com/search?q=telekom%20nintendo&src=typed_query&f=live

2 Likes

Hier noch ein Beitrag. Zwar völlig andere Plattform aber exakt dieselbe Symptomatik und zur selben Zeit gingen da auch die Probleme los:

https://telekomhilft.telekom.de/t5/Telefonie-Internet/Extremer-TCP-Packet-loss-amp-retransmissions-ab-nachmittags-im/m-p/4474836

1 Like

Heute wieder das selbe Problem. Einfachste Lösung für mich: LTE mit Smartphone als Hotspot. Konnte 5 Stunden trainieren ohne Dropouts und am Ende auch speichern. Ungefähr 0,8 GB verbraucht.

Heute auch mehrere Stunden nachmitags vergeblich versucht, mich über Telekom DSL bei Zwift einzuloggen. Mega frustrierend, und keine Kösung absehbar :frowning:

Use a VPN connection, that works perfectly.

It would be good to look what changed on Wednesday last week as several service report failures since then. Not really plausible that exactly Wednesday the load on all services increased so much that would explain the outages. Especially as the load obviously was high enough on weekends also. The corona crisis started earlier than Wednesday.

Eric Schlange is reporting in Zwiftinsider on this problem:

It seems like Deutsche Telekom has an issue with routing into a huge network assigned to AWS (Amazon Web Service) where e.g. Zwift is running its authentication service (or using a provider who is hosting within aws). The affected network is 52.93.0.0/16. I’d urge anyone who has problems to open a support ticket with his ISP so they can properly work on it.
Here is an example to trace the way to secure.zwift.com which is the service you have to logon:

➜ ~ traceroute secure.zwift.com
traceroute: Warning: secure.zwift.com has multiple addresses; using 54.149.44.59
traceroute to secure.zwift.com (54.149.44.59), 64 hops max, 52 byte packets
1 192.168.5.1 (192.168.5.1) 5.293 ms 2.460 ms 1.246 ms
2 62.155.221.39 (62.155.221.39) 10.700 ms 11.340 ms 10.172 ms
3 d-ed5-i.d.de.net.dtag.de (62.154.43.126) 20.516 ms 21.007 ms 21.535 ms
4 80.157.204.58 (80.157.204.58) 73.023 ms 73.598 ms 73.638 ms
5 ae10.cr4-lax2.ip4.gtt.net (89.149.130.90) 216.359 ms 215.597 ms 225.998 ms
6 a100-gw.ip4.gtt.net (173.205.58.58) 219.475 ms 218.363 ms 221.056 ms
7 54.239.103.78 (54.239.103.78) 228.656 ms
54.239.103.18 (54.239.103.18) 222.601 ms
54.239.103.42 (54.239.103.42) 219.087 ms
8 54.239.103.73 (54.239.103.73) 220.116 ms
54.239.102.225 (54.239.102.225) 219.879 ms
54.239.103.107 (54.239.103.107) 231.643 ms
9 * * *
10 54.239.44.22 (54.239.44.22) 244.867 ms 242.077 ms 240.757 ms
11 * * *
12 52.93.14.50 (52.93.14.50) 254.292 ms
52.93.15.48 (52.93.15.48) 242.860 ms
52.93.14.124 (52.93.14.124) 249.517 ms
13 * 52.93.15.31 (52.93.15.31) 280.418 ms
52.93.14.35 (52.93.14.35) 247.976 ms
14 52.93.14.68 (52.93.14.68) 245.354 ms
52.93.14.216 (52.93.14.216) 244.478 ms *
15 52.93.246.175 (52.93.246.175) 242.975 ms
52.93.15.25 (52.93.15.25) 237.497 ms
52.93.15.19 (52.93.15.19) 246.470 ms
16 205.251.232.222 (205.251.232.222) 238.671 ms
52.93.246.77 (52.93.246.77) 239.311 ms
52.93.246.75 (52.93.246.75) 240.879 ms
17 * * *
18 * 52.93.240.65 (52.93.240.65) 244.565 ms *
19 * * *
20 * * *
21 * * *
22 * * *

There is no chance to explain that problem to a normal hotline worker there, sorry. The will only perform a quick check that will pass all tests. (There is no, correct but they have to check their own routes to aws.)
We need a tech Insider or big customer which tells them (not the support phone) this problem.

Any options to use a vpn on the Apple TV?

You really can’t be sure that the VPN company is not doing so either.

1 Like

Same problem since 25.03.2020. I use mobile hotspot on mobile phone for Login. After login I switch to ISP Deutsche Telekom.

1 Like

Same problem. Zwift login issue. Zwift companien also did not work. Help

I guess not for a “normal” user. If you use a router with OpenWrt, a Fritzbox or e.g. a pfSense firewall/router you can route your whole outgoing internet traffic via VPN. An easier way would be to connect your ATV with a free Freifunk WLAN hotspot, if you have one nearby - I am running such a Freifunk hotspot by my own, so that’s the way I go and it works. I have to say that it depends on how the regional Freifunk network is connected to the backbone.
Of course you can also connect ATV to the WLAN hotspot of your smartphone, as many people here in the forum have described already - but it can become pricey :wink:

Unfortunately, that’s a common missunderstanding of VPN - I recomment anyone to read this article

1 Like

Nothing to add, but also experiencing the same problem. Called Telekom, but the response was as clueless as one would expect.

I had seen it after I had replyed already :blush: - In the end I thought the article is of general interest, so do not take it personal.

Having the same issue :frowning:
I just canceled my Zwift membership due to that. Maybe time to give TrainerRoad a try.
Any suggestions for a (ideally free) tool to use workouts from TrainingPeaks to control the trainer?

Login via cellular is now also not possible. Very bad.

Bin zwar nach langer Wartezeit teilweise reinkommen die letzten Tage - aber jetzt geht gar nichts mehr!!! Ebenfalls Telekom Kunde