Skip to content

Outage tracker / Zwift

Is Zwift down?

I'm having a problem

Vendor reports no incidentWhat Zwift reports

Zwift reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:39 UTC.

Zwift's status page

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 passingchecked 1 minute ago

Our checks of Zwift pass from all 4 regions we check.

As of Nov 5, 2026, 3:40 PM UTC, RealUptime's checks of Zwift passed in all 4 regions that returned a reading.

Front-door checks

Email me when Zwift reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Zwift's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 5, 2026, 3:40 PM UTC
US-East491 msChecks passing
US-West1137 msChecks passing
Europe1202 msChecks passing
Asia-Pacific5245 msChecks passing
their status pagetheir claim, not our reading

Zwift reports: All systems operational (“All Systems Operational”)

from Zwift's own status page, checked Nov 5, 2026, 3:13 PM UTC
Zwift's own status page shows no incident, and our checks of Zwift pass right now.

Zwift's own component breakdown, as they publish it

  • RideOperational
  • EventsOperational
  • WorkoutsOperational
  • Zwift CompanionOperational
  • Zwift.comOperational
  • Existing Partner Connections (Importing Workouts & Uploading Zwift Activities)Operational
  • Support PageOperational
  • ZwiftPowerOperational
  • ActivitiesOperational
  • Log InOperational
  • Zwift ShopOperational
  • Campaign ProgressOperational
  • Payment ProcessingOperational
  • Zwift ForumsOperational
  • Account CreationOperational
  • Activity FeedOperational
  • RoboPacersOperational
  • New Partner ConnectionsOperational

These are Zwift's components, named and scored by Zwift. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Zwift's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Zwift response time, by region

US-East
1.2sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-West
1.9sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Europe
3.7sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 3.7s
Oct 7Oct 21Nov 5
Asia-Pacific
4.9sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 4.9s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 6.0s2026-11-05 UTC: p95 4.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on Zwift

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Zwift. It cannot diagnose Zwift's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 491msstatus code: 200checked: Nov 5, 2026, 3:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Zwift normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1137msstatus code: 200checked: Nov 5, 2026, 3:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Zwift normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionZwift is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionZwift is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionZwift is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 1202msstatus code: 200checked: Nov 5, 2026, 3:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Zwift normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionZwift is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 5245msstatus code: 200checked: Nov 5, 2026, 3:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Zwift normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionZwift is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionZwift is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Zwift, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Zwift yet, which is not evidence that nothing is wrong.

Recent probe events

Zwift Slow Loading Times, 19h 43mdeclared on their status page2026-10-20
Campaigns stopped rewarding Drops or XP from 16:30 PT on September 23rd through 12:30 PT on September 24th, 1mdeclared on their status page2026-09-23
ZwiftPower Outage, 1mdeclared on their status page2026-09-23
Timeout errors when trying to access ZwiftPower, 6hdeclared on their status page2026-09-21
Outage impacting importing external activities from Garmin, Hammerhead, Wahoo, and Whoop, 23h 42mdeclared on their status page2026-09-17
Issues with saving activities and giving Ride Ons, 1mdeclared on their status page2026-08-05
Issues Loading Zwift Events, 242h 56mdeclared on their status page2026-06-30
Zwift Companion Server Issue, 21mdeclared on their status page2026-06-02

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Zwift since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Zwift covering any window you pick, with our check readings and Zwift's own claim at the time, side by side.

Full check history for Zwift: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Zwift uptime by RealUptime's checksLive, from this page's own readings.
[![Zwift uptime by RealUptime's checks](https://realuptime.io/outages/zwift/badge.svg?days=30)](https://realuptime.io/outages/zwift)
<a href="https://realuptime.io/outages/zwift"><img src="https://realuptime.io/outages/zwift/badge.svg?days=30" alt="Zwift uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Zwift down?", https://realuptime.io/outages/zwift. The readings change with every check, so give the date you read them.

What we check

primary
https://www.zwift.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.zwift.com

RealUptime is not affiliated with Zwift; the name identifies what we checked, and nothing here speaks for Zwift's own team. We send a single web request to Zwift from 4 regions on our own schedule and time the response. We do not see inside Zwift's systems, do not use an account or real transaction, and are not the same signal Zwift's own team has access to. Treat this as one external data point, not a verdict. What we check for Zwift is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Zwift operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1183 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.