Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Zwift Outage History

Every past Zwift outage tracked by IsDown, with detection times, duration, and resolution details.

There were 81 Zwift outages since December 2017. The 7 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor June 2, 2026

June 2026: Zwift Companion Server Issue

Detected Jun 2, 2026 12:30 PM EDT · Resolved Jun 2, 2026 12:52 PM EDT · Duration 22 minutes

Zwift experienced a server issue affecting the Companion service where in-game chat was unavailable and RoboPacers failed to appear for some users. The incident was resolved after 22 minutes of investigation and troubleshooting.

Major May 22, 2026

May 2026: RoboPacers restarting and disappearing

Detected May 22, 2026 8:47 PM EDT · Resolved May 23, 2026 4:04 PM EDT · Duration about 19 hours

Zwift experienced a major incident where RoboPacers were restarting and disappearing, disrupting the automated pacing feature for users. The service disabled RoboPacers over the weekend while investigating the root cause of the degraded performance. The issue was resolved after 19.3 hours of investigation and remediation work.

Minor May 22, 2026

May 2026: RoboPacer outage

Detected May 22, 2026 3:30 PM EDT · Resolved May 22, 2026 8:47 PM EDT · Duration about 5 hours
Minor April 14, 2026

April 2026: Issue Accessing Support Site

Detected Apr 14, 2026 10:12 AM EDT · Resolved Apr 14, 2026 11:17 AM EDT · Duration about 1 hour

Zwift's support site experienced access issues for 1.1 hours, with users unable to load pages or experiencing intermittent availability. The team investigated the root cause and worked to restore service. The issue was resolved and the support site became fully accessible again.

Major April 10, 2026

April 2026: Activity Feed on Zwift.com showing "Oops! We hit a snag" message when viewing activity details

Detected Apr 10, 2026 12:52 PM EDT · Resolved Apr 10, 2026 3:32 PM EDT · Duration about 3 hours

Zwift's activity feed on Zwift.com experienced a major outage where users encountered "Oops! We hit a snag" error messages when trying to view activity details. The issue was resolved after 2.7 hours by implementing a rollback, with some intermittent issues occurring during the rollback process before full resolution.