Is Fitabase down?

Last checked 3m ago
Current status
Fitabase is up

No active incidents. All 3 components operational.

Fitabase is operational right now. Last checked 3m ago; the most recent incident resolved 15d ago.

Real-time Fitabase status, recent outages, and incident history: pulled directly from Fitabase's official status page at status.fitabase.com every 5 minutes. Pingoru tracks 3 Fitabase services and has captured 1 incident in the last 90 days (99.91% uptime). Get email, Slack, Discord, or webhook alerts the moment Fitabase reports a new incident, free for 3 monitors, no credit card.

Users who monitor Fitabase also follow these Analytics services: New Relic Grafana Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch FullStory View all 8,000+ providers
Fitabase uptime 99.91% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3h 50m
    Started Oct 18, 2026, 06:01 PM UTC · Resolved Oct 18, 2026, 09:51 PM UTC
    Web App
    Timeline · 3 updates
    • 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.

    Latest: New participant profiles are now connecting normally again.

Incident record

Since April 2026 · Statuspage by Atlassian · 3 components checked every 5 minutes
45incidents recorded
5last 12 months
1last 90 days
6 hourstypical duration, 12 months

The longest incident in the last year, High rate of errors and connection failures to Fitbit API on April 29, 2026, ran for 12 hours.

Most affected components, last 12 months

  • Fitbit Syncing4
  • Web App4
  • API3

Latest incidents

  • Fitbit API Connections Failing October 18, 2026 · 4 hours · major outage

    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…

  • Intermittent Connectivity Issues July 23, 2026 · 8 hours · major outage

    Microsoft Azure is experiencing an intermittent connectivity issue affecting several of the key resources Fitabase depends on. Most services remain active…

  • Google has reported an outage affecting Sync functionality for all Google Health users. July 15, 2026 · 6 hours · major outage

    Device sync and pairing are affected. It appears this is also impacting the ability to connect participants in Fitabase. We will monitor this issue and resolve…

Outage history

Past 90 days · 1 incident View full outage history →