Fitabase Outage History

Microsoft Azure is experiencing an intermittent connectivity issue affecting several of the key resources Fitabase depends on. Most services remain active, however some users may see long hanging, emails from our systems delayed, and certain processes time out. Retrying may help. For more info you can visit: https://azure.status.microsoft/en-us/status We do not foresee any long term impact or data loss as a result, however if you are having an issue, you may need to wait until Microsoft has fully resolved their partial outage.

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.

Widespread incident across Fitbit services. See https://status.fitbit.com/incidents/bi5hhNWfdtHvtr28qA8u for more details and updates.

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.

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