checked Sep 7, 2026 10:31 PM UTC · Coalesce's official status page
Coalesce is up and running.
All components operational
Statusfield watches Coalesce alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
3 reports published by Coalesce in the last 30 days
When Coalesce breaks, it is typically resolved in 1h 2m — median across 7 resolved incidents over 90 days.
resolvedSep 2 · 15:51 UTC
This incident is resolved. This incident was caused by a recent update that lacked backwards compatibility with prior versions of the coa CLI. The resolution was to follow up with another update restoring the backwards compatibility.
Reported by Coalesce on their status page.
resolvedSep 1 · 18:28 UTC
Between approximately 10:00 and 12:00 UTC today, some customers experienced delayed or stuck job runs for our Transform customers in North America. During a routine, provider-managed Kubernetes upgrade in one of our US regions, our cloud provider was unable to provision replacement compute capacity. We experienced a similar issue on August 17th as described here: https://status.coalesce.io/incidents/43zcl3trbjxx We took steps after that prior incident to prevent provider upgrades from effecting our customers but those changes were not sufficient. We are currently making the following changes: - Expanded Capacity Buffers: We are adding supplementary node pools (using C3/C3D machine types) alongside our primary pools to act as an immediate capacity buffer if our primary hardware type is unavailable. - Automated Job Cleanup: We deployed an improvement to our job lifecycle management where delayed or stuck jobs now cleanly self-terminate, instantly freeing up resources for healthy jobs. - Resilient Compute Architecture: We are actively implementing GKE Compute Classes, which will allow our infrastructure to automatically draw from up to six different machine types, eliminating our reliance on a single hardware type during cloud provider shortages.
Reported by Coalesce on their status page.
resolvedAug 17 · 13:40 UTC
Between approximately 10:00 and 13:30 UTC today, some customers experienced delayed or stuck job runs. During a routine, provider-managed Kubernetes upgrade in one of our US regions, our cloud provider was unable to provision replacement compute capacity. Instead of aborting, the upgrade proceeded to take existing nodes out of rotation, leaving the region without capacity to start new jobs. We rolled back the upgrade, restoring full scheduling capacity, and jobs are processing normally. We were forced to cancel older jobs that were unable to recover and recommend customers re-run any effected operations. We are adjusting our upgrade configuration and maintenance windows to prevent this scenario from recurring.
Reported by Coalesce on their status page.
