Docusign Status

Postmortem: ## RCA for CLM EU11, EU21, US11, US12, US13 Service Disruption Beginning March 14, 2026

Impact Summary:

Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are noted below:

• US11: 2026-03-14 1:20 AM UTC to 2026-03-14 9:20 AM UTC
• US12: 2026-03-14 1:20 AM UTC to 2026-03-14 10:15 AM UTC
• US13: 2026-03-14 1:20 AM UTC to 2026-03-14 7:35 AM UTC
• EU11: 2026-03-16 8:05 PM UTC to 2026-03-16 10:45 PM UTC
• EU21: 2026-03-14 1:20 AM UTC to 2026-03-17 00:15 AM UTC

Customers in EU11 may have observed degradations across various operations from 03/14/2026 02:50 UTC to 03/14/2026 03:10 UTC, and 03/16/2026 01:25 UTC to 03/16/2026 03:55 UTC.

Following initial recovery, some EU21 customers may have experienced the following issues until 2026-03-17 22:23 UTC: missing historical search results, failures in workflows involving search steps, missing or outdated company logos, and inaccurate reporting of Docusign envelope statuses.

Cause:

The issue was triggered by a planned security update applied to infrastructure supporting our application services. Once issues were identified, the update was rolled back. While the rollback completed successfully in unaffected environments, it did not fully complete in all cases, resulting in a subset of infrastructure entering a degraded or failed state.

Resolution:

In US11, US12 and US13 sites, recovery was achieved and service was restored by resetting affected clusters and restarting application services that had entered a failed state.

EU11 required rebuilding a cluster to reallocate services and restore regular operations.

Recovery efforts in EU21 required additional remediation steps and took longer to stabilize. Multiple parallel efforts were executed in an attempt to restore the failed clusters and we ultimately initiated a failover to alternate infrastructure to complete recovery and restore services.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

An RCA is anticipated to be shared here by 2026-03-19 12:00 AM UTC

Monitoring: We continue to monitor the environment to ensure stability.

Any company logos that were missing or outdated have been updated.

Monitoring: We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Monitoring: A fix has been implemented and we are monitoring the results.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Identified: The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21.

Identified: We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.

Identified: We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.

Identified: We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.

Identified: We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.

Identified: We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.

Identified: We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We have identified an intermittent degradation in our EU11 environment and are working on fixing it.

Identified: We are continuing to work through failover steps.

Identified: We are continuing to work through failover steps.

Identified: We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to remediate impact to EU21 customers.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to remediate impact to EU11 and EU21 customers.

Identified: We are continuing to work on a fix for EU21 customers.  EU21 customers may observe issues accessing the site.  EU11 customers may see intermittent issues generating documents.

Monitoring: A fix has been implemented for US sites as of approximately 09:00 UTC.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Postmortem: ## RCA for CLM EU11, EU21, US11, US12, US13 Service Disruption Beginning March 14, 2026

Impact Summary:

Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are noted below:

• US11: 2026-03-14 1:20 AM UTC to 2026-03-14 9:20 AM UTC
• US12: 2026-03-14 1:20 AM UTC to 2026-03-14 10:15 AM UTC
• US13: 2026-03-14 1:20 AM UTC to 2026-03-14 7:35 AM UTC
• EU11: 2026-03-16 8:05 PM UTC to 2026-03-16 10:45 PM UTC
• EU21: 2026-03-14 1:20 AM UTC to 2026-03-17 00:15 AM UTC

Customers in EU11 may have observed degradations across various operations from 03/14/2026 02:50 UTC to 03/14/2026 03:10 UTC, and 03/16/2026 01:25 UTC to 03/16/2026 03:55 UTC.

Following initial recovery, some EU21 customers may have experienced the following issues until 2026-03-17 22:23 UTC: missing historical search results, failures in workflows involving search steps, missing or outdated company logos, and inaccurate reporting of Docusign envelope statuses.

Cause:

The issue was triggered by a planned security update applied to infrastructure supporting our application services. Once issues were identified, the update was rolled back. While the rollback completed successfully in unaffected environments, it did not fully complete in all cases, resulting in a subset of infrastructure entering a degraded or failed state.

Resolution:

In US11, US12 and US13 sites, recovery was achieved and service was restored by resetting affected clusters and restarting application services that had entered a failed state.

EU11 required rebuilding a cluster to reallocate services and restore regular operations.

Recovery efforts in EU21 required additional remediation steps and took longer to stabilize. Multiple parallel efforts were executed in an attempt to restore the failed clusters and we ultimately initiated a failover to alternate infrastructure to complete recovery and restore services.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

An RCA is anticipated to be shared here by 2026-03-19 12:00 AM UTC

