Hatchet experienced a minor incident on November 13, 2025 affecting API (cloud.hatchet.run) and API (Hatchet API), lasting 21h 27m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 13, 2025, 10:39 PM UTC
We have received reports for issues on enqueuing and assigning runs, we are currently investigating and working on a resolution.
- resolved Nov 14, 2025, 08:06 PM UTC
On November 13, 2025, beginning at approximately 4:55 PM EST, our shared cloud environment experienced disruptions to queueing and monitoring for approximately one hour. The root cause was identified as a RabbitMQ memory saturation issue, which caused the message broker to enter an unrecoverable state. We have since restored full service, implemented monitoring improvements, and are working on several action items to prevent recurrence. This primarily impacted Free, Starter and Growth tier tenants, and did not impact tenants on the enterprise or dedicated plans.