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
Jul 26, 2024

No incidents reported today.

Jul 25, 2024

No incidents reported.

Jul 24, 2024

No incidents reported.

Jul 23, 2024

No incidents reported.

Jul 22, 2024

No incidents reported.

Jul 21, 2024

No incidents reported.

Jul 20, 2024

No incidents reported.

Jul 19, 2024

No incidents reported.

Jul 18, 2024

No incidents reported.

Jul 17, 2024
Resolved - We have completed backfilling the minute level steps, calories, intensity, and METs data for affected profiles. Customers should now see any missing data that would have been captured during 6/25-7/15. Please reach out to support@fitabase.com if you have any concerns about your data not appearing to be complete.
Jul 17, 16:01 PDT
Identified - There was an uncommunicated change applied on June 25th, 2024 in how the Fitbit API requires Fitabase to make minute-level data calls. We are updating our code to align with those new requirements and will be working over the next day or two to make sure the minute-level data is appearing into the platform.

Fitabase on July 15th, 2024 pushed a fix to backfill the minute-level data that was not showing up for actively-syncing participants.
The affected data is minute-level only for the following data types:
* Steps
* Intensity
* METs
* Calories

If you need to backfill this data urgently, you can navigate to an individual participant's sync dates (found within Participant Details) and without changing the sync dates, click "Update Sync Dates". This will run a backfill.

This week we will re-run data pulls for all active profiles during this time, so no additional steps are required by customers. Minute-level data for participants whose sync dates ended before June 25, 2024 should already be in the platform (as this API call change occurred after that date).

Jul 15, 16:59 PDT
Jul 16, 2024

No incidents reported.

Jul 15, 2024
Jul 14, 2024

No incidents reported.

Jul 13, 2024

No incidents reported.

Jul 12, 2024

No incidents reported.