Monitoring: We continue to monitor the environment to ensure stability.

Any company logos that were missing or outdated have been updated.

Monitoring: We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Monitoring: A fix has been implemented and we are monitoring the results.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Identified: The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21.

Identified: We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.

Identified: We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.

Identified: We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.

Identified: We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.

Identified: We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.

Identified: We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We have identified an intermittent degradation in our EU11 environment and are working on fixing it.

Identified: We are continuing to work through failover steps.

Identified: We are continuing to work through failover steps.

Identified: We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to remediate impact to EU21 customers.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to remediate impact to EU11 and EU21 customers.

Identified: We are continuing to work on a fix for EU21 customers.  EU21 customers may observe issues accessing the site.  EU11 customers may see intermittent issues generating documents.

Monitoring: A fix has been implemented for US sites as of approximately 09:00 UTC.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Postmortem: ## RCA for CLM EU11, EU21, US11, US12, US13 Service Disruption Beginning March 14, 2026

Impact Summary:

Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are noted below:

• US11: 2026-03-14 1:20 AM UTC to 2026-03-14 9:20 AM UTC
• US12: 2026-03-14 1:20 AM UTC to 2026-03-14 10:15 AM UTC
• US13: 2026-03-14 1:20 AM UTC to 2026-03-14 7:35 AM UTC
• EU11: 2026-03-16 8:05 PM UTC to 2026-03-16 10:45 PM UTC
• EU21: 2026-03-14 1:20 AM UTC to 2026-03-17 00:15 AM UTC

Customers in EU11 may have observed degradations across various operations from 03/14/2026 02:50 UTC to 03/14/2026 03:10 UTC, and 03/16/2026 01:25 UTC to 03/16/2026 03:55 UTC.

Following initial recovery, some EU21 customers may have experienced the following issues until 2026-03-17 22:23 UTC: missing historical search results, failures in workflows involving search steps, missing or outdated company logos, and inaccurate reporting of Docusign envelope statuses.

Cause:

The issue was triggered by a planned security update applied to infrastructure supporting our application services. Once issues were identified, the update was rolled back. While the rollback completed successfully in unaffected environments, it did not fully complete in all cases, resulting in a subset of infrastructure entering a degraded or failed state.

Resolution:

In US11, US12 and US13 sites, recovery was achieved and service was restored by resetting affected clusters and restarting application services that had entered a failed state.

EU11 required rebuilding a cluster to reallocate services and restore regular operations.

Recovery efforts in EU21 required additional remediation steps and took longer to stabilize. Multiple parallel efforts were executed in an attempt to restore the failed clusters and we ultimately initiated a failover to alternate infrastructure to complete recovery and restore services.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

An RCA is anticipated to be shared here by 2026-03-19 12:00 AM UTC

Monitoring: We continue to monitor the environment to ensure stability.

Any company logos that were missing or outdated have been updated.

Monitoring: We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Monitoring: A fix has been implemented and we are monitoring the results.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Identified: The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21.

Identified: We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.

Identified: We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.

Identified: We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.

Identified: We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.

Identified: We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.

Identified: We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We have identified an intermittent degradation in our EU11 environment and are working on fixing it.

Identified: We are continuing to work through failover steps.

Identified: We are continuing to work through failover steps.

Identified: We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to remediate impact to EU21 customers.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to remediate impact to EU11 and EU21 customers.

Identified: We are continuing to work on a fix for EU21 customers.  EU21 customers may observe issues accessing the site.  EU11 customers may see intermittent issues generating documents.

Monitoring: A fix has been implemented for US sites as of approximately 09:00 UTC.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Postmortem: ## RCA for CLM EU11, EU21, US11, US12, US13 Service Disruption Beginning March 14, 2026

Impact Summary:

Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are noted below:

• US11: 2026-03-14 1:20 AM UTC to 2026-03-14 9:20 AM UTC
• US12: 2026-03-14 1:20 AM UTC to 2026-03-14 10:15 AM UTC
• US13: 2026-03-14 1:20 AM UTC to 2026-03-14 7:35 AM UTC
• EU11: 2026-03-16 8:05 PM UTC to 2026-03-16 10:45 PM UTC
• EU21: 2026-03-14 1:20 AM UTC to 2026-03-17 00:15 AM UTC

Customers in EU11 may have observed degradations across various operations from 03/14/2026 02:50 UTC to 03/14/2026 03:10 UTC, and 03/16/2026 01:25 UTC to 03/16/2026 03:55 UTC.

Following initial recovery, some EU21 customers may have experienced the following issues until 2026-03-17 22:23 UTC: missing historical search results, failures in workflows involving search steps, missing or outdated company logos, and inaccurate reporting of Docusign envelope statuses.

