We have successfully upgraded the infrastructure. Response times are now below 250ms and we are monitoring the systems to ensure stability

The infrastructure upgrade is progressing well. We are continuing work to complete the upgrade and restore full performance.

We have identified the root cause of the degraded performance. The issue is due to increased workload beyond current infrastructure capacity. We will be upgrading the infrastructure to support the new workload requirements.

We are currently investigating reports of degraded performance affecting the EU and US Console and Compliance Page. Our team is actively working to identify the root cause and restore normal service levels.

The scheduled maintenance on the Document feature has been completed successfully. All systems are now fully operational. Thank you for your patience during this maintenance window.

Our scheduled maintenance on the Document feature is taking longer than anticipated. We expect to complete the work within the next hour. We appreciate your patience and will provide updates as we progress.

We identified a new background process that was consuming excessive CPU resources. We have rolled back the changes, implemented a fix, and re-enabled the new feature. All systems are operating normally.

We have identified the issue and are currently upgrading the infrastructure to better respond to the traffic. We are monitoring the situation closely.

We've identified a gateway timeout issue affecting the US Console and Compliance Page. Our team is actively working on a resolution.

Fix has been deployed.

The patch has been reviewed and now we'll deploy it.

The bug only affect access without NDA, we are working on a patch.

After login to the compliance page using magic link the NDA signature trigger a blank page.

All pending certificate renewals have been completed. The incident is now closed.

We're deploying a fix to resume ACME certificate renewing.

The newly deployed version have introduced a non backward compatible state change that causes the previous version to segfault during the certificate renewal process.

We rolled back the load balancer to the previous console version in the US region. The console is now operational. We are continuing to investigate the issue.

All requests to the console API returns timeout.

All traffic has recovered. Our deployment process was in a corrupted state and performed the wrong blue/green swap.

Load balancers sent traffic to outdated targets, which resulted in 5xx responses

Our monitoring detected an increase in 5xx errors across all HTTP responses.