Hatchet incident

Elevated latency on US West (Oregon) cloud shard

Minor Resolved View vendor source →

Hatchet experienced a minor incident on July 24, 2026 affecting API (cloud.hatchet.run) and API (Hatchet API), lasting –. The incident has been resolved; the full update timeline is below.

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

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