Terra Status - Incident history https://status.tryterra.co Terra Fri, 7 Aug 2026 01:08:00 +0000 Elevated errors on API requests Type: Incident Duration: 2 hours and 38 minutes Affected Components: REST endpoints 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. 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, 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. Type: Incident

Duration: 2 hours and 38 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>01:08:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>03:40:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>03:46:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Fri, 7 Aug 2026 01:08:00 +0000 https://status.tryterra.co/incident/cmsifu7ig07ce1bn33plw9hb4 https://status.tryterra.co/incident/cmsifu7ig07ce1bn33plw9hb4 Concept2 Data Fetching Type: Incident Duration: 11 hours and 58 minutes Affected Components: Concept2 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. Aug 6, 08:17:12 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 11 hours and 58 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>20:19:19</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>08:17:12</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 5 Aug 2026 20:19:19 +0000 https://status.tryterra.co/incident/cmsgj5uav00fd0lqxn6b5xtr0 https://status.tryterra.co/incident/cmsgj5uav00fd0lqxn6b5xtr0 Delayed Garmin data delivery Type: Incident Duration: 8 days, 11 hours and 9 minutes Affected Components: Garmin 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. Jul 25, 20:55:19 GMT+0 - Identified - A fix has been identified and is being rolled out. 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 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. Type: Incident

Duration: 8 days, 11 hours and 9 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>08:20:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>20:55:19</var> GMT+0</small><br><strong>Identified</strong> - A fix has been identified and is being rolled out..</p> <p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>21:21:11</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been deployed and delivery times are returning to normal. Some earlier data is still being delivered..</p> <p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>00:07:08</var> GMT+0</small><br><strong>Resolved</strong> - Delivery times have returned to normal. A backlog of earlier data is still being delivered and will complete over the next few hours..</p> ]]> Sat, 25 Jul 2026 08:20:00 +0000 https://status.tryterra.co/incident/cms0radph0bw30kmtjf9uaps1 https://status.tryterra.co/incident/cms0radph0bw30kmtjf9uaps1 Degraded performance — Fitbit Type: Incident Duration: 5 hours and 15 minutes Affected Components: Fitbit 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. 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, 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, 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. Type: Incident

Duration: 5 hours and 15 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>11:45:10</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>13:12:22</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>14:27:36</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Wed, 15 Jul 2026 11:45:10 +0000 https://status.tryterra.co/incident/cmrm151d501gr1amtus4n16om https://status.tryterra.co/incident/cmrm151d501gr1amtus4n16om Strava API access changes for some integrations Type: Incident Duration: 15 days and 54 minutes Affected Components: Strava 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. 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. Type: Incident

Duration: 15 days and 54 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>00:54:21</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Thu, 2 Jul 2026 00:00:00 +0000 https://status.tryterra.co/incident/cmrf6t1q8095q1aq6hh0u8ud8 https://status.tryterra.co/incident/cmrf6t1q8095q1aq6hh0u8ud8 Degraded API performance and delayed data delivery Type: Incident Duration: 2 hours and 50 minutes Affected Components: Event Delivery, REST endpoints 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. Type: Incident

Duration: 2 hours and 50 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>21:55:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>20:15:00</var> GMT+0</small><br><strong>Identified</strong> - We identified saturation in a database used by our connection and configuration service. We are restarting it and increasing its capacity..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>19:05:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating degraded API performance. Some requests are returning errors or timing out, and some data deliveries are delayed..</p> ]]> Fri, 19 Jun 2026 19:05:00 +0000 https://status.tryterra.co/incident/cmrew43hj06oy0zmvtgmimlyb https://status.tryterra.co/incident/cmrew43hj06oy0zmvtgmimlyb Delayed Polar data delivery Type: Incident Duration: 5 days and 18 hours Affected Components: 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. 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 23, 09:00:00 GMT+0 - Monitoring - Polar data volumes are recovering as their fixes roll out and users update the Polar app. 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. Type: Incident

Duration: 5 days and 18 hours

Affected Components:

<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We're seeing reduced, delayed activity data from Polar. Real-time updates for some Polar users are arriving late or not at all..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - Polar data volumes are recovering as their fixes roll out and users update the Polar app..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Thu, 18 Jun 2026 18:00:00 +0000 https://status.tryterra.co/incident/cmrf6r15g01a90rmksatpixqp https://status.tryterra.co/incident/cmrf6r15g01a90rmksatpixqp API unavailable Type: Incident Duration: 16 minutes Affected Components: REST endpoints Jun 5, 15:29:00 GMT+0 - Investigating - We are investigating elevated errors on the Terra API. Requests may fail during this period. 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. Type: Incident

Duration: 16 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>15:29:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating elevated errors on the Terra API. Requests may fail during this period..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>15:45:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Fri, 5 Jun 2026 15:29:00 +0000 https://status.tryterra.co/incident/cmrew42dg039i0kt9kls2qsif https://status.tryterra.co/incident/cmrew42dg039i0kt9kls2qsif Delayed webhook deliveries Type: Incident Duration: 2 days and 2 hours Affected Components: Event Delivery 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. 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, 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 26, 06:00:00 GMT+0 - Resolved - The backlog has been fully delivered. Data during this incident was delayed, not lost. Type: Incident

Duration: 2 days and 2 hours

Affected Components:

<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating delayed webhook deliveries. Incoming data is being received and stored; delivery to your endpoints is running behind..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>06:30:00</var> GMT+0</small><br><strong>Identified</strong> - We identified a large delivery backlog caused by a queueing issue. New events are being prioritised while we work through the backlog..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - Delivery of new events is back to normal speed. We are draining the remaining backlog; older events will arrive over the next hours..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Resolved</strong> - The backlog has been fully delivered. Data during this incident was delayed, not lost..</p> ]]> Sun, 24 May 2026 04:00:00 +0000 https://status.tryterra.co/incident/cmrew40y306n60zq6a8xidjfd https://status.tryterra.co/incident/cmrew40y306n60zq6a8xidjfd