Is Coalesce down?

Last checked 1m ago
Current status
Coalesce is up

No active incidents. All 25 components operational.

Coalesce is operational right now. Last checked 1m ago; the most recent incident resolved 25d ago.

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

Users who monitor Coalesce also follow these Analytics services: New Relic Grafana Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch FullStory View all 8,000+ providers
Coalesce uptime 99.89% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 5m
    Started Oct 09, 2026, 06:21 PM UTC · Resolved Oct 09, 2026, 07:27 PM UTC
    Scheduler
    Timeline · 2 updates
    • identified · Oct 09, 2026, 06:21 PM UTC

      Transform users are currently unable to create jobs in their workspaces. We have identified the issue and working on a resolution. This only effects the creation of new jobs, previously created jobs are continuing to execute.

    • resolved · Oct 09, 2026, 07:27 PM UTC

      This issue has been resolved. Please reach out to our Support team if you are experiencing any issues.

    Latest: This issue has been resolved. Please reach out to our Support team if you are experiencing any issues.

  2. Resolved 14h 43m
    Started Sep 09, 2026, 01:33 AM UTC · Resolved Sep 09, 2026, 04:17 PM UTC
    APISchedulerWeb App
    Timeline · 3 updates
    • identified · Sep 09, 2026, 01:33 AM UTC

      Customers are experiencing OAuth authentication issues with Snowflake. We have identified the issue and are pushing out a fix.

    • monitoring · Sep 09, 2026, 03:35 AM UTC

      We have deployed a fix for anyone experiencing the following error when using OAuth with Snowflake: "error":"Unable to process OAuth callback! error=RPError: iss mismatch, expected snowflake, got: https://example.snowflakecomputing.com/oauth","errorDetail":"" This change introduces case sensitivity for the configured Snowflake URL. If you continue to receive the above error and have a mixed-case URL, a workaround is to change the URL to all lowercase.

    • resolved · Sep 09, 2026, 04:17 PM UTC

      This issue has been resolved.

    Latest: This issue has been resolved.

  3. Resolved 12h 55m
    Started Sep 02, 2026, 02:56 AM UTC · Resolved Sep 02, 2026, 03:51 PM UTC
    australia-southeast1
    Timeline · 3 updates
    • identified · Sep 02, 2026, 02:56 AM UTC

      Some of our customers in our APAC region are seeing jobs not completing. We have identified the root cause and will be releasing a fix shortly.

    • monitoring · Sep 02, 2026, 05:29 AM UTC

      A fix has been deployed and we will monitor for any issues. Further details when fully resolved.

    • resolved · Sep 02, 2026, 03:51 PM 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.

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

  4. Resolved –
    Started Sep 01, 2026, 06:28 PM UTC · Resolved Sep 01, 2026, 06:28 PM UTC
    us-central1
    Timeline · 1 update
    • resolved · Sep 01, 2026, 06:28 PM 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.

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

  5. Resolved 46m
    Started Aug 17, 2026, 12:54 PM UTC · Resolved Aug 17, 2026, 01:40 PM UTC
    Scheduler
    Timeline · 4 updates
    • investigating · Aug 17, 2026, 12:54 PM UTC

      We have identified an issue with jobs executing and investigating the root cause. We will update this incident when resolved.

    • investigating · Aug 17, 2026, 12:56 PM UTC

      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

    • monitoring · Aug 17, 2026, 01:17 PM UTC

      We have identified the issue and pushed a change to resolve job processing. More details to follow once fully resolved.

    • resolved · Aug 17, 2026, 01:40 PM 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.

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

Incident record

Since April 2026 · Statuspage by Atlassian · 25 components checked every 5 minutes
32incidents recorded
19last 12 months
5last 90 days
26 hourstypical duration, 12 months

The longest incident in the last year, Intermittent Job Timeouts on February 25, 2026, ran for 15 days. 8 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Scheduler13
  • Web App4
  • us-central13
  • API2
  • australia-southeast12

Latest incidents

  • Transform Job Creation Blocked October 9, 2026 · 65 minutes · degraded service

    Transform users are currently unable to create jobs in their workspaces. We have identified the issue and working on a resolution. This only effects the…

  • Transform Snowflake OAuth Errors September 9, 2026 · 15 hours · degraded service

    Customers are experiencing OAuth authentication issues with Snowflake. We have identified the issue and are pushing out a fix.

  • APAC Job Execution Failure September 2, 2026 · 13 hours · degraded service

    Some of our customers in our APAC region are seeing jobs not completing. We have identified the root cause and will be releasing a fix shortly.

Outage history

Past 90 days · 5 incidents View full outage history →