Fitabase incident
Subset of Profiles Missing Calorie, Intensity, and MET Data
Fitabase experienced a major incident on August 30, 2024 affecting Fitbit Syncing and API, lasting 6d 22h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 30, 2024, 08:31 PM UTC
A subset of our profiles are not able to capture minute or hour level calories, intensity, or METs for Fitbit users. We are currently working with Fitbit to resolve this issue.
- identified Sep 03, 2024, 02:54 AM UTC
A subset of Fitbit profiles continue to return errors when retrieving data. Currently the datasets affected are minute (and hour) level calories, METs, and intensity, as well as Active Zone Minutes. We are working with our partners at Fitbit to resolve the issue and once normal operations have resumed Fitabase will initiate a re-pull of missing data for affected profiles.
- identified Sep 03, 2024, 08:41 PM UTC
We are continuing to work with Fitbit on a resolution to this issue. A related status post has now been issued by Fitbit here, for reference: https://status.fitbit.com/incidents/D6j3uhKPGKKsJjNoxsp7
- monitoring Sep 05, 2024, 02:57 PM UTC
A fix has been implemented by Fitbit and data is flowing again. We are currently monitoring the fix.
- resolved Sep 06, 2024, 07:21 PM UTC
We continue to monitor data coming in from Fitbit. At this point all customers should see the previously delayed data filled in. Please contact [email protected] with any concerns.