Is Camunda down?
Last checked 2m agoNo incidents right now.
Camunda is operational right now. Last checked 2m ago; the most recent incident resolved 11d ago.
Real-time Camunda status, recent outages, and incident history: pulled directly from Camunda's official status page at status.camunda.io every 5 minutes. Pingoru tracks 9 Camunda services and has captured 4 incidents in the last 90 days (98.95% uptime). Get email, Slack, Discord, or webhook alerts the moment Camunda reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- ConnectorsOperateOptimizeTasklistZeebe
Timeline · 5 updates
- 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)
- 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.
- 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.
- 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.
- 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.
Latest: 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 r…
-
- Modeler
Timeline · 4 updates
- 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.
- 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.
- identified · Aug 08, 2026, 09:55 PM UTC
We are continuing to work on a fix for this issue.
- 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.
Latest: A hotfix was deployed to mitigate the issue. We apologize for any inconvenience caused and thank you for your patience.
-
-
Timeline · 1 update
- resolved · Aug 08, 2026, 09:48 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.
Latest: 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.
-
Incident record
Since April 2026 · Statuspage by Atlassian · 9 components checked every 5 minutesThe longest incident in the last year, C8 Incident - GKE Region europe-west2 on October 20, 2026, ran for 6 hours. 4 maintenance windows announced in the same period.
Most affected components, last 12 months
- Modeler4
- Operate4
- Optimize4
- Tasklist4
- Zeebe4
Latest incidents
- C8 Incident - GKE Region europe-west2
Our team is working to identify the cause and implement a solution. Affected Versions: All Affected Regions: GKE, London, Europe (europe-west2)
- Web Modeler performance degradation
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…
- Web Modeler performance degradation
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…
- Started Oct 20, 2026, 07:01 AM UTC · Resolved Oct 20, 2026, 01:21 PM UTC · 6h 19m
- Web Modeler performance degradation ResolvedStarted Aug 08, 2026, 08:00 PM UTC · Resolved Aug 08, 2026, 09:57 PM UTC · 1h 57m
- Web Modeler performance degradation ResolvedStarted Aug 08, 2026, 08:00 PM UTC · Resolved Aug 08, 2026, 08:00 PM UTC · –