Camunda Outage History

Started Oct 20, 2026, 07:01 AM UTC· resolved Oct 20, 2026, 01:21 PM UTC

1. investigating Oct 20, 2026, 07:01 AM UTC

   Our team is working to identify the cause and implement a solution. Affected Versions: All Affected Regions: GKE, London, Europe (europe-west2)

2. identified Oct 20, 2026, 07:56 AM UTC

   We are currently experiencing an issue affecting a limited number of clusters in our GKE London (europe-west2) region. The cause is an ongoing incident at our cloud provider, Google Cloud, which affects compute and storage resources in this region. Affected clusters may be unavailable or running with reduced functionality. Clusters in other regions are not affected. Recovery depends on the resolution of the underlying provider incident. We will provide the next update within 60 minutes, or sooner if there is a change.

3. identified Oct 20, 2026, 09:04 AM UTC

   Update – Some SaaS clusters in the GCP London region (europe-west2) are unavailable We are continuing to investigate degraded availability for a subset of Camunda 8 SaaS clusters hosted in the Google Cloud London region (europe-west2). The cause is an ongoing infrastructure incident at Google Cloud affecting compute, storage and networking services in this region. As a result, some of the underlying infrastructure for the affected clusters is unavailable, and these clusters can currently not run at full capacity or have lost availability. Google is actively working on the incident. We are in contact with Google Cloud Support and are working with them to restore the affected resources as quickly as possible. At this point, recovery depends on Google's resolution of the underlying issue, so we do not have an estimated time of resolution yet. Clusters in other regions are not affected. No data loss is expected. We will post the next update within 120 minutes, or earlier if there is any change.

4. monitoring Oct 20, 2026, 11:32 AM UTC

   Google has published an update on the incident affecting GKE in europe-west2 (London). All C8 SaaS workloads have recovered and are running normally. We are now monitoring the recovery and the cluster capacity in the region. We will post another update once Google has fully restored the affected zone or if anything changes.

5. resolved Oct 20, 2026, 01:21 PM UTC

   The issue has been resolved. Google has restored zone europe-west2-b in the London region, and new nodes can be created there again. All affected workloads have recovered and are running normally. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Aug 08, 2026, 08:00 PM UTC· resolved Aug 08, 2026, 09:57 PM UTC

1. investigating Aug 08, 2026, 09:52 PM UTC

   We are currently investigating reports of degraded performance of Camunda's Web Modeler offering. Our team is working to identify the cause and implement a solution.

2. identified Aug 08, 2026, 09:54 PM UTC

   The issue has been identified as caused by database lock contention from the background cleanup of recently deleted items. We are working to mitigate the issue.

3. identified Aug 08, 2026, 09:55 PM UTC

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

4. resolved Aug 08, 2026, 09:57 PM UTC

   A hotfix was deployed to mitigate the issue. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Jul 02, 2026, 07:34 PM UTC· resolved Jul 02, 2026, 07:36 PM UTC

1. identified Jul 02, 2026, 07:34 PM UTC

   Earlier today, starting around 10:20 AM EDT (14:20 UTC), Web Modeler SaaS became unresponsive for a short period after the release of version 8.9.31. The issue was identified as a Flyway migration-related problem, and we mitigated it by rolling back to version 8.9.30.

2. resolved Jul 02, 2026, 07:36 PM UTC

   The issue has been resolved. Earlier today, starting around 10:20 AM EDT (14:20 UTC), Web Modeler SaaS was unresponsive for a couple of minutes after the release of version 8.9.31. We mitigated the issue by rolling back to version 8.9.30, which restored service. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Jun 18, 2026, 09:42 AM UTC· resolved Jun 18, 2026, 09:43 AM UTC

1. monitoring Jun 18, 2026, 09:42 AM UTC

   test

2. resolved Jun 18, 2026, 09:43 AM UTC

   Test done

Read the full incident report →

Started May 08, 2026, 05:43 AM UTC· resolved May 08, 2026, 09:43 AM UTC

1. identified May 08, 2026, 05:43 AM UTC

   The issue has been identified as AWS incident in availability zone use1-az4/us-east-1b. We are working to mitigate the issue and will provide an update in the next 2hrs. Affected Region: AWS - US-EAST-1 Summary of AWS incident - https://health.aws.amazon.com/health/status AWS is currently experiencing an infrastructure issue in one Availability Zone of the US-EAST-1 region, caused by elevated temperatures in a single data center. As a result, some compute and storage resources in that zone are operating with reduced availability or increased latency. Other zones in US-EAST-1 are unaffected. AWS reports early signs of recovery: additional cooling capacity has been brought online and affected hardware is being restored in a controlled manner. Some workloads in the impacted zone may continue to see elevated error rates until full recovery is complete. We are actively monitoring the situation and will share further updates as the situation evolves.

