Camunda incident

C8 SaaS clusters can be unhealthy status due to images not being pulled

Critical Resolved View vendor source →

Camunda experienced a critical incident on September 25, 2025, lasting 33m. The incident has been resolved; the full update timeline is below.

Started
Sep 25, 2025, 01:22 AM UTC
Resolved
Sep 25, 2025, 01:55 AM UTC
Duration
33m
Detected by Pingoru
Sep 25, 2025, 01:22 AM UTC

Update timeline

  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.