Fitabase had 11 outages in the last 2 years totaling 13435h 37m of downtime — averaging 0.5 incidents per month.
There were 11 Fitabase outages since August 30, 2024 totaling 13435h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
Device sync and pairing are affected. We will monitor this issue and resolve any impacted syncing data once Google reports the outage has been resolved.
The outage has been resolved and all Fitbit data should now be caught up in Fitabase.
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.
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.
We are currently seeing data delays and intermittent site loading issues. The issue lasted for about 1 hour and appears to be resolving. The underlying Azure Storage account service has been identified and Microsoft has acknowledged the issue and is actively working to resolve it.
This incident has been resolved and we will continue to monitor.
Fitbit is currently investigating a major outage in their system.
Fitbit has resolved the issue. We have confirmed data is flowing successfully through our system.
Widespread incident across Fitbit services. See https://status.fitbit.com/incidents/bi5hhNWfdtHvtr28qA8u for more details and updates.
Google reports that Fitbit services have been restored: https://status.fitbit.com/incidents/bi5hhNWfdtHvtr28qA8u
We are experiencing delays processing Fitbit data. All data has been queued and is now being processed into Fitabase. We will post an update as soon as data capture is caught up.
Data processing has been resolved. The issue was specifically with the HRV data set. Other data sets should not have been impacted. All data should sync and be available on Fitabase within the next 24 hours.
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.
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.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
This incident has been resolved.
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.
A fix has been implemented by Fitbit and data is flowing again. We are currently monitoring the fix.
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.
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.
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.
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
A fix has been implemented by Fitbit and data is flowing again. We are currently monitoring the fix.
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.