Cause:

The issue was triggered by a planned security update applied to infrastructure supporting our application services. Once issues were identified, the update was rolled back. While the rollback completed successfully in unaffected environments, it did not fully complete in all cases, resulting in a subset of infrastructure entering a degraded or failed state.

Resolution:

In US11, US12 and US13 sites, recovery was achieved and service was restored by resetting affected clusters and restarting application services that had entered a failed state.

EU11 required rebuilding a cluster to reallocate services and restore regular operations.

Recovery efforts in EU21 required additional remediation steps and took longer to stabilize. Multiple parallel efforts were executed in an attempt to restore the failed clusters and we ultimately initiated a failover to alternate infrastructure to complete recovery and restore services.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

An RCA is anticipated to be shared here by 2026-03-19 12:00 AM UTC

Monitoring: We continue to monitor the environment to ensure stability.

Any company logos that were missing or outdated have been updated.

Monitoring: We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Monitoring: A fix has been implemented and we are monitoring the results.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Identified: The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21.

Identified: We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.

Identified: We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.

Identified: We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.

Identified: We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.

Identified: We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.

Identified: We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We have identified an intermittent degradation in our EU11 environment and are working on fixing it.

Identified: We are continuing to work through failover steps.

Identified: We are continuing to work through failover steps.

Identified: We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to remediate impact to EU21 customers.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to remediate impact to EU11 and EU21 customers.

Identified: We are continuing to work on a fix for EU21 customers.  EU21 customers may observe issues accessing the site.  EU11 customers may see intermittent issues generating documents.

Monitoring: A fix has been implemented for US sites as of approximately 09:00 UTC.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Identified: As a continuation of incident 4517, a subset of customers may experience incomplete search results for historical documents older than one year. A fix is currently underway, and full resolution is anticipated by Wednesday, March 18, 2026 at 11:00 AM UTC.

Postmortem: ## RCA for CLM EU11, EU21, US11, US12, US13 Service Disruption Beginning March 14, 2026

Impact Summary:

Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are noted below:

• US11: 2026-03-14 1:20 AM UTC to 2026-03-14 9:20 AM UTC
• US12: 2026-03-14 1:20 AM UTC to 2026-03-14 10:15 AM UTC
• US13: 2026-03-14 1:20 AM UTC to 2026-03-14 7:35 AM UTC
• EU11: 2026-03-16 8:05 PM UTC to 2026-03-16 10:45 PM UTC
• EU21: 2026-03-14 1:20 AM UTC to 2026-03-17 00:15 AM UTC

Customers in EU11 may have observed degradations across various operations from 03/14/2026 02:50 UTC to 03/14/2026 03:10 UTC, and 03/16/2026 01:25 UTC to 03/16/2026 03:55 UTC.

Following initial recovery, some EU21 customers may have experienced the following issues until 2026-03-17 22:23 UTC: missing historical search results, failures in workflows involving search steps, missing or outdated company logos, and inaccurate reporting of Docusign envelope statuses.

Cause:

The issue was triggered by a planned security update applied to infrastructure supporting our application services. Once issues were identified, the update was rolled back. While the rollback completed successfully in unaffected environments, it did not fully complete in all cases, resulting in a subset of infrastructure entering a degraded or failed state.

Resolution:

In US11, US12 and US13 sites, recovery was achieved and service was restored by resetting affected clusters and restarting application services that had entered a failed state.

EU11 required rebuilding a cluster to reallocate services and restore regular operations.

Recovery efforts in EU21 required additional remediation steps and took longer to stabilize. Multiple parallel efforts were executed in an attempt to restore the failed clusters and we ultimately initiated a failover to alternate infrastructure to complete recovery and restore services.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

An RCA is anticipated to be shared here by 2026-03-19 12:00 AM UTC

Monitoring: We continue to monitor the environment to ensure stability.

Any company logos that were missing or outdated have been updated.

Monitoring: We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Monitoring: A fix has been implemented and we are monitoring the results.

Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

Identified: The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

Identified: We are still continuing to work through the failover steps for EU21.

Identified: We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.

Identified: We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.

Identified: We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.

Identified: We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.

Identified: We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.

Identified: We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

Identified: We have identified an intermittent degradation in our EU11 environment and are working on fixing it.

Identified: We are continuing to work through failover steps.

Identified: We are continuing to work through failover steps.

Identified: We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to remediate impact to EU21 customers.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to remediate impact to EU11 and EU21 customers.

Identified: We are continuing to work on a fix for EU21 customers.  EU21 customers may observe issues accessing the site.  EU11 customers may see intermittent issues generating documents.

Monitoring: A fix has been implemented for US sites as of approximately 09:00 UTC.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.