Is Camunda down?

Last checked 6m ago
Current status
Camunda is up

No incidents right now.

Official status page: https://status.camunda.io · Polled every 5 minutes · 8 components tracked

Camunda is operational right now. Last checked 6m ago; the most recent incident resolved 23d ago.

Real-time Camunda status, recent outages, and incident history — pulled directly from Camunda's official status page at https://status.camunda.io every 5 minutes. Pingoru tracks 8 Camunda services and has captured 5 incidents in the last 90 days (99.86% uptime). Get email, Slack, Discord, or webhook alerts the moment Camunda reports a new incident — free for 5 monitors, no credit card.

Users who monitor Camunda also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Camunda uptime 99.86% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1m
    Started Jul 02, 2026, 07:34 PM UTC · Resolved Jul 02, 2026, 07:36 PM UTC
    Modeler
    Timeline · 2 updates
    • 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.

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

    Latest: 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.…

  2. Resolved 57s
    Started Jun 18, 2026, 09:42 AM UTC · Resolved Jun 18, 2026, 09:43 AM UTC
    Timeline · 2 updates
    • monitoring · Jun 18, 2026, 09:42 AM UTC

      test

    • resolved · Jun 18, 2026, 09:43 AM UTC

      Test done

    Latest: Test done

  3. Resolved 3h 59m
    Started May 08, 2026, 05:43 AM UTC · Resolved May 08, 2026, 09:43 AM UTC
    Zeebe
    Timeline · 4 updates
    • 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.

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

    • monitoring · May 08, 2026, 09:41 AM UTC

      We are continuing to monitor for any further issues.

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

    Latest: 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 f…

Outage history

Past 90 days · 3 incidents View full outage history →