Fitabase Status

All Systems Operational

About This Site

Keep an eye here for any issue related to Fitabase's operational status. If you are observing odd behavior and it isn't listed on this page, please email us so we can investigate: support@fitabase.com.

Web App Operational

Fitbit Syncing Operational

API Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Apr 20, 2025

No incidents reported today.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025

No incidents reported.

Apr 16, 2025

No incidents reported.

Apr 15, 2025

No incidents reported.

Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

Apr 11, 2025

No incidents reported.

Apr 10, 2025

Delays in Fitbit data

Resolved - 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.
Apr 10, 14:31 PDT

Monitoring - 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.
Apr 9, 12:49 PDT

Apr 9, 2025

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

Resolved - This incident has been resolved.
Apr 9, 13:26 PDT

Monitoring - 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.
Oct 11, 15:22 PDT

A select set of Fitbit profiles have missing data

Resolved - This incident has been resolved.
Apr 9, 13:25 PDT

Update - This incident has been resolved.
Apr 9, 13:25 PDT

Identified - 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.
Sep 13, 14:27 PDT

Fitbit incident causing delayed steps data

Resolved - This incident has been resolved.
Apr 9, 13:24 PDT

Monitoring - 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.
Nov 5, 09:41 PST

Investigating - 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.
Oct 30, 14:03 PDT

Apr 8, 2025

No incidents reported.

Apr 7, 2025

No incidents reported.

Apr 6, 2025

No incidents reported.