Fitabase Outage History

Fitabase is up right now

Fitabase had 11 outages in the last 2 years totaling 13476h 34m of downtime — averaging 0.5 incidents per month.

There were 11 Fitabase outages since July 15, 2024 totaling 13476h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fitabase.com

Major April 29, 2026

High rate of errors and connection failures to Fitbit API

Detected by Pingoru
Apr 29, 2026, 02:20 PM UTC
Resolved
Apr 30, 2026, 02:24 AM UTC
Duration
12h 3m
Affected: Web AppFitbit SyncingAPI
Timeline · 2 updates
  1. identified Apr 29, 2026, 02:20 PM UTC

    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.

  2. resolved Apr 30, 2026, 02:24 AM UTC

    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.

Read the full incident report →

Major February 7, 2026

Partial Outage Due to Latency in our Azure Storage Accounts

Detected by Pingoru
Feb 07, 2026, 10:17 AM UTC
Resolved
Feb 07, 2026, 10:44 AM UTC
Duration
27m
Affected: Web AppFitbit SyncingAPI
Timeline · 2 updates
  1. monitoring Feb 07, 2026, 10:17 AM UTC

    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.

  2. resolved Feb 07, 2026, 10:44 AM UTC

    This incident has been resolved and we will continue to monitor.

Read the full incident report →

Major July 17, 2025

Major Fitbit Outage

Detected by Pingoru
Jul 17, 2025, 12:43 PM UTC
Resolved
Jul 17, 2025, 04:58 PM UTC
Duration
4h 15m
Affected: Web AppFitbit SyncingAPI
Timeline · 2 updates
  1. investigating Jul 17, 2025, 12:43 PM UTC

    Fitbit is currently investigating a major outage in their system.

  2. resolved Jul 17, 2025, 04:58 PM UTC

    Fitbit has resolved the issue. We have confirmed data is flowing successfully through our system.

Read the full incident report →

Major June 12, 2025

Fitbit Services - Widespread incident across Fitbit services

Detected by Pingoru
Jun 12, 2025, 08:27 PM UTC
Resolved
Jun 12, 2025, 09:44 PM UTC
Duration
1h 17m
Affected: Fitbit Syncing
Timeline · 2 updates
  1. identified Jun 12, 2025, 08:27 PM UTC

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

  2. resolved Jun 12, 2025, 09:44 PM UTC

    Google reports that Fitbit services have been restored: https://status.fitbit.com/incidents/bi5hhNWfdtHvtr28qA8u

Read the full incident report →

Minor April 9, 2025

Delays in Fitbit data

Detected by Pingoru
Apr 09, 2025, 07:49 PM UTC
Resolved
Apr 10, 2025, 09:31 PM UTC
Duration
1d 1h
Affected: Fitbit Syncing
Timeline · 2 updates
  1. monitoring Apr 09, 2025, 07:49 PM UTC

    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.

  2. resolved Apr 10, 2025, 09:31 PM UTC

    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.

Read the full incident report →

Minor October 30, 2024

Fitbit incident causing delayed steps data

Detected by Pingoru
Oct 30, 2024, 09:03 PM UTC
Resolved
Apr 09, 2025, 08:24 PM UTC
Duration
160d 23h
Affected: Fitbit Syncing
Timeline · 3 updates
  1. investigating Oct 30, 2024, 09:03 PM UTC

    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.

  2. monitoring Nov 05, 2024, 05:41 PM UTC

    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.

  3. resolved Apr 09, 2025, 08:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 11, 2024

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

Detected by Pingoru
Oct 11, 2024, 10:22 PM UTC
Resolved
Apr 09, 2025, 08:26 PM UTC
Duration
179d 22h
Affected: Fitbit Syncing
Timeline · 2 updates
  1. monitoring Oct 11, 2024, 10:22 PM UTC

    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.

  2. resolved Apr 09, 2025, 08:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 13, 2024

A select set of Fitbit profiles have missing data

Detected by Pingoru
Sep 13, 2024, 09:27 PM UTC
Resolved
Apr 09, 2025, 08:25 PM UTC
Duration
207d 22h
Affected: Fitbit Syncing
Timeline · 3 updates
  1. identified Sep 13, 2024, 09:27 PM UTC

    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.

  2. identified Apr 09, 2025, 08:25 PM UTC

    This incident has been resolved.

  3. resolved Apr 09, 2025, 08:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 4, 2024

Delays in Current Fitbit Data

Detected by Pingoru
Sep 04, 2024, 08:47 PM UTC
Resolved
Sep 06, 2024, 07:21 PM UTC
Duration
1d 22h
Affected: Fitbit SyncingAPI
Timeline · 3 updates
  1. investigating Sep 04, 2024, 08:47 PM UTC

    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.

  2. monitoring Sep 05, 2024, 02:57 PM UTC

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

  3. resolved Sep 06, 2024, 07:21 PM UTC

    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.

Read the full incident report →

Major August 30, 2024

Subset of Profiles Missing Calorie, Intensity, and MET Data

Detected by Pingoru
Aug 30, 2024, 08:31 PM UTC
Resolved
Sep 06, 2024, 07:21 PM UTC
Duration
6d 22h
Affected: Fitbit SyncingAPI
Timeline · 5 updates
  1. investigating Aug 30, 2024, 08:31 PM UTC

    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.

  2. identified Sep 03, 2024, 02:54 AM UTC

    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.

  3. identified Sep 03, 2024, 08:41 PM UTC

    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

  4. monitoring Sep 05, 2024, 02:57 PM UTC

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

  5. resolved Sep 06, 2024, 07:21 PM UTC

    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.

Read the full incident report →