User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Sports
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 3 min ago. Last stored result reached it in 306 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 168 ms | 0 |
| Mon 22 | 0 | 0.0 | 414 ms | 0 |
| Tue 00 | 0 | 0.0 | 452 ms | 0 |
| Tue 02 | 0 | 0.0 | 306 ms | 0 |
| Tue 04 | 0 | 0.0 | 216 ms | 0 |
| Tue 06 | 0 | 0.0 | 436 ms | 0 |
| Tue 08 | 0 | 0.0 | 407 ms | 0 |
| Tue 10 | 0 | 0.0 | 280 ms | 0 |
| Tue 12 | 0 | 0.0 | 379 ms | 0 |
| Tue 15 | 0 | 0.0 | 396 ms | 0 |
| Tue 17 | 0 | 0.0 | 400 ms | 0 |
| Tue 19 | 0 | 0.0 | 458 ms | 0 |
| Tue 22 | 0 | 0.0 | 315 ms | 0 |
| Wed 01 | 0 | 0.0 | 413 ms | 0 |
| Wed 03 | 0 | 0.0 | 194 ms | 0 |
| Wed 05 | 0 | 0.0 | 421 ms | 0 |
| Wed 07 | 0 | 0.0 | 321 ms | 0 |
| Wed 10 | 0 | 0.0 | 361 ms | 0 |
| Wed 12 | 0 | 0.0 | 557 ms | 0 |
| Wed 14 | 0 | 0.0 | 303 ms | 0 |
| Wed 16 | 0 | 0.0 | 465 ms | 0 |
| Wed 18 | 0 | 0.0 | 222 ms | 0 |
| Wed 20 | 0 | 0.0 | 416 ms | 0 |
| Wed 23 | 0 | 0.0 | 443 ms | 0 |
| Thu 01 | 0 | 0.0 | 492 ms | 0 |
| Thu 03 | 0 | 0.0 | 461 ms | 0 |
| Thu 05 | 0 | 0.0 | 418 ms | 0 |
| Thu 07 | 0 | 0.0 | 205 ms | 0 |
| Thu 09 | 0 | 0.0 | 407 ms | 0 |
| Thu 11 | 0 | 0.0 | 433 ms | 0 |
| Thu 13 | 0 | 0.0 | 418 ms | 0 |
| Thu 15 | 0 | 0.0 | 361 ms | 0 |
| Thu 17 | 0 | 0.0 | 222 ms | 0 |
| Thu 20 | 0 | 0.0 | 260 ms | 0 |
| Thu 22 | 0 | 0.0 | 320 ms | 0 |
| Fri 00 | 0 | 0.0 | 279 ms | 0 |
| Fri 02 | 0 | 0.0 | 332 ms | 0 |
| Fri 04 | 0 | 0.0 | 230 ms | 0 |
| Fri 06 | 0 | 0.0 | 500 ms | 0 |
| Fri 08 | 0 | 0.0 | 335 ms | 0 |
| Fri 10 | 0 | 0.0 | 316 ms | 0 |
| Fri 11 | 0 | 0.0 | 375 ms | 0 |
| Fri 13 | 0 | 0.0 | 390 ms | 0 |
| Fri 15 | 0 | 0.0 | 476 ms | 0 |
| Fri 17 | 0 | 0.0 | 380 ms | 0 |
| Fri 19 | 0 | 0.0 | 291 ms | 0 |
| Fri 21 | 0 | 0.0 | 306 ms | 0 |
| Fri 23 | 0 | 0.0 | 314 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Zwift yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Zwift goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zwift alerts to Slack, Discord or a webhook — free.
We track Zwift (zwift.com) as part of the Sports group. Zwift is a virtual cycling app that is transforming indoor cycling. Discover training plans, ride with friends from around the world, and workout anytime.
Zwift publishes an official status page at status.zwift.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with sports services: ticketing, team app and live-score pages slowing down around game time.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 346 ms average, 230–500 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Zwift incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
346 ms on average over the last 24 hours (230–500 ms).
Yes, at https://status.zwift.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For sports services, watch for ticketing, team app and live-score pages slowing down around game time. If many people report Zwift here at once, the problem is on Zwift's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Zwift. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.