Hatchet incident

Elevated latency on US West (Oregon) cloud shard

Resolved on July 24, 2026, affecting API (cloud.hatchet.run) and API (Hatchet API).

resolved Jul 24, 2026, 11:14 AM UTC

Between approximately 05:00–10:00 UTC on July 24, the shared cloud shard in our us-west-2 region experienced elevated database lock contention, which caused higher API and scheduling latency and some intermittent task-dispatch delays for tenants on that shard. This was isolated to a single shard in us-west-2 (cloud). Other regions and shards were not affected. We have no evidence of dropped workload, and all assignments were eventually completed. We are continuing to investigate and monitor.

Other major vendors with incidents that started within 30 minutes of this one

Auth0 Outage Regional Service Disruption on Public Cloud Environments

Render Outage Service Disruption in Oregon

Okta Outage Service Disruption - Timeouts and Login Failures

Adobe Creative Cloud Outage Mixamo

Zendesk Outage Unable to Access Zendesk

Amazon Web Services Outage Multiple services — Oregon: [RESOLVED] Connectivity Issues

And 2 more: Notion, Cloudflare.

Started: Jul 24, 2026, 11:14 AM UTC
Resolved: Jul 24, 2026, 11:14 AM UTC
Duration: –
Detected by Pingoru: Jul 24, 2026, 11:14 AM UTC

Affected components

API (cloud.hatchet.run)API (Hatchet API)

Update timeline

resolved Jul 24, 2026, 11:14 AM UTC

Between approximately 05:00–10:00 UTC on July 24, the shared cloud shard in our us-west-2 region experienced elevated database lock contention, which caused higher API and scheduling latency and some intermittent task-dispatch delays for tenants on that shard. This was isolated to a single shard in us-west-2 (cloud). Other regions and shards were not affected. We have no evidence of dropped workload, and all assignments were eventually completed. We are continuing to investigate and monitor.

Your product runs on more than Hatchet

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.