Is Zwift down in the US?
Vendor reports no incidentWhat Zwift reports
Zwift reports no incident on its status page.
As of the last successful poll, 2026-11-05 17:59 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Zwift at Nov 5, 2026, 5:57 PM UTC.
Over the last 24 hours we completed 241 checks from Ashburn and San Jose and 241 answered cleanly, 100.00% availability.
Of the 2 other regions we check Zwift from, all 2 read checks passing right now.
Email me when Zwift reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 5:57 PM UTC.
Zwift from Ashburn and San Jose over the last 30 days
Over the last 30 days, Zwift answered our Ashburn probe in 969 ms on average, and 1 check in 20 took longer than 1,738 ms.
Over the last 30 days, Zwift answered our San Jose probe in 1,443 ms on average, and 1 check in 20 took longer than 2,313 ms.
Ranked by average response time across the 4 cities we check Zwift from, Ashburn 1st, San Jose 2nd; Ashburn was fastest at 969 ms and Tokyo slowest at 2,881 ms.
From Ashburn and San Jose we ran 760 checks of Zwift in 4 days, and 758 answered cleanly: 99.73% availability.
1 of the 4 days had at least one failed check. The weakest was Nov 4 (UTC), at 99.17% across 243 checks.
In Ashburn local time (EST), Zwift was slowest around 8 AM, at 1,552 ms on average over the last 14 days, and quickest around 9 AM, at 676 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 180 | 100.00% | 1,038 ms |
| Wed, Nov 4 | 243 | 99.17% | 1,309 ms |
| Tue, Nov 3 | 238 | 100.00% | 1,145 ms |
| Mon, Nov 2 | 99 | 100.00% | 1,121 ms |
Zwift outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Zwift outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Zwift from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 93 checks |
| Tokyo | Checks passing | 100.00% of 56 checks |
Other countries we check Zwift from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Zwift's public endpoints. They are not user reports, and they are not Zwift's own status page.
See Zwift's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Zwift has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter