Time: Nov. 5, 2024, 5:41 p.m.

Status: Monitoring

Update: A fix has been implemented 11/01 that resolved the issue of retrieving data. We are monitoring the fix and implementing a solution for any profiles that were affected by the issue.

Time: Oct. 30, 2024, 9:03 p.m.

Status: Investigating

Update: The Fitbit API is experiencing an issue that has resulted in Fitabase being unable to retrieve minute-level steps data today (10/30). Fitbit is aware of the issue and investigating. We will update this incident with more information as it becomes available.

Time: Oct. 11, 2024, 10:22 p.m.

Status: Monitoring

Update: 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.

Time: Sept. 13, 2024, 9:27 p.m.

Status: Identified

Update: We're aware that after the partial outage last week, a few profiles have missing data within a few key daily value fields. We are working to fully identify the affected profiles, working with Fitbit's team, and once fully scoped we will backfill missing values of affected profiles.

Time: Sept. 6, 2024, 7:21 p.m.

Status: Resolved

Update: 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.

Time: Sept. 5, 2024, 2:57 p.m.

Status: Monitoring

Update: A fix has been implemented by Fitbit and data is flowing again. We are currently monitoring the fix.

Time: Sept. 4, 2024, 8:47 p.m.

Status: Investigating

Update: We are working with Fitbit to resolve an issue that is affecting our ability to pull in existing Fitbit data. Expect delays in the current Fitbit data being captured.

Time: Sept. 6, 2024, 7:21 p.m.

Status: Resolved

Update: 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.

Time: Sept. 5, 2024, 2:57 p.m.

Status: Monitoring

Update: A fix has been implemented by Fitbit and data is flowing again. We are currently monitoring the fix.

Time: Sept. 3, 2024, 8:41 p.m.

Status: Identified

Update: 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

Time: Sept. 3, 2024, 2:54 a.m.

Status: Identified

Update: 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.

Time: Aug. 30, 2024, 8:31 p.m.

Status: Investigating

Update: 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.