All Systems Operational

About This Site

We publish in real time the operational status of our systems as well as descriptions of historical incidents. Incidents published on this site may reflect downtime due to scheduled maintenance or issues related to external applications or third parties.

If you are experiencing an operational issue with our services please inform us so that we can assist you:

Web: https://support.coalesce.io
Email: support@coalesce.io

Catalog Operational
API Operational
Chrome Extension Operational
Microsoft Teams App Operational
Slack App Operational
Web App Operational
AI Capabilities Operational
Transform Operational
API Operational
Scheduler Operational
Web App Operational
Transform - AWS Operational
ap-southeast-2 Operational
eu-central-1 Operational
eu-west-2 Operational
us-east-1 Operational
us-east-2 Operational
us-west-2 Operational
Transform - GCP Operational
australia-southeast1 Operational
europe-west1 Operational
europe-west3 Operational
northamerica-northeast1 Operational
us-central1 Operational
us-east4 Operational
Transform - Azure Operational
centralus Operational
eastus2 Operational
southcentralus Operational
westus2 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Aug 22, 2026

No incidents reported today.

Aug 21, 2026

No incidents reported.

Aug 20, 2026

No incidents reported.

Aug 19, 2026

No incidents reported.

Aug 18, 2026

No incidents reported.

Aug 17, 2026

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

Aug 17, 13:40 UTC
Monitoring - We have identified the issue and pushed a change to resolve job processing. More details to follow once fully resolved.
Aug 17, 13:17 UTC
Update - We are investigating an issue affecting job runs for customers in our US region. A portion of scheduled and API-triggered job runs are failing to start. An affected run may remain in a Waiting state and then fail with the message "Run timed out. Restart the
run, and if this issue persists contact support." Runs that do start are completing normally.

Customers in our EU, Canada, and APAC regions are not affected. Our engineering team is actively investigating. We will post an update by 9:30 AM ET

Aug 17, 12:56 UTC
Investigating - We have identified an issue with jobs executing and investigating the root cause. We will update this incident when resolved.
Aug 17, 12:54 UTC

Aug 16, 2026

No incidents reported.

Aug 15, 2026

No incidents reported.

Aug 14, 2026

No incidents reported.

Aug 13, 2026

No incidents reported.

Aug 12, 2026

No incidents reported.

Aug 11, 2026

No incidents reported.

Aug 10, 2026

No incidents reported.

Aug 9, 2026

No incidents reported.

Aug 8, 2026

No incidents reported.