Fitabase experienced a minor incident on May 24, 2017, lasting 26m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating May 24, 2017, 11:48 PM UTC
Starting at 4:40pm PDT Fitabase became unable to communicate to the Fitbit API for various requests. Data pulls are queued up and will resume once the issue has resolved. We will post here when we have more information.
- monitoring May 25, 2017, 12:13 AM UTC
The Fitbit API had a brief, full scope outage as reported here: http://www.fitbitstatus.com/incidents/glg4mzbdtm1q. Fitabase web app continues to run however some status indicators for device profiles will show "unable to communicate with Fitbit.com" or a similar warning. All new incoming data will be delayed.
- resolved May 25, 2017, 12:15 AM UTC
The Fitbit API was restored, all Fitabase services have resumed and all queued data pulls that failed during the brief window have now completed.