Resolved after 1 day 21 hours, affecting API (cloud.hatchet.run) and API (Hatchet API), on June 19, 2026.
We’re back! Hatchet Cloud region us-west-2 should be up and running. Thanks for bearing with us.
Affected components
Update timeline
- 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.
- 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.
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.
Amazon Web Services