Fitabase Outage History

Fitabase is up right now

Fitabase had 4 outages in the last 2 years totaling 26h 31m of downtime — averaging 0.2 incidents per month.

There were 4 Fitabase outages since February 7, 2026 totaling 26h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fitabase.com

Major July 23, 2026

Intermittent Connectivity Issues

Detected by Pingoru
Jul 23, 2026, 06:37 PM UTC
Resolved
Jul 24, 2026, 02:32 AM UTC
Duration
7h 55m
Affected: Web AppFitbit SyncingAPI
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Critical July 15, 2026

Google has reported an outage affecting Sync functionality for all Google Health users.

Detected by Pingoru
Jul 15, 2026, 03:23 PM UTC
Resolved
Jul 15, 2026, 09:27 PM UTC
Duration
6h 4m
Affected: Fitbit Syncing
Timeline · 2 updates
  1. 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.

  2. resolved Jul 15, 2026, 09:27 PM UTC

    The outage has been resolved and all Fitbit data should now be caught up in Fitabase.

Read the full incident report →

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 →