Fitabase incident

Some Fitbit profiles delay beginning their synchronizing of data on connection.

Minor Resolved View vendor source →

Fitabase experienced a minor incident on October 11, 2024 affecting Fitbit Syncing, lasting 179d 22h. The incident has been resolved; the full update timeline is below.

Started
Oct 11, 2024, 10:22 PM UTC
Resolved
Apr 09, 2025, 08:26 PM UTC
Duration
179d 22h
Detected by Pingoru
Oct 11, 2024, 10:22 PM UTC

Affected components

Fitbit Syncing

Update timeline

  1. monitoring Oct 11, 2024, 10:22 PM UTC

    When a new Fitbit profile is connected to a Fitabase participant portal, regular data delivery may be delayed to Fitabase by as much as 12 hours. We have identified examples of situations where Fitbit's subscription service is correctly registered by 3rd party applications, but does not immediately begin. In this scenario our dashboards will show "No Device Sync Yet" even though the profile is set up correctly. Once the delay passes, syncing does appear to follow normal behavior. Important note to customers: While we investigate this, be assured that we do not see any opportunity for data loss as the data is being correctly delivered to Fitbit's servers. The delay is the notifications that Fitabase needs to receive to trigger our timely synchronization. All examples of this have self-corrected after a number of hours and all unpulled data was correctly retrieved.

  2. resolved Apr 09, 2025, 08:26 PM UTC

    This incident has been resolved.