Fitabase incident

High rate of errors and connection failures to Fitbit API

Major Resolved View vendor source →

Fitabase experienced a major incident on April 29, 2026 affecting Web App and Fitbit Syncing and 1 more component, lasting 12h 3m. The incident has been resolved; the full update timeline is below.

Started
Apr 29, 2026, 02:20 PM UTC
Resolved
Apr 30, 2026, 02:24 AM UTC
Duration
12h 3m
Detected by Pingoru
Apr 29, 2026, 02:20 PM UTC

Affected components

Web AppFitbit SyncingAPI

Update timeline

  1. identified Apr 29, 2026, 02:20 PM UTC

    Fitabase is temporarily unable to connect with the Fitbit API for many profiles. We're working with our engineering contacts at Google / Fitbit to help identify the issue.

  2. resolved Apr 30, 2026, 02:24 AM UTC

    The issue has been resolved. Today we worked closely with the team at Google to identify the issue and once it was resolved, we re-queued data pulls into Fitabase. That has now completed. Any profiles connected during the outage should now have missing data filled in.