Fitabase incident

Delay in Fitbit Data

Critical Resolved View vendor source →

Fitabase experienced a critical incident on February 6, 2020 affecting Fitbit Syncing, lasting 9h 14m. The incident has been resolved; the full update timeline is below.

Started
Feb 06, 2020, 04:10 AM UTC
Resolved
Feb 06, 2020, 01:25 PM UTC
Duration
9h 14m
Detected by Pingoru
Feb 06, 2020, 04:10 AM UTC

Affected components

Fitbit Syncing

Update timeline

  1. identified Feb 06, 2020, 04:10 AM UTC

    Fitbit's Subscription / PubSub system that notifies third parties of new available data appears to be having intermittent issues preventing Fitabase from getting all new notifications for new data. We have alerted Fitbit's engineering. No data loss is expected however data parity may be delayed as much as 2 hours.

  2. resolved Feb 06, 2020, 01:25 PM UTC

    This incident has been resolved.