2. monitoring May 08, 2026, 07:06 AM UTC

   We continue to monitor the ongoing AWS infrastructure issue affecting one Availability Zone in the US-EAST-1 region. AWS reports continued progress toward recovery, with most affected hardware already restored. A small number of resources may still see elevated error rates or latency until AWS completes full recovery. Most customer workloads have returned to normal operation. We are actively restoring the few remaining impacted services and will share another update once AWS provides their next status report (expected by 12:00 CEST).

3. monitoring May 08, 2026, 09:41 AM UTC

   We are continuing to monitor for any further issues.

4. resolved May 08, 2026, 09:43 AM UTC

   The issue has been resolved. AWS infrastructure issue affecting one availability zone in the US-EAST-1 region. reference: https://health.aws.amazon.com/health/status We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Apr 22, 2026, 04:29 PM UTC· resolved Apr 22, 2026, 06:29 PM UTC

1. resolved Apr 23, 2026, 10:44 AM UTC

   On April 22, 2026, from 18:29 UTC to 19:01 UTC (32 minutes), Camunda 8 SaaS experienced a login outage caused by an incident at Auth0, our external authentication provider. During this period, new sign-ins to C8 SaaS were not possible for affected users. Existing sessions remained unaffected. The root cause was fully on Auth0's side and outside Camunda's control. Auth0 resolved the incident at 19:01 UTC, after which login functionality was restored automatically. Reference: Auth0 incident report: https://status.auth0.com/incidents/04dsyk887lv6

Read the full incident report →

Started Feb 06, 2026, 02:49 PM UTC· resolved Feb 06, 2026, 03:04 PM UTC

1. identified Feb 06, 2026, 02:49 PM UTC

   The issue has been identified. We are working to mitigate the issue and will provide an update in the next 30min. Affected Versions: All C8 SaaS Affected Regions: - Belgium, Europe (europe-west1) - South Carolina, North America, (us-east1)

2. resolved Feb 06, 2026, 03:04 PM UTC

   The issue has been resolved. There was an issue with our ingress. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Nov 18, 2025, 11:59 AM UTC· resolved Nov 18, 2025, 03:03 PM UTC

1. identified Nov 18, 2025, 11:59 AM UTC

   We are aware of a network issue affected the whole Camunda SaaS platform. We are working to mitigate the issue and will provide an update in the next [30min].

2. identified Nov 18, 2025, 12:13 PM UTC

   Camunda SaaS is currently impacted by an on-going issue with our service provider Cloudflare. Our team is working to mitigate the issue and will provide an update within the next hour.

3. monitoring Nov 18, 2025, 12:20 PM UTC

   Camunda is observing recovery, but does not yet have confirmation from Cloudflare that the issue is fully resolved. We are continuing to monitor and will post another update within the hour.

4. monitoring Nov 18, 2025, 01:12 PM UTC

   Camunda is observing recovery, but does not yet have confirmation from Cloudflare that the issue is fully resolved. We are continuing to monitor and will post another update within the hour.

5. monitoring Nov 18, 2025, 02:03 PM UTC

   Camunda 8 SaaS services are now restored. Connector services are functional but are unable to reach marketplace.camunda.com Camunda continues to monitor updates from Cloudfare about its restoration efforts.

6. resolved Nov 18, 2025, 03:03 PM UTC

   The incident is now resolved for Camunda 8 SaaS.

Read the full incident report →

Started Nov 03, 2025, 11:05 PM UTC· resolved Nov 03, 2025, 11:49 PM UTC

1. investigating Nov 03, 2025, 11:05 PM UTC

   We are currently investigating reports of user seeing 404 when navigating to Operate, Tasklist and Optimize due to issues with Authentication. Our team is working to identify the cause and implement a solution. Affected Regions: Sydney, Australia (syd-1)

2. monitoring Nov 03, 2025, 11:38 PM UTC

   A fix has been implemented and we are monitoring the situation to ensure stability. Further updates will be provided as necessary. Sydney, Australia (syd-1)

3. resolved Nov 03, 2025, 11:49 PM UTC

   The issue has been resolved. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Oct 30, 2025, 04:54 PM UTC· resolved Oct 30, 2025, 06:30 PM UTC

1. investigating Oct 30, 2025, 04:54 PM UTC

   We are currently investigating issues with Connectors after an upgrade to 8.8. Our team is working to identify the cause and implement a solution.

2. identified Oct 30, 2025, 05:25 PM UTC

   Camunda Clusters running version 8.8 with app-integrations enabled are currently experiencing a service disruption affecting Connectors; when using this early access alpha feature. We’ve identified the root cause as a malformed configuration introduced in this version. A software fix has been developed and is currently undergoing testing in our integration environments.

3. monitoring Oct 30, 2025, 06:24 PM UTC

   We are in the process of rolling out the configuration fix across our fleet of clusters. The rollout is being performed gradually. We are closely monitoring all environments as the update progresses.

4. resolved Oct 30, 2025, 06:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 28, 2025, 11:42 AM UTC· resolved Oct 28, 2025, 04:02 PM UTC

1. investigating Oct 28, 2025, 11:42 AM UTC

   We are currently investigating alerts of stuck updates. The health information in our SaaS Console calculates that the update process is ongoing. However, the update is already finished. We identified that the health logic incorrectly takes into account the legacy importer from the prior version. Impact: Incorrect health states in our SaaS Console and issues by dependent systems that take the health state into account. Affected Versions: Clusters that were updated to SaaS Generation 8.8gen2

2. identified Oct 28, 2025, 12:51 PM UTC

   We’ve identified an issue with the health evaluation logic in our Control Plane and are actively working on a fix. In the meantime, we’re manually triaging affected clusters to move them out of the “Update” state. The Camunda cluster itself is available and not affected from this.

3. identified Oct 28, 2025, 01:28 PM UTC

   We have developed a fix addressing the Control Plane health logic issue. The update is currently being tested and validated in our development and staging environments to ensure stability before production release. We’ve also completed triage of all Enterprise clusters to ensure the issue is not affecting the interactions in our SaaS Console.

4. resolved Oct 28, 2025, 04:02 PM UTC

   The incident has been resolved. The fix has been successfully deployed to all production systems, and normal operation has been fully restored.

Read the full incident report →

Started Oct 20, 2025, 09:49 AM UTC· resolved Oct 21, 2025, 07:46 AM UTC

1. 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)

2. identified Oct 20, 2025, 09:50 AM UTC

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

3. 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.

4. 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.

5. monitoring Oct 20, 2025, 01:04 PM UTC

   We are still seeing issues coming from our cloud provider and we keep monitoring the situation.

6. 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.

7. 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.

Read the full incident report →

Started Sep 25, 2025, 01:22 AM UTC· resolved Sep 25, 2025, 01:55 AM UTC

1. identified Sep 25, 2025, 01:22 AM UTC

   On all GCP regions, C8 workloads cannot start due to images not being pulled. As a result, pods cannot be started and C8 SaaS clusters can be in Unhealthy status. This affects different customers. Our team is working to identify the cause and implement a solution. Affected Regions: South Carolina, North America (us-east1), Iowa, North America (us-central1), Toronto, North America (northamerica-northeast2), Belgium, Europe (europe-west1), London, Europe (europe-west2), Sydney, Australia (australia-southeast1)

2. resolved Sep 25, 2025, 01:55 AM UTC

   The issue has been resolved. The images could not be fetched due to problems with authentication with Dockerhub caused by an issue on their side. Details of the issue are shared in the Dockerhub statuspage - https://www.dockerstatus.com/pages/history/533c6539221ae15e3f000031 We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Jun 12, 2025, 07:23 PM UTC· resolved Jun 12, 2025, 09:05 PM UTC

1. identified Jun 12, 2025, 07:23 PM UTC

   We are currently experiencing a service disruption affecting Camunda Cloud 8 due to a widespread issue with Google Cloud’s Identity and Access Management (IAM) service. This ongoing incident is impacting multiple Google Cloud services, including authentication and authorization mechanisms that are critical to our platform’s availability and functionality. As a result, some customers may observe issues such as: - Failures in API requests - Deployment errors or timeouts - Delays in provisioning or accessing cluster This incident affects multiple regions globally, including all major GCP regions where Camunda Cloud 8 is hosted. ## Google Cloud Status: Google’s engineering teams are actively mitigating the issue and have reported signs of recovery in select regions. However, full restoration across all regions has not yet been confirmed. Google has not provided an estimated time to resolution (ETA). ## Next Update: We will continue to monitor the situation closely and provide updates as soon as more information becomes available or when recovery is confirmed across all impacted regions. ## Customer Impact: This incident is external to Camunda infrastructure, and we are dependent on Google Cloud’s resolution efforts. We understand the inconvenience this may cause and appreciate your patience while Google works toward full mitigation. For real-time updates, you may also refer to the [Google Cloud Status Dashboard](https://status.cloud.google.com/).

