Fitabase incident

High rate of errors and connection failures to Fitbit API

Major Resolved View vendor source →
Started
Apr 29, 2026, 02:20 PM UTC
Resolved
Apr 30, 2026, 02:24 AM UTC
Duration
12h 3m
Detected by Pingoru
Apr 29, 2026, 02:20 PM UTC

Affected components

Web AppFitbit SyncingAPI

Update timeline

  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.

Looking to track Fitabase downtime and outages?

Pingoru polls Fitabase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Fitabase reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Fitabase alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Fitabase for free

5 free monitors · No credit card required