We started checking Zwift on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Zwift reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Zwift's own status page declared. Below it, any public chatter we saw about Zwift and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Zwift's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Zwift in the last 24 hours, which is not evidence that nothing is wrong.
Zwift's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Zwift's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Zwift next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.78%
461
US-West
99.70%
336
Europe
100.00%
307
Asia-Pacific
99.46%
184
Their declared record
Zwift's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Zwift Slow Loading TimesMinor incident
Oct 20, 2026, 5:02 PM UTC to Oct 21, 2026, 12:45 PM UTC (19h 43m)resolved
their latest update (Oct 21, 2026, 12:45 PM UTC): This incident has been resolved.
Campaigns stopped rewarding Drops or XP from 16:30 PT on September 23rd through 12:30 PT on September 24thPartial outage
Sep 23, 2026, 11:30 PM UTC to Sep 23, 2026, 11:30 PM UTC (0 min)resolved
their latest update (Sep 23, 2026, 11:30 PM UTC): The below campaigns temporarily stopped rewarding Drops and/or XP for their respective milestones:
- Climb of the Week
- Indoor Outdoor Challenge
- Route of the Week
- Zwift Racing Powered by Dura-Ace
- Zwift Shorts
We are actively working to determine all impacted Zwifters and…
ZwiftPower OutageMajor outage
Sep 23, 2026, 1:35 PM UTC to Sep 23, 2026, 1:35 PM UTC (0 min)resolved
their latest update (Sep 23, 2026, 1:35 PM UTC): ZwiftPower was temporarily unavailable from 06:35AM PT until it was restored at 07:10AM PT after implementing a fix on our end.
Timeout errors when trying to access ZwiftPowerMajor outage
Sep 21, 2026, 9:43 PM UTC to Sep 22, 2026, 3:43 AM UTC (6h)resolved
their latest update (Sep 22, 2026, 3:43 AM UTC): After additional backend changes access to ZwiftPower has now been fully restored.
Outage impacting importing external activities from Garmin, Hammerhead, Wahoo, and WhoopPartial outage
Sep 17, 2026, 4:18 PM UTC to Sep 18, 2026, 4:00 PM UTC (23h 42m)resolved
their latest update (Sep 18, 2026, 4:00 PM UTC): All Wahoo, Hammerhead, and Garmin data has been reprocessed. Due to limitations when fetching Garmin data and if Zwifters have only granted Zwift limited permissions to their Garmin account then they may need to disconnect and reconnect their Garmin accounts to pull in any missin…
Issues with saving activities and giving Ride OnsMajor outage
Aug 5, 2026, 4:13 PM UTC to Aug 5, 2026, 4:13 PM UTC (0 min)resolved
their latest update (Aug 5, 2026, 4:13 PM UTC): From approximately 9:13AM (PDT) to 10:13AM (PDT) we discovered there was an issue preventing activities from successfully saving, and giving other Zwifters Ride Ons. These issue should now be resolved.
Issues Loading Zwift EventsMinor incident
Jun 30, 2026, 4:20 PM UTC to Jul 10, 2026, 7:16 PM UTC (10d 2h)resolved
their latest update (Jul 10, 2026, 7:16 PM UTC): This incident has been resolved.
Zwift Companion Server IssueAll systems operational
Jun 2, 2026, 4:30 PM UTC to Jun 2, 2026, 4:51 PM UTC (21 min)resolved
their latest update (Jun 2, 2026, 4:51 PM UTC): This incident has been resolved.
RoboPacers restarting and disappearingAll systems operational
May 23, 2026, 12:47 AM UTC to May 23, 2026, 8:03 PM UTC (19h 15m)resolved
their latest update (May 23, 2026, 8:03 PM UTC): This incident has been resolved.
RoboPacer outageAll systems operational
May 22, 2026, 7:30 PM UTC to May 22, 2026, 7:30 PM UTC (0 min)resolved
their latest update (May 22, 2026, 7:30 PM UTC): We are investigating an intermittent outage of RoboPacers.
Showing the 10 most recent of 50 incidents Zwift has declared in the history we hold.
These entries are Zwift's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Zwift's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.