Resolved after 31 minutes, affecting API (cloud.hatchet.run) and API (Hatchet API), on July 29, 2026.
We saw elevated database load on our shared production environment beginning around 05:00 UTC, which caused some multi-step workflows to experience scheduling delays and increased API/dashboard latency for affected tenants. We reduced connection pressure on the shared database and latency has returned to normal. We’re continuing to monitor closely.
Affected components
Update timeline
- investigating Jul 29, 2026, 07:56 AM UTC
We're monitoring increased latency on a single shared cloud shard in our us-west-2 region experienced elevated database lock contention, which is causing higher API and scheduling latency and some intermittent task-dispatch delays for tenants on that shard. Tasks are continuing to be ingested and assigned.
- investigating Jul 29, 2026, 08:20 AM UTC
We have pushed some configuration changes and are seeing initial signs of improvement. We will continue to monitor the situation.
- resolved Jul 29, 2026, 08:27 AM UTC
We saw elevated database load on our shared production environment beginning around 05:00 UTC, which caused some multi-step workflows to experience scheduling delays and increased API/dashboard latency for affected tenants. We reduced connection pressure on the shared database and latency has returned to normal. We’re continuing to monitor closely.
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