Camunda incident
Degraded Camunda Orchestration Clusters in AWS us-east-1
Camunda experienced a major incident on October 20, 2025 affecting Connectors and Operate and 1 more component, lasting 14h 12m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2025, 09:49 AM UTC
We are aware of an issue impacting the AWS `us-east-1` region and we are closely monitoring the situation. See: https://health.aws.amazon.com/health/status We will update this incident as the situation progresses and will post an update within the next 1 hour. Affected Regions: * AWS: North America, Virginia (us-east-1)
- identified Oct 20, 2025, 09:50 AM UTC
We are continuing to work on a fix for this issue.
- identified Oct 20, 2025, 10:47 AM UTC
Our teams are still trying to mitigate the situation with our cloud provider. We are seeing a slow improvement of the requests made to AWS and are slowly getting back the missing compute capacity to run all our customers' workloads.
- monitoring Oct 20, 2025, 11:50 AM UTC
Most of the affected Camunda Orchestration Clusters have been recovered and should be working correctly. We are still seeing issues with our cloud provider, and some Camunda Orchestration Clusters may we working with reduced capacity. Impacted clusters are still processing their data, but slower than usual. We will post an update within the next 1 hour.
- monitoring Oct 20, 2025, 01:04 PM UTC
We are still seeing issues coming from our cloud provider and we keep monitoring the situation.
- monitoring Oct 20, 2025, 05:33 PM UTC
We are still seeing errors from our cloud provider and we have deployed several mitigations which acquired enough capacity to run all our customers Camunda Orchestration Clusters. In the meantime, we will continue monitoring the situation.
- resolved Oct 21, 2025, 07:46 AM UTC
The incident with our cloud provider as been resolved and all the Camunda Orchestration Clusters in the region are working normally since 19:33 CEST yesterday.