2. identified Jun 12, 2025, 07:45 PM UTC

   Google Cloud has confirmed that the root cause of the ongoing Identity and Access Management (IAM) service disruption has been identified and mitigated. Recovery is progressing across affected services. At this time, all impacted Camunda 8 clusters should be recovering, except for those hosted in Iowa, North America (us-central1). Customers with clusters in us-central1 may continue to experience degraded performance or service interruptions. Google has stated that: - All locations except us-central1 have fully recovered. - us-central1 is mostly recovered, but some issues remain. - No ETA is currently available for full recovery. Customer Impact: If your Camunda 8 cluster is located outside of us-central1, services should be stabilizing. For clusters in us-central1, degraded behavior may persist until Google completes its recovery efforts. Next Update: We will continue to monitor the situation closely and will provide an update when we have confirmation of full recovery, or if additional information becomes available. You can also follow ongoing progress on the Google Cloud Status Dashboard https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW.

3. identified Jun 12, 2025, 08:33 PM UTC

   Google Cloud has provided another update regarding the ongoing Identity and Access Management (IAM) service disruption. While the root cause has been identified and mitigations have been applied, infrastructure recovery is still incomplete in the us-central1 (Iowa) region. Google reports that multiple products are gradually recovering, but some customers may continue to experience issues, particularly in us-central1. For Camunda 8: - All clusters outside of us-central1 remain fully operational. - Clusters in us-central1 show signs of partial recovery, but degraded performance and service interruptions may still occur. There is still no official ETA from Google for full service restoration in the affected regions. Customer Impact: If your Camunda 8 cluster is located in GCP Iowa region, you may still encounter instability. We are closely monitoring cluster health and continue to coordinate with Google Cloud to ensure full restoration. No further action is required from you at this time. Next Update: We will share another update by 2025-06-12 14:30 PDT, or earlier if there are significant developments. We appreciate your continued patience and will keep you informed.

4. monitoring Jun 12, 2025, 08:48 PM UTC

   Google Cloud has confirmed that the IAM service disruption has been mitigated and recovery has progressed across all affected regions, including Iowa, North America (us-central1). Camunda 8 Cluster Status: All Camunda 8 clusters, including those in us-central1, have now recovered. Our internal monitoring shows services are operating normally. Next Steps: We will continue to monitor closely for any signs of regression and will take immediate action if needed. Thank you for your patience during this incident.

5. resolved Jun 12, 2025, 09:05 PM UTC

   Google Cloud has implemented additional mitigation for the Identity and Access Management (IAM) service issue impacting us-central1 and multi-region/us. Recovery is ongoing, and Google has indicated that full service restoration is expected within the hour. Camunda 8 Status: All Camunda 8 SaaS clusters, including those hosted in us-central1, are currently healthy. We have not observed any active alerts, and services are operating normally.

Read the full incident report →

Started May 21, 2025, 02:26 PM UTC· resolved May 21, 2025, 04:38 PM UTC

1. identified May 21, 2025, 02:26 PM UTC

   We are currently investigating reports of instances of IDP process extractions initiated on web-modeler that never complete. Our team is working to identify the cause and implement a solution. Affected Versions: Camunda 8.7.2 SaaS Affected Regions: Belgium, Europe (europe-west1), London, Europe (europe-west2) Franfkurt, Europe (eu-central-1) South Carolina, North America (us-east1) Iowa, North America (us-central1) Toronto, North America (northamerica-northeast2) Virgnia, North America (us-east-1) Singapore, Asia (asia-southeast1) Sydney, Australia (australia-southeast1)

2. resolved May 21, 2025, 04:38 PM UTC

   The issue has been resolved. We deployed a hotfix that addressed the problem. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started May 20, 2025, 05:10 AM UTC· resolved May 20, 2025, 12:48 PM UTC

1. identified May 20, 2025, 05:10 AM UTC

   We are currently investigating Zeebe outage for some clusters. Our team is working to identify the cause and implement a solution. Affected Regions: Iowa, North America (us-central1) & London, Europe (europe-west2)

2. identified May 20, 2025, 06:02 AM UTC

   We are currently investigating the problem with our cloud provider support engineers.

3. identified May 20, 2025, 06:42 AM UTC

   We are continuing our investigation of Zeebe and Elasticsearch outage for some clusters. In some cases, disks cannot be mounted. This can lead to situations, where either Zeebe processing, or data imported into WebApps (Operate, Tasklist, Optimize), or both, are impacted. Affected Regions: Iowa, North America (us-central1), Belgium, Europe (europe-west1), London, Europe (europe-west2), South Carolina, North America (us-east1), Toronto, North America (northamerica-northeast2), Toronto, North America (northamerica-northeast2), Sydney, Australia (australia-southeast1)

