Duration: 27 minutes

Affected Components: ,

Sep 29, 15:30:00 GMT+0
Resolved - This incident is resolved. Between 15:03 and 15:19 UTC, a large share of data requests to the Terra API returned errors, and webhook deliveries were delayed. Webhooks queued during this period were delivered once service recovered, and data requests were slower than usual until 15:30 UTC. Some users connecting Apple Health during the incident may have needed to retry. If you notice gaps in data from this window, requesting that period again will return it. No action is needed..

Sep 29, 15:03:00 GMT+0
Investigating - We are investigating elevated errors on Terra API data requests and delayed webhook deliveries..

Duration: 3 hours

Affected Components:

Sep 23, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Sep 23, 05:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 21, 12:50:09 GMT+0
Identified - Polar has scheduled a maintenance break across all Polar services on Wednesday 23 September from 05:00 UTC. Polar expects up to 3 hours of downtime, followed by a few hours before its services are back to full speed. During this window, new Polar data may be delayed and new Polar connections may fail. Data recorded during the maintenance is expected to arrive once Polar's services recover, so no action is needed on your side. All other integrations are unaffected. Polar will post progress at https://status.polar.com..

Duration: 13 days, 10 hours and 31 minutes

Affected Components:

Sep 21, 21:00:00 GMT+0
Resolved - Requests to TrainerRoad are succeeding normally again, and authentication and data syncing for TrainerRoad users have been fully restored since 21 September at 21:00 UTC. Data delayed during the incident has been backfilled automatically, so no action is needed..

Sep 8, 10:28:54 GMT+0
Identified - API calls to TrainerRoad's server are failing at a high rate, impairing authentication & data fetching for users..

Duration: 18 hours and 46 minutes

Affected Components:

Sep 2, 15:50:44 GMT+0
Resolved - Fitbit's API has been stable since 21:30 UTC on 1 September and Fitbit data has been delivering normally since..

Sep 1, 21:48:47 GMT+0
Monitoring - Fitbit's API recovered at around 21:30 UTC and new Fitbit data is flowing normally again. We're monitoring while recent data works through..

Sep 1, 21:04:24 GMT+0
Identified - We're seeing elevated errors from Fitbit's API. New Fitbit data may be delayed or missing while this continues. Existing connections are unaffected and no action is needed..

Affected Components:

Sep 21, 17:01:28 GMT+0
Identified - Since approximately 14:40 UTC today, incoming Garmin data has stopped arriving for most connections, both new and existing. Historical data requests and planned workout delivery remain impacted as before. We are assessing our next escalation steps with Garmin. We do not have an ETA to provide yet..

Sep 10, 10:40:41 GMT+0
Monitoring - There is no material change to report at this time. New and existing Garmin connections continue to receive incoming data; however, historical data requests and planned workout delivery remain impacted. We are continuing to work with Garmin and will provide further updates here..

Sep 8, 21:54:44 GMT+0
Monitoring - There is no material change to report at this time. New and existing Garmin connections continue to receive incoming data; however, historical data requests and planned workout delivery remain impacted. We are continuing to work with Garmin and will provide further updates here..

Sep 7, 09:09:50 GMT+0
Identified - There is no material change to report at this time. New and existing Garmin connections continue to receive incoming data; however, historical data requests and planned workout delivery remain impacted. We are continuing to work with Garmin and will provide further updates here..

Sep 5, 21:44:44 GMT+0
Monitoring - There is no material change to report at this time. New and existing Garmin connections continue to receive incoming data; however, historical data requests and planned workout delivery remain impacted. We are continuing to work with Garmin and will provide further updates here..

Sep 4, 14:10:49 GMT+0
Identified - Garmin is changing its API terms and the way partners access its APIs. We do not have an ETA yet, but we will update this page at least once every calendar day, even if there is no change. Once Garmin restores access, we will backfill the historical data missed during this period. Planned workout pushes cannot be resynced automatically, and we are working on a feature to requeue the affected pushes..

Sep 2, 19:25:43 GMT+0
Identified - New Garmin connections can be established again, and incoming data for new and existing connections is being delivered. Historical data requests and planned workout delivery to Garmin devices remain impacted for all connections while we await confirmation from Garmin. A further update will follow..

Sep 2, 12:38:34 GMT+0
Identified - We are awaiting a response from Garmin. New Garmin connections cannot be established, and planned workout delivery to Garmin devices is impacted for all users, including existing connections. Incoming data from existing connections is unaffected and continues to be delivered. A further update will follow once we receive confirmation from Garmin..

Sep 1, 19:40:00 GMT+0
Investigating - Garmin's API began rejecting authorization requests at 19:40 UTC. New Garmin connections are failing; already-connected users are unaffected and their data continues to flow. Resolving this depends on Garmin. We're in direct contact with them and will update here..

Affected Components:

Sep 2, 11:21:00 GMT+0
Resolved - Nutracheck login recovered and new connections are completing normally again..

Aug 29, 18:05:20 GMT+0
Resolved - Between 18:05 UTC on 29 August and 11:21 UTC on 2 September, Nutracheck's login page returned errors and new Nutracheck connections could not be completed. Already-connected users were unaffected and their data continued to flow. This has recovered and new connections are working normally again..

Duration: 2 hours and 38 minutes

Affected Components:

Aug 7, 03:46:00 GMT+0
Resolved - This incident is resolved. Between 01:08 and 03:46 UTC, requests authenticated with a Terra API key could fail with an authorization error. Your API keys were never changed or revoked - requests are succeeding again with no action needed. Provider connections and data delivery were unaffected and no data was lost..

Aug 7, 03:40:00 GMT+0
Identified - We have identified the cause and are applying a fix now. API keys have not been changed or revoked. Data from connected providers has continued to arrive throughout..

