Fitabase Outage History
Fitabase is up right nowPingoru has recorded 45 incidents for Fitabase: 5 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 12 of 720 (2%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 2 | 14 of 744 (2%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 4 of 526 (1%) |
Incidents, newest first
Major October 18, 2026 Fitbit API Connections Failing 3h 50m Web App
Started Oct 18, 2026, 06:01 PM UTC· resolved Oct 18, 2026, 09:51 PM UTC
- identified Oct 18, 2026, 06:01 PM UTC
Over the weekend, the Fitbit OAuth 2.0 connection flow began to fail, with a "403 Forbidden" error. This may be a temporary 'brown out' in preparation for the Google Health migration. Fitabase has filed a ticket with the Google Health team regardless. Customers needing to connect to the Fitbit API with intentions of concluding their studies before Oct 30th should reach out to [email protected] to be excluded from the automatic update scheduled this week. While we hope to mitigate this issue, starting this week, we will be removing the option for new connections to the Fitbit OAuth in favor of the Google OAuth.
- monitoring Oct 18, 2026, 08:55 PM UTC
A fix has been implemented and we're monitoring to make sure that the issue resolves for affected customers. Note: you may need to start an Incognito browser session or log out of each profile if you are attempting to connect multiple Google accounts one after another to Fitabase.
- resolved Oct 18, 2026, 09:51 PM UTC
New participant profiles are now connecting normally again.
Major July 23, 2026 Intermittent Connectivity Issues 7h 55m Web App, Fitbit Syncing, API
Started Jul 23, 2026, 06:37 PM UTC· resolved Jul 24, 2026, 02:32 AM UTC
- identified Jul 23, 2026, 06:37 PM UTC
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.
- resolved Jul 24, 2026, 02:32 AM UTC
All services were restored earlier today and Fitabase has confirmed all systems have now caught up and returned to normal states.
Critical July 15, 2026 Google has reported an outage affecting Sync functionality for all Google Health users. 6h 4m Fitbit Syncing
Started Jul 15, 2026, 03:23 PM UTC· resolved Jul 15, 2026, 09:27 PM UTC
- investigating Jul 15, 2026, 03:23 PM UTC
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.
- resolved Jul 15, 2026, 09:27 PM UTC
The outage has been resolved and all Fitbit data should now be caught up in Fitabase.
Major April 29, 2026 High rate of errors and connection failures to Fitbit API 12h 3m Web App, Fitbit Syncing, API
Started Apr 29, 2026, 02:20 PM UTC· resolved Apr 30, 2026, 02:24 AM UTC
- 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.
- 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.
Major February 7, 2026 Partial Outage Due to Latency in our Azure Storage Accounts 27m Web App, Fitbit Syncing, API
Started Feb 07, 2026, 10:17 AM UTC· resolved Feb 07, 2026, 10:44 AM UTC
- 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.
- resolved Feb 07, 2026, 10:44 AM UTC
This incident has been resolved and we will continue to monitor.
Major July 17, 2025 Major Fitbit Outage 4h 15m Web App, Fitbit Syncing, API
Started Jul 17, 2025, 12:43 PM UTC· resolved Jul 17, 2025, 04:58 PM UTC
- investigating Jul 17, 2025, 12:43 PM UTC
Fitbit is currently investigating a major outage in their system.
- resolved Jul 17, 2025, 04:58 PM UTC
Fitbit has resolved the issue. We have confirmed data is flowing successfully through our system.
Major June 12, 2025 Fitbit Services - Widespread incident across Fitbit services 1h 17m Fitbit Syncing
Started Jun 12, 2025, 08:27 PM UTC· resolved Jun 12, 2025, 09:44 PM UTC
- 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.
- resolved Jun 12, 2025, 09:44 PM UTC
Google reports that Fitbit services have been restored: https://status.fitbit.com/incidents/bi5hhNWfdtHvtr28qA8u
Minor April 9, 2025 Delays in Fitbit data 1d 1h Fitbit Syncing
Started Apr 09, 2025, 07:49 PM UTC· resolved Apr 10, 2025, 09:31 PM UTC
- 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.
- 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.
Minor October 30, 2024 Fitbit incident causing delayed steps data 160d 23h Fitbit Syncing
Started Oct 30, 2024, 09:03 PM UTC· resolved Apr 09, 2025, 08:24 PM UTC
- 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.
- 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.
- resolved Apr 09, 2025, 08:24 PM UTC
This incident has been resolved.