Fitabase incident

Fitbit API SSL Certificate Expired - Data Delays

Notice Resolved View vendor source →

Fitabase experienced a notice incident on September 27, 2017, lasting 13m. The incident has been resolved; the full update timeline is below.

Started
Sep 27, 2017, 01:36 PM UTC
Resolved
Sep 27, 2017, 01:50 PM UTC
Duration
13m
Detected by Pingoru
Sep 27, 2017, 01:36 PM UTC

Update timeline

  1. identified Sep 27, 2017, 01:36 PM UTC

    Fitbit is reporting that all calls to their API fail due to an expired *.fitbit.com SSL certificate. http://www.fitbitstatus.com/incidents/qb56ysy215wz Data will be delayed showing up in Fitabase until this is resolved.

  2. resolved Sep 27, 2017, 01:50 PM UTC

    API Connection from Fitabase to Fitbit are succeeding and all queued up data sync operations have been retried and succeeded. We'll continue to monitor the connection.