Hatchet incident

us-west-2 increased latency

Major Resolved View vendor source →

Hatchet experienced a major incident on June 19, 2026 affecting API (cloud.hatchet.run) and API (Hatchet API), lasting 1d 21h. The incident has been resolved; the full update timeline is below.

Started
Jun 19, 2026, 11:00 PM UTC
Resolved
Jun 21, 2026, 08:00 PM UTC
Duration
1d 21h
Detected by Pingoru
Jun 19, 2026, 11:00 PM UTC

Affected components

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

Update timeline

  1. investigating Jun 19, 2026, 11:00 PM UTC

    Hatchet's shared cloud (free, team, and scale plans) in us-west-2 experienced a partial outage between 6/19/26 23:07:00 UTC and 6/20 and 00:34:00 UTC caused by crashes on an internal queue. We were alerted and responded immediately, which brought the service online. Task processing (e.g. dispatching tasks to workers) was affected, but ingestion was not. You may see stuck DAGs, which likely will need to be cancelled and replayed or retriggered from scratch to reconcile. We'll continue to update as we investiage the root cause of the message queue crash.

  2. resolved Jun 21, 2026, 08:00 PM UTC

    We’re back! Hatchet Cloud region us-west-2 should be up and running. Thanks for bearing with us.