All Systems Operational

About This Site

Keep an eye here for any issue related to Fitabase's operational status. If you are observing odd behavior and it isn't listed on this page, please email us so we can investigate: support@fitabase.com.

Web App Operational
Fitbit Syncing Operational
API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Oct 19, 2026

No incidents reported today.

Oct 18, 2026

Resolved - New participant profiles are now connecting normally again.
Oct 18, 14:51 PDT
Monitoring - A fix has been implemented and we're monitoring to make sure that the issue resolves for affected customers. Note: you may need to start an Incognito browser session or log out of each profile if you are attempting to connect multiple Google accounts one after another to Fitabase.
Oct 18, 13:55 PDT
Identified - Over the weekend, the Fitbit OAuth 2.0 connection flow began to fail, with a "403 Forbidden" error. This may be a temporary 'brown out' in preparation for the Google Health migration. Fitabase has filed a ticket with the Google Health team regardless.

Customers needing to connect to the Fitbit API with intentions of concluding their studies before Oct 30th should reach out to support@fitabase.com to be excluded from the automatic update scheduled this week.

While we hope to mitigate this issue, starting this week, we will be removing the option for new connections to the Fitbit OAuth in favor of the Google OAuth.

Oct 18, 11:01 PDT

Oct 17, 2026

No incidents reported.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

No incidents reported.

Oct 14, 2026

No incidents reported.

Oct 13, 2026

No incidents reported.

Oct 12, 2026

No incidents reported.

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

No incidents reported.

Oct 6, 2026

No incidents reported.

Oct 5, 2026

No incidents reported.