Gardin Status - Incident history https://status.gardin.ag Gardin Thu, 24 Sep 2026 09:30:00 +0000 Schedule Database Maintanance Type: Maintenance Duration: 6 hours and 30 minutes Affected Components: Query API, Reporting App (app.gardin.ag) Sep 21, 09:56:04 GMT+0 - Identified - We will be performing scheduled database maintenance on Thursday, September 24, 2026, starting at 10:30 AM BST. We expect the maintenance to take up to 6 hours. During this maintenance window: * New data will not be refreshed in the Gardin app until the database is back online. Historical data will still be available. * Any pending data will be processed afterward, so there will be no permanent data loss. * The Query API will be unavailable and will return HTTP 503 errors. Once the maintenance is complete and all systems are operational again, we will send another update. Thanks & Regards, Sep 24, 09:30:01 GMT+0 - Identified - Maintenance is now in progress Sep 24, 16:00:00 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 6 hours and 30 minutes

Affected Components: ,

<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>09:56:04</var> GMT+0</small><br><strong>Identified</strong> - We will be performing scheduled database maintenance on Thursday, September 24, 2026, starting at 10:30 AM BST. We expect the maintenance to take up to 6 hours. During this maintenance window: * New data will not be refreshed in the Gardin app until the database is back online. Historical data will still be available. * Any pending data will be processed afterward, so there will be no permanent data loss. * The Query API will be unavailable and will return HTTP 503 errors. Once the maintenance is complete and all systems are operational again, we will send another update. Thanks & Regards,.</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>09:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 24 Sep 2026 09:30:00 +0000 https://status.gardin.ag/maintenance/cmub2ldlu11ij0wmrmcenoidq https://status.gardin.ag/maintenance/cmub2ldlu11ij0wmrmcenoidq Index processing issues - EFFICIENCY and PRODUCTIVITY Type: Incident Duration: 9 hours and 45 minutes Affected Components: Reporting App (app.gardin.ag), Query API Feb 3, 10:50:57 GMT+0 - Investigating - We are currently experiencing issues with processing EFFICIENCY and PRODUCTIVITY indices data and the engineering team is fully engaged on providing a resolution as fast as possible. Please be assured that no data has been lost, and all historical data will be fully processed and made available via both the Gardin reporting app and the Query API as soon as possible. We sincerely apologise for any inconvenience this may cause and appreciate your patience as we work to resolve this issue swiftly. Feb 3, 14:45:36 GMT+0 - Identified - We have identified the root cause of this issue and are working with our cloud hosting provider to remediate as quickly as possible. Feb 3, 17:28:41 GMT+0 - Monitoring - We have applied a fix and are currently monitoring as normal service resumes for incoming data. We have also begun reprocessing affected historical data. Feb 3, 20:36:18 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 9 hours and 45 minutes

Affected Components: ,

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>10:50:57</var> GMT+0</small><br><strong>Investigating</strong> - We are currently experiencing issues with processing EFFICIENCY and PRODUCTIVITY indices data and the engineering team is fully engaged on providing a resolution as fast as possible. Please be assured that no data has been lost, and all historical data will be fully processed and made available via both the Gardin reporting app and the Query API as soon as possible. We sincerely apologise for any inconvenience this may cause and appreciate your patience as we work to resolve this issue swiftly..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>14:45:36</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause of this issue and are working with our cloud hosting provider to remediate as quickly as possible. .</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>17:28:41</var> GMT+0</small><br><strong>Monitoring</strong> - We have applied a fix and are currently monitoring as normal service resumes for incoming data. We have also begun reprocessing affected historical data..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>20:36:18</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 3 Feb 2025 10:50:57 +0000 https://status.gardin.ag/incident/cm6oxk46u0035cv8c7zjomyom https://status.gardin.ag/incident/cm6oxk46u0035cv8c7zjomyom Processing delays Type: Incident Duration: 2 days, 23 hours and 28 minutes Affected Components: Reporting App (app.gardin.ag), Query API Jan 13, 09:08:18 GMT+0 - Investigating - We are currently experiencing delays in processing index data and the engineering team is fully engaged on providing a resolution as fast as possible. Please be assured that no data has been lost, and all historical data will be fully processed and made available via both the Gardin reporting app and the Query API as soon as possible. We sincerely apologise for any inconvenience this may cause and appreciate your patience as we work to resolve this issue swiftly. Jan 13, 10:49:03 GMT+0 - Identified - We are continuing to work on a fix. Jan 13, 15:51:22 GMT+0 - Monitoring - We are writing to provide an update on the ongoing system performance issues. We have been in contact with our cloud computing provider, who are assisting us in diagnosing the root cause with the highest priority. We have started re-enabling the processing of indices data to customers and are actively working to resolve any remaining issues as quickly as possible. We sincerely apologise for the continued inconvenience and thank you for your patience as we address this matter. Jan 13, 19:58:49 GMT+0 - Monitoring - We are continuing to monitor the fix implemented by our engineering team and remain in close contact with our cloud computing provider whilst we complete the re-enablement of all tenant indices data streams. We are now targeting resumption of incoming indices data for all customers by lunchtime of Tuesday 14th Jan. Once this has been achieved, the reprocessing of historical data since 11th Jan will be undertaken. Jan 14, 12:26:13 GMT+0 - Monitoring - We are making good progress in continuing to restore customer indices data. We are implementing as quickly as possible an alternative architecture to address ongoing performance issues, and engineering teams are working with our cloud-hosting provider to deliver this as soon as possible. Jan 15, 08:27:58 GMT+0 - Monitoring - We are writing to provide an update on the ongoing system performance issues. In collaboration with our cloud-computing provider, we have now identified the underlying root cause and our engineering teams are working diligently on a permanent fix. We are targeting end of play today to have current incoming index data restored for all customers. We will then proceed with the restoration of missing historical data. We understand the impact this outage is having on our customers, and sincerely apologise. Jan 17, 17:21:00 GMT+0 - Resolved - Gardin takes issues and outages and their effect on our customers extremely seriously, and would like to express our sincere apologies for the inconvenience caused by this incident. We believe it is critical to be transparent and honest when things go wrong, so we can share our learnings and from this build better products. We wanted to provide you with some additional information about the service disruption that occurred on 13th January 2025. \-- ### Post-incident summary: Gardin Pulse data warehouse outage **What happened?** In the early hours of the morning on 11th Jan 2025, routine maintenance of our central data warehouse cluster was performed automatically by our cloud hosting provider. The maintenance completed without issue, with queued data processing workloads resuming shortly after. On the morning of 13th Jan, automated alarms alerted the Platform team to delays arising in data processing. A rapid triage investigation revealed that workloads were no longer being distributed evenly across the data warehouse cluster computing resources, leading to severe bottlenecking of compute capacity and consequently hindering the ability of the platform to process incoming data from customer sensor fleets in within the standard 15 minute latency window. A Priority 1 incident was declared by the Gardin Platform team at 07:00 UTC, and immediate response actions were taken. The cloud provider’s incident support team was engaged to investigate, and the Gardin Platform team attempted to rollback the cluster to its previous version in an attempt to restore previous behaviour. Unfortunately, this rollback process failed repeatedly and required further escalation to the cloud provider’s support team. While working on a resolution, the Platform team paused all processing jobs to stabilise the system and implemented a temporary mechanism to limit incoming workloads. This approach allowed live data processing to resume approximately 10 hours after the incident was declared. Throughout the incident, no data was lost as all incoming information was securely stored. Once the live data was restored, the team focused on back-processing the historical data that had been delayed. This process was carried out carefully, ensuring the system remained stable as workloads were gradually reintroduced. By 08:30 UTC on 17th Jan, all customer data was fully processed, and the system returned to normal operation. The incident was officially closed at 09:30 UTC. **Next steps/lessons learnt** 1. We continue to work extremely closely with our cloud hosting provider to understand the root cause of the performance issues that started following the managed maintenance work on the 11th Jan. 1. The platform team conducted an immediate review into the efficacy of automated system alerts and this highlighted that alerts could have been raised earlier in this situation had more appropriate monitoring of underlying cluster resource limit breaches been in place. This will now be implemented as a high priority. 2. The platform team has initiated a detailed review into the events leading up to the incident and the subsequent response/recovery process looking at both the technological and business process aspects to identify improvements which can be implemented. **In closing** We apologise for the impact this incident caused for our customers. While we are proud of our track record of availability, any outage is one too many, and we know this event impacted many customers in significant ways. We will do everything we can to learn from this event and use it to improve our availability even further. Jan 16, 08:36:13 GMT+0 - Resolved - We’re pleased to inform you that full service was successfully restored overnight, and we are now reprocessing the affected historical data to ensure everything is back to normal. Our focus is now shifting to thoroughly investigating how this incident occurred and identifying the lessons we can learn to prevent future disruptions. We are committed to transparency and will share a detailed post-incident review report with you via this status page once our analysis is complete. We sincerely apologise for the inconvenience caused and thank you for your patience and understanding as we work to make things right. Type: Incident

Duration: 2 days, 23 hours and 28 minutes

Affected Components: ,

<p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>09:08:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently experiencing delays in processing index data and the engineering team is fully engaged on providing a resolution as fast as possible. Please be assured that no data has been lost, and all historical data will be fully processed and made available via both the Gardin reporting app and the Query API as soon as possible. We sincerely apologise for any inconvenience this may cause and appreciate your patience as we work to resolve this issue swiftly..</p> <p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>10:49:03</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix..</p> <p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>15:51:22</var> GMT+0</small><br><strong>Monitoring</strong> - We are writing to provide an update on the ongoing system performance issues. We have been in contact with our cloud computing provider, who are assisting us in diagnosing the root cause with the highest priority. We have started re-enabling the processing of indices data to customers and are actively working to resolve any remaining issues as quickly as possible. We sincerely apologise for the continued inconvenience and thank you for your patience as we address this matter..</p> <p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>19:58:49</var> GMT+0</small><br><strong>Monitoring</strong> - We are continuing to monitor the fix implemented by our engineering team and remain in close contact with our cloud computing provider whilst we complete the re-enablement of all tenant indices data streams. We are now targeting resumption of incoming indices data for all customers by lunchtime of Tuesday 14th Jan. Once this has been achieved, the reprocessing of historical data since 11th Jan will be undertaken..</p> <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>12:26:13</var> GMT+0</small><br><strong>Monitoring</strong> - We are making good progress in continuing to restore customer indices data. We are implementing as quickly as possible an alternative architecture to address ongoing performance issues, and engineering teams are working with our cloud-hosting provider to deliver this as soon as possible..</p> <p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>08:27:58</var> GMT+0</small><br><strong>Monitoring</strong> - We are writing to provide an update on the ongoing system performance issues. In collaboration with our cloud-computing provider, we have now identified the underlying root cause and our engineering teams are working diligently on a permanent fix. We are targeting end of play today to have current incoming index data restored for all customers. We will then proceed with the restoration of missing historical data. We understand the impact this outage is having on our customers, and sincerely apologise..</p> <p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>17:21:00</var> GMT+0</small><br><strong>Resolved</strong> - Gardin takes issues and outages and their effect on our customers extremely seriously, and would like to express our sincere apologies for the inconvenience caused by this incident. We believe it is critical to be transparent and honest when things go wrong, so we can share our learnings and from this build better products. We wanted to provide you with some additional information about the service disruption that occurred on 13th January 2025. \-- ### Post-incident summary: Gardin Pulse data warehouse outage **What happened?** In the early hours of the morning on 11th Jan 2025, routine maintenance of our central data warehouse cluster was performed automatically by our cloud hosting provider. The maintenance completed without issue, with queued data processing workloads resuming shortly after. On the morning of 13th Jan, automated alarms alerted the Platform team to delays arising in data processing. A rapid triage investigation revealed that workloads were no longer being distributed evenly across the data warehouse cluster computing resources, leading to severe bottlenecking of compute capacity and consequently hindering the ability of the platform to process incoming data from customer sensor fleets in within the standard 15 minute latency window. A Priority 1 incident was declared by the Gardin Platform team at 07:00 UTC, and immediate response actions were taken. The cloud provider’s incident support team was engaged to investigate, and the Gardin Platform team attempted to rollback the cluster to its previous version in an attempt to restore previous behaviour. Unfortunately, this rollback process failed repeatedly and required further escalation to the cloud provider’s support team. While working on a resolution, the Platform team paused all processing jobs to stabilise the system and implemented a temporary mechanism to limit incoming workloads. This approach allowed live data processing to resume approximately 10 hours after the incident was declared. Throughout the incident, no data was lost as all incoming information was securely stored. Once the live data was restored, the team focused on back-processing the historical data that had been delayed. This process was carried out carefully, ensuring the system remained stable as workloads were gradually reintroduced. By 08:30 UTC on 17th Jan, all customer data was fully processed, and the system returned to normal operation. The incident was officially closed at 09:30 UTC. **Next steps/lessons learnt** 1. We continue to work extremely closely with our cloud hosting provider to understand the root cause of the performance issues that started following the managed maintenance work on the 11th Jan. 1. The platform team conducted an immediate review into the efficacy of automated system alerts and this highlighted that alerts could have been raised earlier in this situation had more appropriate monitoring of underlying cluster resource limit breaches been in place. This will now be implemented as a high priority. 2. The platform team has initiated a detailed review into the events leading up to the incident and the subsequent response/recovery process looking at both the technological and business process aspects to identify improvements which can be implemented. **In closing** We apologise for the impact this incident caused for our customers. While we are proud of our track record of availability, any outage is one too many, and we know this event impacted many customers in significant ways. We will do everything we can to learn from this event and use it to improve our availability even further..</p> <p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>08:36:13</var> GMT+0</small><br><strong>Resolved</strong> - We’re pleased to inform you that full service was successfully restored overnight, and we are now reprocessing the affected historical data to ensure everything is back to normal. Our focus is now shifting to thoroughly investigating how this incident occurred and identifying the lessons we can learn to prevent future disruptions. We are committed to transparency and will share a detailed post-incident review report with you via this status page once our analysis is complete. We sincerely apologise for the inconvenience caused and thank you for your patience and understanding as we work to make things right..</p> ]]> Mon, 13 Jan 2025 09:08:18 +0000 https://status.gardin.ag/incident/cm5utn7er008dg38b8fswwomb https://status.gardin.ag/incident/cm5utn7er008dg38b8fswwomb Processing delays - PPFD index Type: Incident Duration: 1 day, 5 hours and 47 minutes Affected Components: Reporting App (app.gardin.ag), Query API Nov 14, 14:05:29 GMT+0 - Resolved - The engineering team are pleased to confirm this incident has been resolved and all historical PPFD index data has been reprocessed and is now available via the Gardin Pulse reporting app and Query API. We again apologise for the inconvenience caused. Nov 13, 08:57:38 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 13, 08:18:11 GMT+0 - Investigating - We are currently experiencing delays in processing PPFD index data and the engineering team is fully engaged on providing a resolution as fast as possible. Please be assured that no data has been lost, and all historical data will be fully processed and made available via both the Gardin reporting app and the Query API as soon as possible. We sincerely apologise for any inconvenience this may cause and appreciate your patience as we work to resolve this issue swiftly. Nov 13, 17:32:29 GMT+0 - Identified - We apologise for the ongoing unavailability of PPFD index data. Our engineers have made significant progress on a permanent fix, which we aim to release tomorrow, Thursday 14th November 2024. Please rest assured that all data remains safe, and any missing historical data will be fully processed and made available via the Gardin Pulse reporting app and Query API as soon as possible. Thank you for your continued patience and understanding. Nov 14, 12:36:55 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 1 day, 5 hours and 47 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>14:05:29</var> GMT+0</small><br><strong>Resolved</strong> - The engineering team are pleased to confirm this incident has been resolved and all historical PPFD index data has been reprocessed and is now available via the Gardin Pulse reporting app and Query API. We again apologise for the inconvenience caused..</p> <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>08:57:38</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>08:18:11</var> GMT+0</small><br><strong>Investigating</strong> - We are currently experiencing delays in processing PPFD index data and the engineering team is fully engaged on providing a resolution as fast as possible. Please be assured that no data has been lost, and all historical data will be fully processed and made available via both the Gardin reporting app and the Query API as soon as possible. We sincerely apologise for any inconvenience this may cause and appreciate your patience as we work to resolve this issue swiftly..</p> <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>17:32:29</var> GMT+0</small><br><strong>Identified</strong> - We apologise for the ongoing unavailability of PPFD index data. Our engineers have made significant progress on a permanent fix, which we aim to release tomorrow, Thursday 14th November 2024. Please rest assured that all data remains safe, and any missing historical data will be fully processed and made available via the Gardin Pulse reporting app and Query API as soon as possible. Thank you for your continued patience and understanding..</p> <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>12:36:55</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Wed, 13 Nov 2024 08:18:11 +0000 https://status.gardin.ag/incident/cm3flztjq000ws64tsy3x7g5g https://status.gardin.ag/incident/cm3flztjq000ws64tsy3x7g5g Processing Delays - Indices Type: Incident Duration: 2 days, 7 hours and 25 minutes Affected Components: Reporting App (app.gardin.ag), Query API Nov 12, 06:42:55 GMT+0 - Investigating - Our data processing infrastructure is suffering an outage which is causing a delays in the processing of latest information in the reporting app and Query API. No data has been lost and the engineering team is actively investigating. We sincerely apologise for the inconvenience caused. Nov 12, 07:02:07 GMT+0 - Identified - We are engaged with our cloud services provider and have identified a fix that the engineering team is currently implementing. Nov 12, 09:48:17 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 12, 13:07:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 14, 14:07:26 GMT+0 - Resolved - The engineering team are pleased to confirm this incident has been resolved and all historical PPFD index data has been reprocessed and is now available via the Gardin Pulse reporting app and Query API. We again apologise for the inconvenience caused. Type: Incident

Duration: 2 days, 7 hours and 25 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>06:42:55</var> GMT+0</small><br><strong>Investigating</strong> - Our data processing infrastructure is suffering an outage which is causing a delays in the processing of latest information in the reporting app and Query API. No data has been lost and the engineering team is actively investigating. We sincerely apologise for the inconvenience caused..</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>07:02:07</var> GMT+0</small><br><strong>Identified</strong> - We are engaged with our cloud services provider and have identified a fix that the engineering team is currently implementing..</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>09:48:17</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>13:07:57</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>14:07:26</var> GMT+0</small><br><strong>Resolved</strong> - The engineering team are pleased to confirm this incident has been resolved and all historical PPFD index data has been reprocessed and is now available via the Gardin Pulse reporting app and Query API. We again apologise for the inconvenience caused..</p> ]]> Tue, 12 Nov 2024 06:42:55 +0000 https://status.gardin.ag/incident/cm3e35fs60002jhqhdc3rdmx5 https://status.gardin.ag/incident/cm3e35fs60002jhqhdc3rdmx5 Processing delays - Gardin Indices Type: Incident Duration: 3 hours and 44 minutes Affected Components: Reporting App (app.gardin.ag), Query API Nov 10, 08:56:00 GMT+0 - Identified - Our data processing infrastructure is running behind which is causing a delay in the availability of the latest Gardin indices information in the reporting app and via the Query API. The team is actively investigating. Nov 10, 09:06:13 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 10, 10:15:29 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 10, 12:40:09 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 44 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>08:56:00</var> GMT+0</small><br><strong>Identified</strong> - Our data processing infrastructure is running behind which is causing a delay in the availability of the latest Gardin indices information in the reporting app and via the Query API. The team is actively investigating..</p> <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>09:06:13</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>10:15:29</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>12:40:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 10 Nov 2024 08:56:00 +0000 https://status.gardin.ag/incident/cm3bcu73p000xyzlvtmp8fh0a https://status.gardin.ag/incident/cm3bcu73p000xyzlvtmp8fh0a Processing Delays Type: Incident Duration: 12 days, 5 hours and 21 minutes Affected Components: Reporting App (app.gardin.ag), Query API Oct 31, 10:39:58 GMT+0 - Investigating - Our data processing infrastructure is running behind which is causing a lack of latest information in the reporting app. No data has been lost and the team is actively investigating. Oct 31, 10:59:44 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 31, 12:31:07 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 31, 12:58:34 GMT+0 - Identified - Unfortunately, it's taking our teams longer than usual to fix this issue. All of the team are engaged on resolving this incident as soon as possible. All data collected since this incident started remains safe and will be processed as soon as possible. We sincerely apologise for the ongoing inconvenience. Oct 31, 21:11:05 GMT+0 - Resolved - This incident has been resolved. Nov 12, 13:07:33 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 12, 16:00:53 GMT+0 - Resolved - This incident has been resolved and we are reprocessing historical data over the last 24 hours. We sincerely apologise for the inconvenience caused. Type: Incident

Duration: 12 days, 5 hours and 21 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>10:39:58</var> GMT+0</small><br><strong>Investigating</strong> - Our data processing infrastructure is running behind which is causing a lack of latest information in the reporting app. No data has been lost and the team is actively investigating..</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>10:59:44</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>12:31:07</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>12:58:34</var> GMT+0</small><br><strong>Identified</strong> - Unfortunately, it's taking our teams longer than usual to fix this issue. All of the team are engaged on resolving this incident as soon as possible. All data collected since this incident started remains safe and will be processed as soon as possible. We sincerely apologise for the ongoing inconvenience..</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>21:11:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>13:07:33</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>16:00:53</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and we are reprocessing historical data over the last 24 hours. We sincerely apologise for the inconvenience caused..</p> ]]> Thu, 31 Oct 2024 10:39:58 +0000 https://status.gardin.ag/incident/cm2x6c2pt003aeliw81r97mqn https://status.gardin.ag/incident/cm2x6c2pt003aeliw81r97mqn Timeouts when accessing data warehouse Type: Incident Duration: 40 minutes Affected Components: Reporting App (app.gardin.ag), Query API Aug 6, 10:12:10 GMT+0 - Investigating - We are currently investigating an issue causing timeouts when accessing our data warehouse, which is causing a lack of latest information in the reporting app and delays in the use of the Query API. No data has been lost and the team is actively investigating. Aug 6, 10:52:28 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 40 minutes

Affected Components: ,

<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>10:12:10</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue causing timeouts when accessing our data warehouse, which is causing a lack of latest information in the reporting app and delays in the use of the Query API. No data has been lost and the team is actively investigating..</p> <p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>10:52:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 6 Aug 2024 10:12:10 +0000 https://status.gardin.ag/incident/clzi9h27a470494hzo6nt1kp0a0 https://status.gardin.ag/incident/clzi9h27a470494hzo6nt1kp0a0 Indices not updating over weekend. Type: Incident Duration: 4 hours and 29 minutes Affected Components: Reporting App (app.gardin.ag) Jun 24, 06:42:10 GMT+0 - Investigating - We are currently investigating this incident. Jun 24, 06:55:09 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 24, 07:40:03 GMT+0 - Monitoring - We are continuing to re-process affected data from over the weekend. We expect this to complete within the next 1 hour. Jun 24, 07:18:19 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. We are back-processing affected data. Jun 24, 09:37:01 GMT+0 - Monitoring - We apologise for the ongoing delay and are continuing to work as fast as we can to resume normal service. Jun 24, 11:11:10 GMT+0 - Resolved - We sincerely apologise to our customers for the delay in data availability over the weekend and into this morning (Monday 24th June 2024), but are pleased to announce that the underlying issue has been rectified and all affected data is now available, and normal service has resumed. Gardin takes these matters extremely seriously, and a full review will be conducted to understand the causes and what lessons can be learnt. Type: Incident

Duration: 4 hours and 29 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>06:42:10</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>06:55:09</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>07:40:03</var> GMT+0</small><br><strong>Monitoring</strong> - We are continuing to re-process affected data from over the weekend. We expect this to complete within the next 1 hour..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>07:18:19</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. We are back-processing affected data. .</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>09:37:01</var> GMT+0</small><br><strong>Monitoring</strong> - We apologise for the ongoing delay and are continuing to work as fast as we can to resume normal service..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>11:11:10</var> GMT+0</small><br><strong>Resolved</strong> - We sincerely apologise to our customers for the delay in data availability over the weekend and into this morning (Monday 24th June 2024), but are pleased to announce that the underlying issue has been rectified and all affected data is now available, and normal service has resumed. Gardin takes these matters extremely seriously, and a full review will be conducted to understand the causes and what lessons can be learnt..</p> ]]> Mon, 24 Jun 2024 06:42:10 +0000 https://status.gardin.ag/incident/clxsm1dax70895baoqct6pot9h https://status.gardin.ag/incident/clxsm1dax70895baoqct6pot9h Change of domain name for Gardin Platform Type: Maintenance Duration: 1 day Affected Components: Reporting App (app.gardin.ag), , Integration Services → Feb 27, 00:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 26, 00:00:00 GMT+0 - Identified - As part of ongoing upgrades to our infrastructure, the Gardin Platform will be moving its primary domain name to [**gardin.ag**](http://gardin.ag)on **Monday 26th February 2024**. At this time, the below changes will take effect to the following public-facing URLs: 1. **Developer Documentation:** [developers.gardinagritech.com](http://developers.gardinagritech.com) becomes[**developers.gardin.ag**](http://developers.gardin.ag) 2. **OAuth2 Authentication:** [login.gardinagritech.com](http://login.gardinagritech.com) becomes [**login.gardin.ag**](http://login.gardin.ag) 3. **Gardin API:** [api.gardinagritech.com](http://api.gardinagritech.com) becomes[**api.gardin.ag**](http://api.gardin.ag) 4. **SFTP:** [sftp.gardinagritech.com](http://sftp.gardinagritech.com) becomes[**sftp.gardin.ag**](http://sftp.gardin.ag) Please ensure that you have updated any browser bookmarks and API/SFTP integration code by **Monday 26th February 2024 to avoid any interruptions.** Feb 26, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 1 day

Affected Components: ,

<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> - As part of ongoing upgrades to our infrastructure, the Gardin Platform will be moving its primary domain name to [**gardin.ag**](http://gardin.ag)on **Monday 26th February 2024**. At this time, the below changes will take effect to the following public-facing URLs: 1. **Developer Documentation:** [developers.gardinagritech.com](http://developers.gardinagritech.com) becomes[**developers.gardin.ag**](http://developers.gardin.ag) 2. **OAuth2 Authentication:** [login.gardinagritech.com](http://login.gardinagritech.com) becomes [**login.gardin.ag**](http://login.gardin.ag) 3. **Gardin API:** [api.gardinagritech.com](http://api.gardinagritech.com) becomes[**api.gardin.ag**](http://api.gardin.ag) 4. **SFTP:** [sftp.gardinagritech.com](http://sftp.gardinagritech.com) becomes[**sftp.gardin.ag**](http://sftp.gardin.ag) Please ensure that you have updated any browser bookmarks and API/SFTP integration code by **Monday 26th February 2024 to avoid any interruptions.**.</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Mon, 26 Feb 2024 00:00:00 +0000 https://status.gardin.ag/maintenance/clsqawdb5266777balh8k5eutby https://status.gardin.ag/maintenance/clsqawdb5266777balh8k5eutby Downtime for routine maintenance Type: Maintenance Duration: 10 hours and 7 minutes Affected Components: Reporting App (app.gardin.ag), , Integration Services → Dec 27, 10:06:42 GMT+0 - Completed - Maintenance has completed successfully. We thank all of our users for their understanding and patience. Dec 27, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 27, 00:00:00 GMT+0 - Identified - The Gardin platform will be undergoing routine maintenance starting at midnight on 27th December. This necessary maintenance is expected to last up to 24 hours. During this period, the platform will be unavailable. We appreciate your understanding and apologise for any inconvenience this may cause. Type: Maintenance

Duration: 10 hours and 7 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>10:06:42</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully. We thank all of our users for their understanding and patience..</p> <p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> - The Gardin platform will be undergoing routine maintenance starting at midnight on 27th December. This necessary maintenance is expected to last up to 24 hours. During this period, the platform will be unavailable. We appreciate your understanding and apologise for any inconvenience this may cause..</p> ]]> Wed, 27 Dec 2023 00:00:00 +0000 https://status.gardin.ag/maintenance/clqe31lbi20375b4okko96abuj https://status.gardin.ag/maintenance/clqe31lbi20375b4okko96abuj Processing Delays Type: Incident Duration: 25 minutes Dec 21, 15:20:40 GMT+0 - Investigating - Our data processing infrastructure is running behind which is causing a lack of latest information in the reporting app. No data has been lost and the team is actively investigating. Dec 21, 15:34:28 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 21, 15:34:53 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 21, 15:45:13 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 25 minutes

<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>15:20:40</var> GMT+0</small><br><strong>Investigating</strong> - Our data processing infrastructure is running behind which is causing a lack of latest information in the reporting app. No data has been lost and the team is actively investigating..</p> <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>15:34:28</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>15:34:53</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>15:45:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 21 Dec 2023 15:20:40 +0000 https://status.gardin.ag/incident/clqfcnpgm87027b8my248af594 https://status.gardin.ag/incident/clqfcnpgm87027b8my248af594 Upgrade of infrastructure for BI systems. Type: Maintenance Duration: 18 hours Oct 31, 08:06:41 GMT+0 - Completed - The scheduled maintenance has been completed. Oct 31, 00:32:17 GMT+0 - Identified - Unfortunately the upgrade is taking longer than we would have hoped. We now expect the system to be back online by 9am GMT on Tues 31st October. Oct 30, 17:01:52 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 30, 07:49:01 GMT+0 - Identified - Our BI systems are undergoing maintenance during this time to allow our teams to undertake a major upgrade to underlying infrastructure. Please ensure you have saved any work before the scheduled start time. Oct 30, 16:00:02 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Type: Maintenance

Duration: 18 hours

<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>08:06:41</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>00:32:17</var> GMT+0</small><br><strong>Identified</strong> - Unfortunately the upgrade is taking longer than we would have hoped. We now expect the system to be back online by 9am GMT on Tues 31st October..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>17:01:52</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>07:49:01</var> GMT+0</small><br><strong>Identified</strong> - Our BI systems are undergoing maintenance during this time to allow our teams to undertake a major upgrade to underlying infrastructure. Please ensure you have saved any work before the scheduled start time..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>16:00:02</var> GMT+0</small><br><strong>Identified</strong> - Maintenance will begin as scheduled in 60 minutes..</p> ]]> Mon, 30 Oct 2023 17:00:00 +0000 https://status.gardin.ag/maintenance/cloq90p35000ab5olgvqvev2d-nwdrnl72d9q3 https://status.gardin.ag/maintenance/cloq90p35000ab5olgvqvev2d-nwdrnl72d9q3 Data Processing Delays - Reporting Tools Affected Type: Incident Oct 20, 12:11:47 GMT+0 - Resolved - This incident has been resolved. Oct 20, 09:30:00 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Oct 20, 09:14:07 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Oct 20, 06:21:33 GMT+0 - Investigating - We are continuing to investigate this issue. Oct 20, 06:20:46 GMT+0 - Investigating - Our data processing infrastructure is running behind which is causing a lack of latest information in the reporting app. No data has been lost and the team is actively investigating. Type: Incident

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>12:11:47</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>09:30:00</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>09:14:07</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>06:21:33</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate this issue..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>06:20:46</var> GMT+0</small><br><strong>Investigating</strong> - Our data processing infrastructure is running behind which is causing a lack of latest information in the reporting app. No data has been lost and the team is actively investigating..</p> ]]> Fri, 20 Oct 2023 06:20:46 +0000 https://status.gardin.ag/incident/cloq90p35000hb5olg0w3eshe-h5wm9skfjyg1 https://status.gardin.ag/incident/cloq90p35000hb5olg0w3eshe-h5wm9skfjyg1 ChF metrics not being processed correctly. Type: Incident Jan 27, 07:56:30 GMT+0 - Resolved - The Platform team apologise for the inconvenience this issue caused. Our investigation found that the use of Glue bookmarks to incrementally retrieve **new** data that was queued for processing was silently preventing our pipeline from returning the full range of **historical** data neccessary to compute certain ChF metrics correctly, despite explicitly setting the time window that we required in the query. This issue proved difficult to replicate in a development envrionment, as it is neccessary to disable Glue bookmarks in this envrionment for testing. We have now replaced the use of Glue bookmarks for tracking pipeline progress with a “roll our own” alternative tailored to our needs. This increases visibility and provides ultimate control over the behaviour of incremental query loads. We have also increased the telemetry and logging we collect, to improve visibility further. All affected historcial data has now been reprocessed, and we will continue to monitor closely over the next 24-72 hours. Jan 27, 07:51:00 GMT+0 - Resolved - We have identified and fixed an issue leading to incorrect ChF metric results being published to the data warehouse. Type: Incident

<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>07:56:30</var> GMT+0</small><br><strong>Resolved</strong> - The Platform team apologise for the inconvenience this issue caused. Our investigation found that the use of Glue bookmarks to incrementally retrieve **new** data that was queued for processing was silently preventing our pipeline from returning the full range of **historical** data neccessary to compute certain ChF metrics correctly, despite explicitly setting the time window that we required in the query. This issue proved difficult to replicate in a development envrionment, as it is neccessary to disable Glue bookmarks in this envrionment for testing. We have now replaced the use of Glue bookmarks for tracking pipeline progress with a “roll our own” alternative tailored to our needs. This increases visibility and provides ultimate control over the behaviour of incremental query loads. We have also increased the telemetry and logging we collect, to improve visibility further. All affected historcial data has now been reprocessed, and we will continue to monitor closely over the next 24-72 hours..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>07:51:00</var> GMT+0</small><br><strong>Resolved</strong> - We have identified and fixed an issue leading to incorrect ChF metric results being published to the data warehouse..</p> ]]> Wed, 25 Jan 2023 07:51:00 +0000 https://status.gardin.ag/incident/cloq90p35000pb5ol4fhkbenw-njsb42c2zrr0 https://status.gardin.ag/incident/cloq90p35000pb5ol4fhkbenw-njsb42c2zrr0 Vitals dashboard unavailable Type: Incident Sep 8, 18:04:43 GMT+0 - Resolved - The Platform team apologise for the inconvenience this outage has caused. Unfortunately, due a deployment oversight that occurred whilst undertaking some testing of a new part of the platform AWS stack, the database and integration layer that supports the vitals telemetry dashboard was stood down and removed - the database on this occasion, was also irreversibly lost, making data reconstruction impossible. It should not have been possible for this to happen in a production environment. ‌We have now identified that additional automated safety checks that should have prevented this loss were not configured correctly, and after correcting this have now ensured that moving forward, these checks will block such loss of data. Additional process controls will also be put in place to guide the team through the deployment process. Sep 8, 18:04:11 GMT+0 - Resolved - The issue has now been fixed, and the vitals dashboard is now available once again. Sep 8, 12:23:29 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Type: Incident

<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>18:04:43</var> GMT+0</small><br><strong>Resolved</strong> - The Platform team apologise for the inconvenience this outage has caused. Unfortunately, due a deployment oversight that occurred whilst undertaking some testing of a new part of the platform AWS stack, the database and integration layer that supports the vitals telemetry dashboard was stood down and removed - the database on this occasion, was also irreversibly lost, making data reconstruction impossible. It should not have been possible for this to happen in a production environment. ‌We have now identified that additional automated safety checks that should have prevented this loss were not configured correctly, and after correcting this have now ensured that moving forward, these checks will block such loss of data. Additional process controls will also be put in place to guide the team through the deployment process..</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>18:04:11</var> GMT+0</small><br><strong>Resolved</strong> - The issue has now been fixed, and the vitals dashboard is now available once again..</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>12:23:29</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> ]]> Thu, 8 Sep 2022 12:23:29 +0000 https://status.gardin.ag/incident/cloq90p35000sb5ol1aeie4bb-6jkw89y3qt9t https://status.gardin.ag/incident/cloq90p35000sb5ol1aeie4bb-6jkw89y3qt9t Maintenance for demo Type: Maintenance Duration: 1 day Sep 6, 12:29:32 GMT+0 - Identified - We will be undergoing scheduled maintenance during this time. Sep 6, 12:28:09 GMT+0 - Identified - We will be undertaking development of the insights pipeline and analytics reporting front end during this time. Sep 7, 09:55:22 GMT+0 - Completed - The scheduled maintenance has been completed. Sep 6, 12:29:42 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Type: Maintenance

Duration: 1 day

<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>12:29:32</var> GMT+0</small><br><strong>Identified</strong> - We will be undergoing scheduled maintenance during this time..</p> <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>12:28:09</var> GMT+0</small><br><strong>Identified</strong> - We will be undertaking development of the insights pipeline and analytics reporting front end during this time..</p> <p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>09:55:22</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>12:29:42</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> ]]> Tue, 6 Sep 2022 12:29:00 +0000 https://status.gardin.ag/maintenance/cloq90p35000xb5ol241b8agf-3b98471bqn90 https://status.gardin.ag/maintenance/cloq90p35000xb5ol241b8agf-3b98471bqn90