Fitabase incident

Intermittent Connection Errors to Fitbit API

Notice Resolved View vendor source →

Fitabase experienced a notice incident on May 10, 2017, lasting 3d 2h. The incident has been resolved; the full update timeline is below.

Started
May 10, 2017, 05:48 PM UTC
Resolved
May 13, 2017, 08:39 PM UTC
Duration
3d 2h
Detected by Pingoru
May 10, 2017, 05:48 PM UTC

Update timeline

  1. monitoring May 10, 2017, 05:48 PM UTC

    We are monitoring high rates of error connections to the Fitbit API. This may delay data availability in Fitabase temporarily. Additionally you may track this at http://www.fitbitstatus.com/incidents/wcvk17p04t8q

  2. resolved May 13, 2017, 08:39 PM UTC

    Connections to Fitbit's API have resumed at normal success rates. It was determined that gradual rollouts of updates to CloudFlare, the proxy in front of the Fitbit API were the root cause.