outages.live
Live
HatchetMaintenance ·

Scheduled maintenance

MaintenanceOfficial update

We will perform scheduled maintenance across all regions, including dedicated environments, on Saturday from 19:00 to 21:00 UTC. You may see a brief interruption of up to one minute at some point during this window. Workloads will retry automatically, though scheduling may be delayed during this time. No action is required.

The latest update from Hatchet.

State

Maintenance

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Hatchet

Maintenance

We will perform scheduled maintenance across all regions, including dedicated environments, on Saturday from 19:00 to 21:00 UTC. You may see a brief interruption of up to one minute at some point during this window. Workloads will retry automatically, though scheduling may be delayed during this time. No action is required.

Affected components

2
Hatchet APIcloud.hatchet.run

Hatchet in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

41 min

This incident

Not comparable

Other Hatchet incidents

All incidents

Hatchet·[us-west-2] Increased latency for some customers in us-west-2

Latency issues have resolved on this instance

Resolved

Follow Hatchet

Your coding agent knows when Hatchet is down, and tells you when a failure is theirs, not yours. You can also get Hatchet incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "hatchet" and tell me if Hatchet has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=hatchet
Slack
/feed subscribe https://outages.live/feed.xml?providers=hatchet

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane