Duration: 24 minutes

Affected Components:

Oct 5, 20:10:45 GMT+0
Resolved - \[Sandbox\] The Orchestration API has automatically recovered and is now functioning normally. Our monitoring system has verified that all services are operating as expected. This incident has been automatically resolved. We apologize for any inconvenience and thank you for your patience..

Oct 5, 19:46:20 GMT+0
Investigating - \[Sandbox\] We've detected that the Orchestration API is currently experiencing availability issues. Our engineering team has been automatically notified and is monitoring the situation. If the service doesn't recover automatically, we'll investigate to identify and resolve the root cause. This incident was created automatically by our monitoring system..

Duration: 9 minutes

Affected Components:

Sep 3, 20:00:34 GMT+0
Resolved - \[EU\] The Orchestration API has automatically recovered and is now functioning normally. Our monitoring system has verified that all services are operating as expected. This incident has been automatically resolved. We apologize for any inconvenience and thank you for your patience..

Sep 3, 19:51:29 GMT+0
Investigating - \[EU\] We've detected that the Orchestration API is currently experiencing availability issues. Our engineering team has been automatically notified and is monitoring the situation. If the service doesn't recover automatically, we'll investigate to identify and resolve the root cause. This incident was created automatically by our monitoring system..

Duration: 6 minutes

Affected Components:

Sep 2, 11:26:46 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Sep 2, 11:21:07 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 2 minutes

Affected Components:

Aug 10, 20:53:35 GMT+0
Resolved - \[UK\] The Orchestration API has automatically recovered and is now functioning normally. Our monitoring system has verified that all services are operating as expected. This incident has been automatically resolved. We apologize for any inconvenience and thank you for your patience..

Aug 10, 20:51:24 GMT+0
Investigating - \[UK\] We've detected that the Orchestration API is currently experiencing availability issues. Our engineering team has been automatically notified and is monitoring the situation. If the service doesn't recover automatically, we'll investigate to identify and resolve the root cause. This incident was created automatically by our monitoring system..

Duration: 12 minutes

Affected Components:

Aug 9, 16:08:18 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 15:56:30 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 57 minutes

Affected Components:

Aug 9, 14:47:30 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 13:50:40 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 5 minutes

Affected Components:

Aug 9, 13:35:01 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 13:30:01 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 23 minutes

Affected Components:

Aug 9, 12:58:33 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 12:35:56 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 11 minutes

Affected Components:

Aug 9, 10:18:14 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 10:07:10 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 29 minutes

Affected Components:

Aug 9, 09:51:29 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 09:22:08 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 48 minutes

Affected Components:

Aug 9, 09:06:07 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 08:18:23 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 31 minutes

Affected Components:

Aug 9, 08:02:43 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Aug 9, 07:31:57 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 12 minutes

Affected Components:

Jul 13, 10:59:58 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Jul 13, 10:47:35 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 15 days and 20 hours

Affected Components: , , ,

Jun 30, 09:15:00 GMT+0
Resolved - The database cluster has been restored to a fully functional state. We are now investigating the impact on care flows and will reach out to our users to give them more details..

Jun 30, 03:08:00 GMT+0
Investigating - One of the servers in the database cluster reported running out of disk space. This issue resolved itself within 15 minutes, but the server was left in a degraded state and refused to perform some of its tasks..

Duration: 1 hour

Affected Components: , ,

Jun 15, 09:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jun 15, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 15, 08:00:00 GMT+0
Identified - We'll be running some upgrades to our systems and expect moderate downtime during this upgrade.

Duration: 1 hour

Affected Components: , , , , , , , , ,

Jun 13, 02:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jun 13, 01:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 13, 01:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Duration: 11 minutes

Affected Components:

Jun 10, 09:27:58 GMT+0
Resolved - \[UK\] The Orchestration API has automatically recovered and is now functioning normally. Our monitoring system has verified that all services are operating as expected. This incident has been automatically resolved. We apologize for any inconvenience and thank you for your patience..

Jun 10, 09:16:51 GMT+0
Investigating - \[UK\] We've detected that the Orchestration API is currently experiencing availability issues. Our engineering team has been automatically notified and is monitoring the situation. If the service doesn't recover automatically, we'll investigate to identify and resolve the root cause. This incident was created automatically by our monitoring system..

Duration: 15 minutes

Affected Components: , ,

May 18, 09:00:00 GMT+0
Completed - Maintenance has completed successfully.

May 18, 08:45:01 GMT+0
Identified - Maintenance is now in progress.

May 18, 08:45:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Duration: 6 minutes

Affected Components:

May 15, 12:57:04 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

May 15, 12:51:07 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 1 hour and 27 minutes

Affected Components: , , , , , ,

May 12, 19:04:18 GMT+0
Completed - Maintenance has completed successfully..

May 12, 18:57:00 GMT+0
Completed - Maintenance has completed successfully.

May 12, 17:30:01 GMT+0
Identified - Maintenance is now in progress.

May 12, 17:30:00 GMT+0
Identified - We are performing a rolling database upgrade in EU & UK to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

Duration: 2 hours and 2 minutes

Affected Components: , ,

May 12, 10:02:06 GMT+0
Completed - Maintenance has completed successfully..

May 12, 08:00:00 GMT+0
Identified - We are performing a rolling database upgrade in US to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

May 12, 08:00:00 GMT+0
Identified - Maintenance is now in progress..

Duration: 3 hours and 42 minutes

Affected Components: , ,

May 9, 10:11:37 GMT+0
Completed - Maintenance has completed successfully..

May 9, 06:30:00 GMT+0
Identified - We are performing a rolling database upgrade in US to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

May 9, 06:30:00 GMT+0
Identified - Maintenance is now in progress..

Duration: 4 hours

Affected Components: , , , , , ,

May 9, 06:30:00 GMT+0
Identified - We are performing a rolling database upgrade in EU & UK to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

May 9, 06:30:00 GMT+0
Identified - We are performing a rolling database upgrade in EU & UK to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

May 9, 06:30:00 GMT+0
Completed - Maintenance has completed successfully..

Duration: 2 hours and 40 minutes

Affected Components: , ,

May 7, 07:00:00 GMT+0
Identified - We are performing a rolling infrastructure update in US to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

May 7, 07:00:00 GMT+0
Completed - Maintenance has completed successfully..

Duration: 1 hour

Affected Components: , , , , , ,

May 7, 02:00:00 GMT+0
Completed - Maintenance has completed successfully.

May 7, 01:00:01 GMT+0
Identified - Maintenance is now in progress.

May 7, 01:00:00 GMT+0
Identified - We are performing a rolling infrastructure update in our production environments to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

Duration: 3 minutes

Affected Components:

May 6, 12:53:46 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

May 6, 12:50:19 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 20 minutes

Affected Components: , ,

May 6, 03:49:31 GMT+0
Completed - Maintenance has completed successfully..

May 6, 03:30:01 GMT+0
Identified - Maintenance is now in progress.

May 6, 03:30:00 GMT+0
Identified - We are performing a rolling infrastructure update in Sandbox to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..

Duration: 2 hours and 30 minutes

Affected Components: , ,

May 5, 10:15:54 GMT+0
Completed - Maintenance has completed successfully..

May 5, 07:40:00 GMT+0
Identified - We are performing a scheduled maintenance that will cause brief downtime as we refresh and further harden our databases..

Duration: 4 days and 9 hours

Affected Components: , , , , , ,

May 5, 03:45:00 GMT+0
Completed - Maintenance has completed successfully.

May 5, 02:10:31 GMT+0
Identified - Maintenance has completed successfully in EU.

May 5, 02:00:01 GMT+0
Identified - Maintenance is now in progress.

May 5, 02:00:00 GMT+0
Identified - We are planning for a scheduled maintenance that will cause brief downtime as we refresh and further harden our databases..

Duration: 37 minutes

Affected Components:

May 4, 15:35:00 GMT+0
Resolved - This incident has been resolved..

May 4, 14:58:00 GMT+0
Investigating - We experienced infrastructure issues impacting Orchestration activities for a subset of activities. Some users experienced degraded performance..

Duration: 3 minutes

Affected Components:

May 2, 12:53:16 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

May 2, 12:49:54 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 11 minutes

Affected Components:

May 1, 13:00:24 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

May 1, 12:49:54 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 2 minutes

Affected Components:

Apr 29, 12:52:12 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Apr 29, 12:50:13 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 36 minutes

Affected Components:

Apr 28, 22:29:00 GMT+0
Resolved - We experienced infrastructure issues impacting Awell Hosted Pages and initiating care flows via our API. Core orchestration remained operational, but some users experienced degraded performance. Starting care flows through incoming webhooks and bulk uploads were not impacted. The issue is resolved..

Apr 28, 20:06:00 GMT+0
Identified - Intermittent Redis restarts caused unreliable calls from Awell Hosted Pages and other non-core services..

Duration: 3 minutes

Affected Components:

Apr 26, 12:52:56 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Apr 26, 12:50:16 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 1 day, 11 hours and 56 minutes

Affected Components:

Apr 27, 08:31:00 GMT+0
Resolved - This incident has been resolved..

Apr 25, 20:35:00 GMT+0
Investigating - We are currently investigating an incident causing Orchestration activities to fail during creation and completion..

Duration: 4 minutes

Affected Components:

Apr 24, 12:54:12 GMT+0
Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges. The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..

Apr 24, 12:50:20 GMT+0
Investigating - \[US\] We're currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation. The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn't improve shortly, we'll take additional actions to reduce the impact of this temporary load. This notice was created automatically by our monitoring system..

Duration: 15 minutes

Affected Components: , , , , , , , , ,

Apr 20, 01:15:00 GMT+0
Completed - Maintenance has completed successfully.

Apr 20, 01:00:01 GMT+0
Identified - Maintenance is now in progress.

Apr 20, 01:00:00 GMT+0
Identified - We will perform a brief service upgrade across all environments, which will improve the throughput of our systems.

Duration: 11 minutes

Affected Components: , ,

Apr 19, 11:11:21 GMT+0
Completed - Maintenance has completed successfully..

Apr 19, 11:00:01 GMT+0
Identified - Maintenance is now in progress.

Apr 19, 11:00:00 GMT+0
Identified - ```markdown We will be performing a scheduled upgrade of our internal messaging infrastructure in the US region. During this one-hour window, you may experience: - A brief interruption (~30 seconds) where API requests may time out - Delayed message processing for up to 5 minutes as services reconnect - Temporary delays in real-time notifications and care flow progression Active care flows will automatically resume. No data loss is expected. The actual disruption is expected to be brief. The one-hour window provides buffer if additional remediation is needed. ```.

Duration: 22 minutes

Affected Components: , , , , , , , , , , , ,

Apr 18, 22:21:37 GMT+0
Completed - Maintenance in EU is complete. All maintenance has been completed..

Apr 18, 22:14:34 GMT+0
Identified - UK maintenance is complete..

Apr 18, 22:00:01 GMT+0
Identified - Maintenance is now in progress.

Apr 18, 22:00:00 GMT+0
Identified - ```markdown We will be performing scheduled upgrades of our internal messaging infrastructure in the EU and UK regions. During this one-hour window, you may experience: - A brief interruption (~30 seconds per region) where API requests may time out - Delayed message processing for up to 5 minutes per region as services reconnect - Temporary delays in real-time notifications and care flow progression Active care flows will automatically resume. No data loss is expected. The actual disruption in each region is expected to be brief. The one-hour window provides buffer if additional remediation is needed. We will post updates as each region completes. ```.

Duration: 2 hours

Affected Components: , , ,

Jan 30, 10:30:00 GMT+0
Completed - Maintenance has completed successfully.

Jan 30, 08:30:01 GMT+0
Identified - Maintenance is now in progress.

Jan 30, 08:30:00 GMT+0
Identified - We are upgrading our database cluster to the latest version. This will be done as a zero downtime operation..

Duration: 1 hour

Affected Components:

May 14, 09:30:00 GMT+0
Completed - Maintenance has completed successfully.

May 14, 08:30:01 GMT+0
Identified - Maintenance is now in progress.

May 14, 08:30:00 GMT+0
Identified - We are planning for a scheduled maintenance to further improve our orchestration data store resilience..

Duration: 1 hour and 17 minutes

Affected Components: ,

May 14, 05:46:44 GMT+0
Completed - Maintenance has completed successfully..

May 14, 04:46:43 GMT+0
Identified - We are observing degraded performance on orchestration as a result of the maintenance we are performing - that is expected and should be automatically solved until the end of the maintenance..

May 14, 04:30:01 GMT+0
Identified - Maintenance is now in progress.

May 14, 04:30:00 GMT+0
Identified - We are planning for a scheduled maintenance to further improve our orchestration data store resilience..

Duration: 1 hour

Affected Components: , , ,

Sep 5, 20:00:00 GMT+0
Completed - Maintenance has completed successfully.

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

Sep 5, 19:00:00 GMT+0
Identified - We are planning for scheduled maintenance during that time to facilitate upgrading Retool. Retool application cannot be used during this time and dashboards should not be edited..

Duration: 9 minutes

Affected Components: , ,

Jul 3, 09:01:18 GMT+0
Completed - Maintenance operations have been successfully completed with no impact on system uptime, ensuring enhanced stability and security..

Jul 3, 08:52:47 GMT+0
Identified - Maintenance is now in progress..

Jul 3, 08:45:00 GMT+0
Identified - We are performing planned maintenance to improve infrastructure security and stability. We don't expect any downtime, but we do expect small periods of time with degraded performance..

Duration: 2 hours and 12 minutes

Affected Components: , , , , , , , ,

Jul 3, 06:42:14 GMT+0
Completed - Maintenance operations have been successfully completed with no impact on system uptime, ensuring enhanced stability and security..

Jul 3, 05:32:05 GMT+0
Identified - Both Production EU and Production UK are finished and shouldn't experience any downgraded performance. Sandbox is still ongoing..

Jul 3, 04:30:00 GMT+0
Identified - We are performing planned maintenance to improve infrastructure security and stability. We don't expect any downtime, but we do expect small periods of time with degraded performance..

Duration: 21 minutes

Affected Components: , , ,

Jan 16, 10:49:09 GMT+0
Completed - Maintenance has completed successfully..

Jan 16, 10:28:12 GMT+0
Identified - We are updating the deployment configuration of the API proxy to improve its Quality-of-Service class and make it guaranteed. There is no expected impact on the availability of the orchestration API during the maintenance..

Duration: 1 day, 2 hours and 55 minutes

Affected Components: , , , , ,

Jan 15, 11:00:00 GMT+0
Completed - The maintenance has been successfully executed in all environments..

Jan 15, 10:38:00 GMT+0
Completed - Sandbox environment has been updated. No impact on availability or performances detected..

Jan 15, 10:11:05 GMT+0
Identified - We are planning a migration to the managed prometheus metrics collection feature. While this requires a change to the kubernetes cluster configuration we expect no availability or performances impact while the maintenance is ongoing. We will perform the maintenance in the Sandbox environment first, then apply it in all production environments when confirmed that availability and performances are not impacted..

Duration: 13 minutes

Affected Components: , ,

Jan 2, 10:42:45 GMT+0
Completed - Maintenance has completed successfully..

Jan 2, 10:30:20 GMT+0
Identified - Maintenance is now in progress..

Jan 2, 10:30:01 GMT+0
Identified - Maintenance is now in progress.

Jan 2, 10:30:00 GMT+0
Identified - We'll be applying a patch upgrade to our database and some intermittent downtime is expected during the upgrade..

Duration: 29 minutes

Affected Components: , , , , , , , ,

Jan 2, 03:41:57 GMT+0
Completed - Maintenance has completed successfully..

Jan 2, 03:30:23 GMT+0
Identified - UK upgrade was completed successfully. Moving on to EU.

Jan 2, 03:18:48 GMT+0
Identified - Proceeding with UK server.

Jan 2, 03:13:00 GMT+0
Identified - Sandbox migration was successful..

Jan 2, 03:00:00 GMT+0
Identified - We'll be applying a patch upgrade to our database and some intermittent downtime is expected during the upgrade..