4. identified May 20, 2025, 08:24 AM UTC

   We are working closely with our cloud infrastructure provider to identify the cause of the issue. In some cases, disks cannot be mounted. This can lead to situations where either Zeebe processing, data imported into WebApps (Operate, Tasklist, Optimize), or both are impacted. Connectors might also be impacted due to transitivity with other affected components. Affected Regions: Iowa, North America (us-central1), Belgium, Europe (europe-west1), London, Europe (europe-west2), South Carolina, North America (us-east1), Toronto, North America (northamerica-northeast2), Toronto, North America (northamerica-northeast2), Sydney, Australia (australia-southeast1)

5. identified May 20, 2025, 09:38 AM UTC

   Our teams continue working closely with our cloud infrastructure provider to identify the cause of the issue and implement a solution

6. identified May 20, 2025, 10:35 AM UTC

   Our teams are actively implementing mitigations while continuing to investigate the root cause in collaboration with our cloud infrastructure provider.

7. identified May 20, 2025, 11:31 AM UTC

   We are observing improvements across all regions and we continue to closely monitor the situation to ensure full stability.

8. resolved May 20, 2025, 12:48 PM UTC

   The issue causing unavailability of disks in some GCP regions has been resolved by our cloud infrastructure provider. All Camunda Services have fully recovered. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started May 19, 2025, 03:19 PM UTC· resolved May 22, 2025, 07:23 AM UTC

1. identified May 19, 2025, 03:19 PM UTC

   We have identified an issue with the Tasklist update from 8.3.x to 8.4.20 and 8.4.x to 8.5.15. After updating, the Tasklist importer will get stuck, leading to no new data being imported for Tasklist. General processing is *not* affected. We have the issue identified and are working on a fix asap. We have temporarily disabled updates in SaaS.

2. resolved May 22, 2025, 07:23 AM UTC

   The issue has been resolved. Tasklist update paths are restored. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Apr 09, 2025, 09:04 AM UTC· resolved Apr 09, 2025, 05:36 PM UTC

1. identified Apr 09, 2025, 09:04 AM UTC

   We disabled the update path from 8.6.13 to 8.7.0 because of a bug we identified after the update, that led to stopped Zeebe processing in some situations where multi-instances were in use. We are preparing an 8.7.1 patch, which will allow full recovery of affected clusters. No risk of data loss exists. Affected Versions: 8.6.13 to 8.7.0 update

2. identified Apr 09, 2025, 09:05 AM UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

3. resolved Apr 09, 2025, 05:36 PM UTC

   The issue has been resolved. Update paths have been re-enabled. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Jan 15, 2025, 10:47 AM UTC· resolved Jan 17, 2025, 08:13 PM UTC

1. identified Jan 15, 2025, 10:47 AM UTC

   We have identified an issue with Camunda 8.7-alpha3 on SaaS. This issue leads to data not appearing in Operate and Tasklist. We have disabled the creation of new alpha3 clusters. We have identified the root cause and are working on the solution. We expect the solution to be rolled out on Thursday (16/01). Once the solution has been rolled out, we will re-enable the creation of alpha3 SaaS clusters. Existing alpha3 will be reset once the solution is rolled out. Processes have to be re-deployed. Affected Versions: Camunda 8.7-alpha3 SaaS Affected Regions: Global

2. identified Jan 16, 2025, 04:14 PM UTC

   We have a solution in test and expect it to be rolled out on Friday (17/01). Once the solution has been rolled out, we will re-enable the creation of alpha3 SaaS clusters. Existing alpha3 will be reset once the solution is rolled out. Processes have to be re-deployed. Affected Versions: Camunda 8.7-alpha3 SaaS Affected Regions: Global

3. resolved Jan 17, 2025, 08:13 PM UTC

   The generation 8.7.0-alpha3 is available again, functional and the new default in the alpha channel. Thanks for your patience!

Read the full incident report →

Started Nov 07, 2024, 05:22 PM UTC· resolved Nov 07, 2024, 05:24 PM UTC

1. identified Nov 07, 2024, 05:22 PM UTC

   We have identified an issue where a small number of Optimize instances were not starting between 12:00 and 17:00. This only impacted new Optimize 8.6.1 instances. No other components are affected and we have not identified any data corruption. We apologize for any inconvenience caused and thank you for your patience, and have already applied a fix for impacted clusters.

2. resolved Nov 07, 2024, 05:24 PM UTC

   The fix has already been applied and Optimize is now available on all impacted clusters.

Read the full incident report →