Aug 7, 01:08:00 GMT+0
Investigating - We are investigating elevated errors on the Terra API. Requests authenticated with a Terra API key may fail with an authorization error. Provider connections and incoming data are not affected..

Duration: 11 hours and 58 minutes

Affected Components:

Aug 6, 08:17:12 GMT+0
Resolved - This incident has been resolved..

Aug 5, 20:19:19 GMT+0
Identified - Concept2's API is currently returning errors, which is disrupting data sync for Concept2 connections. This is an issue on Concept2's side — Terra's systems are healthy. Syncs will resume automatically once Concept2 recovers; no action is needed on your end. We're monitoring and will post updates here..

Duration: 8 days, 11 hours and 9 minutes

Affected Components:

Jul 26, 00:07:08 GMT+0
Resolved - Delivery times have returned to normal. A backlog of earlier data is still being delivered and will complete over the next few hours..

Jul 25, 21:21:11 GMT+0
Monitoring - A fix has been deployed and delivery times are returning to normal. Some earlier data is still being delivered..

Jul 25, 20:55:19 GMT+0
Identified - A fix has been identified and is being rolled out..

Jul 25, 08:20:00 GMT+0
Identified - Garmin data is arriving later than usual. Other providers are unaffected and no data is being lost. We have identified the cause and are working on a fix..

Duration: 5 hours and 15 minutes

Affected Components:

Jul 15, 17:00:00 GMT+0
Resolved - Resolved. Fitbit's platform recovered and we processed the full backlog of notifications that accumulated during their outage. All delayed Fitbit data has been synced — nothing was lost. Catch-up completed by 17:00 UTC..

Jul 15, 14:27:36 GMT+0
Monitoring - Fitbit's API is responding normally again in our checks. We are now working through the large backlog of notifications that accumulated during the outage, so Fitbit data will catch up progressively over the next hours — newest data first for most users. No data was lost. Google's own status page still lists their incident as open; we'll resolve here once delivery is fully back to normal..

Jul 15, 13:12:22 GMT+0
Identified - Google, who operate the Fitbit platform, have confirmed an outage on their side affecting sync for all Fitbit users (their status page: https://status.healthapp.google.com/incidents/P9M1yCB8EG8EN5SyC6jA). Fitbit data delivery remains reduced until Google resolves the issue. Data during this window is delayed, not lost — it will sync automatically once their service recovers..

Jul 15, 11:45:10 GMT+0
Investigating - Fitbit's API is returning elevated errors, which is reducing Fitbit data delivery for some users. Data during this window will be delayed — it will sync automatically once Fitbit recovers. We're monitoring and will post updates here..

Duration: 15 days and 54 minutes

Affected Components:

Jul 17, 00:54:21 GMT+0
Resolved - Strava's new API access requirements have been in effect since July 2 and affected integrations have had time to complete the required updates. Closing this notice — if your Strava connection still shows issues, please reach out to support..

Jul 2, 00:00:00 GMT+0
Monitoring - Since July 2, Strava has begun requiring developers to maintain an active Strava subscription (Standard Tier, effective June 30). Applications without one receive an “Inactive” response from Strava and stop delivering new data. Existing data is unaffected. If your Strava data has stopped, ensure the Strava account that owns your application has an active subscription, then reactivate the app in Strava’s API settings. Strava’s full migration deadline is September 1..

Duration: 2 hours and 50 minutes

Affected Components: ,

Jun 19, 21:55:00 GMT+0
Resolved - Service has recovered. Data during this incident was delayed, not lost, and has been delivered. We are adding stronger saturation alerting and capacity guardrails so this class of issue is caught earlier..

Jun 19, 20:15:00 GMT+0
Identified - We identified saturation in a database used by our connection and configuration service. We are restarting it and increasing its capacity..

Jun 19, 19:05:00 GMT+0
Investigating - We are investigating degraded API performance. Some requests are returning errors or timing out, and some data deliveries are delayed..

Duration: 5 days and 18 hours

Affected Components:

Jun 24, 12:00:00 GMT+0
Resolved - Polar data delivery has returned to normal. Real-time updates during this period were delayed; the underlying data remains available from Polar and can be re-synced..

Jun 23, 09:00:00 GMT+0
Monitoring - Polar data volumes are recovering as their fixes roll out and users update the Polar app..

Jun 19, 10:00:00 GMT+0
Identified - This is an upstream issue on Polar's side. Polar has confirmed synchronization problems in their mobile app affecting activity data and webhook delivery for a subset of users. Historical data remains available from Polar..

Jun 18, 18:00:00 GMT+0
Investigating - We're seeing reduced, delayed activity data from Polar. Real-time updates for some Polar users are arriving late or not at all..

Duration: 16 minutes

Affected Components:

Jun 5, 15:45:00 GMT+0
Resolved - API availability has been restored after a deployment issue. The API was unavailable for approximately 16 minutes (15:29 to 15:45 UTC). We are adding additional deployment checks to reduce the risk of recurrence..

Jun 5, 15:29:00 GMT+0
Investigating - We are investigating elevated errors on the Terra API. Requests may fail during this period..

Duration: 2 days and 2 hours

Affected Components:

May 26, 06:00:00 GMT+0
Resolved - The backlog has been fully delivered. Data during this incident was delayed, not lost..

May 24, 14:00:00 GMT+0
Monitoring - Delivery of new events is back to normal speed. We are draining the remaining backlog; older events will arrive over the next hours..

May 24, 06:30:00 GMT+0
Identified - We identified a large delivery backlog caused by a queueing issue. New events are being prioritised while we work through the backlog..

May 24, 04:00:00 GMT+0
Investigating - We are investigating delayed webhook deliveries. Incoming data is being received and stored; delivery to your endpoints is running behind..