Same here in Belgium using Proximus 100/20 and Proximus data connection not working… Tried everything and I don’t want to use a VPN
Expecting a solution very soon…?
Hi Paul, can you explain your ideia ? I am also a “computer geek” and I am thinking what does the list of ports helps on fixing the problem. This must be something with IPS and ZWIFT.
It won’t help fix the problem, it would just show the user where the issue is.
Do you mind explaining your strategy…maybe I can help you …
In my mention it’s a routing problem with secure.zwift.com
habib@MacBook-ProR ~ % traceroute secure.zwift.com
traceroute: Warning: secure.zwift.com has multiple addresses; using 52.35.78.137
traceroute to secure.zwift.com (52.35.78.137), 64 hops max, 52 byte packets
1 fritz.box (192.168.100.1) 1.750 ms 1.156 ms 1.110 ms
2 85.16.121.207 (85.16.121.207) 19.094 ms 19.276 ms 19.784 ms
3 85.16.250.34 (85.16.250.34) 20.037 ms 20.043 ms 19.595 ms
4 85.16.249.99 (85.16.249.99) 19.800 ms 19.750 ms 19.813 ms
5 bbrt.hb-0-1-ae3.ewe-ip-backbone.de (80.228.90.41) 22.285 ms 21.431 ms 21.752 ms
6 bbrt.hb-2-xe-3-0-0.ewe-ip-backbone.de (80.228.90.5) 21.761 ms 21.906 ms 23.291 ms
7 bbrt.ffm-0-ae10.ewe-ip-backbone.de (212.6.114.22) 29.731 ms 29.489 ms 29.482 ms
8 80.157.206.141 (80.157.206.141) 29.864 ms 30.162 ms 30.346 ms
9 pao-sb3-i.pao.us.net.dtag.de (62.154.5.242) 186.706 ms 184.568 ms 185.438 ms
10 pao-sb3-i.pao.us.net.dtag.de (62.154.5.242) 184.273 ms 184.705 ms 184.881 ms
11 * * *
12 * * 52.93.141.161 (52.93.141.161) 178.689 ms
13 * * 54.240.243.155 (54.240.243.155) 181.119 ms
14 * * *
15 * 52.93.128.26 (52.93.128.26) 203.994 ms
52.93.128.22 (52.93.128.22) 199.801 ms
16 * * *
17 * * *
18 52.93.14.46 (52.93.14.46) 321.559 ms
52.93.15.48 (52.93.15.48) 206.045 ms
52.93.15.40 (52.93.15.40) 304.211 ms
19 * * 52.93.14.107 (52.93.14.107) 202.172 ms
20 52.93.14.144 (52.93.14.144) 201.403 ms
52.93.14.182 (52.93.14.182) 197.221 ms
52.93.14.176 (52.93.14.176) 201.565 ms
21 52.93.240.111 (52.93.240.111) 217.286 ms
54.239.48.197 (54.239.48.197) 201.235 ms *
22 * 52.93.240.87 (52.93.240.87) 197.453 ms
52.93.240.97 (52.93.240.97) 325.954 ms
23 * * *
24 * * *
If I call the URL in a webbrowser I get an redirect to: Welcome to Red Hat Single Sign-On
Where a Red Hat Single Sign on waits:
1 Like
i have the same problem in Germany, Win10, all accounts (three)
“no roads available, please check your internet connection”
1 Like
If I switch from wlan to mobile data (different provider), it works. Strange.
1 Like
Same problem here In Belgium
Can t Log In 
2 Likes
I agree, looks like a routing issue.
Here is my trace:
tracert secure.zwift.com
Tracing route to secure.zwift.com [54.149.44.59]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms RT-AC68U-B4F8 [192.168.1.1]
2 3 ms 2 ms 2 ms 195.190.228.119
3 * * * Request timed out.
4 4 ms 3 ms 3 ms asd2-rou-1022.NL.eurorings.net [134.222.129.236]
5 3 ms 3 ms 3 ms asd-s5-rou-1041.NL.eurorings.net [134.222.48.247]
6 4 ms 4 ms 4 ms adm-b1-link.telia.net [213.248.77.152]
7 149 ms 150 ms 150 ms adm-bb4-link.telia.net [62.115.137.64]
8 * * * Request timed out.
9 * * * Request timed out.
10 154 ms 155 ms 155 ms sjo-b21-link.telia.net [213.155.130.129]
11 150 ms 150 ms 149 ms a100-ic-301289-sjo-b21.c.telia.net [213.248.101.158]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Jepp - this works her also 
- very strange
If I switch from wlan to mobile data (different provider), it works.
Zwift has been down for hours now for me. Using iPad, provider Proximus. All other software and internet works just fine. Only Zwift doesn’t …
I had my virtual ride for today, but not in zwift, only in rouvy
Traceroute from Deutsche Telekom:
traceroute to secure.zwift.com (52.35.78.137), 30 hops max, 60 byte packets
1 fritz.box (192.168.0.1) 0.758 ms 0.678 ms 0.754 ms
2 62.155.246.201 (62.155.246.201) 8.873 ms 8.948 ms 9.580 ms
3 pao-sb3-i.PAO.US.NET.DTAG.DE (62.154.5.90) 159.734 ms 160.076 ms 160.406 ms
4 pao-sb3-i.PAO.US.NET.DTAG.DE (62.154.5.90) 160.302 ms 160.619 ms 160.841 ms
5 80.157.200.202 (80.157.200.202) 159.056 ms 158.952 ms 159.754 ms
6 52.93.141.161 (52.93.141.161) 157.051 ms * 52.93.141.155 (52.93.141.155) 159.398 ms
7 * 54.240.243.99 (54.240.243.99) 159.135 ms 54.240.243.37 (54.240.243.37) 154.904 ms
8 * * *
9 52.93.131.162 (52.93.131.162) 179.136 ms * 52.93.130.24 (52.93.130.24) 178.947 ms
10 * 52.93.131.235 (52.93.131.235) 182.493 ms 52.93.131.231 (52.93.131.231) 180.201 ms
11 52.93.15.38 (52.93.15.38) 180.312 ms * *
12 52.93.14.179 (52.93.14.179) 180.104 ms 52.93.14.143 (52.93.14.143) 177.044 ms 52.93.14.160 (52.93.14.160) 171.748 ms
13 * 52.93.14.109 (52.93.14.109) 178.391 ms 52.93.14.69 (52.93.14.69) 172.756 ms
14 * * 52.93.14.104 (52.93.14.104) 179.395 ms
15 52.93.246.181 (52.93.246.181) 177.720 ms * *
16 * * 52.93.246.83 (52.93.246.83) 179.550 ms
17 * * *
18 * * *
After 3 hops I’m already in the US, but then it gets stuck somewhere in Amazon Cloud. It pretty looks the same as early April.
From another german provider, it looks even worse:
2 * * *
3 core5.fra.hetzner.com (213.239.224.254) 17.421 ms
core5.fra.hetzner.com (213.239.224.250) 71.273 ms
core5.fra.hetzner.com (213.239.224.254) 27.861 ms
4 ffm-b4-link.telia.net (213.248.70.2) 5.389 ms * *
5 ffm-bb2-link.telia.net (62.115.114.90) 146.897 ms
ffm-bb1-link.telia.net (62.115.114.88) 151.160 ms 150.962 ms
6 prs-bb4-link.telia.net (62.115.122.138) 152.046 ms * *
7 rest-bb1-link.telia.net (62.115.122.159) 92.441 ms
ash-bb2-link.telia.net (62.115.112.242) 96.704 ms
rest-bb1-link.telia.net (62.115.122.159) 92.234 ms
8 las-b24-link.telia.net (62.115.114.86) 147.096 ms 146.693 ms
las-b24-link.telia.net (62.115.121.220) 149.943 ms
9 a100-ic-325183-las-b24.c.telia.net (62.115.155.111) 155.468 ms * 158.390 ms
10 * * *
11 * * *
12 * * *
But in April were only Telekom customers in germany affected, not me for example… I’m already german but not Telekom customer…
Same problem. Location: Munich. Provider: 1&1.
As the issue seems to reach lots of user, does anyone from Zwift will give some news about the way they try to find a solution? Do they answer on forum or do they only communicate with the “status” page? (I am not used to this forum).
I was one of the first users with that login problems and contacted zwift support at 9 o’clock today morning and didn’t get any answer until now.
I also contacted them this morning. I guess they are busy with this problem… It was just to know if we can hope an solution for tomorrow… The weather here is not very good to go outside this WE… 
Same problem. Location: Braunschweig. Provider: 1&1
Same here. (Netherlands). When i use a VPN, it works.