outages.live
Live
HatchetIncident · 2026-10-30 18:43 UTC

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

ResolvedOfficial update

Latency issues have resolved on this instance

The latest update from Hatchet.

State

Resolved

Started

2 d ago

2026-10-30 18:43 UTC

Lasted

41 min

until 2026-10-30 19:24 UTC

Worst impact

Degraded

Timeline

3 updates
18:4318:5319:0419:1419:24
DegradedUpdate postedTimes in UTC

Degraded

41 min 100%

Updates

Times in UTC

As posted by Hatchet

Resolved2026-10-30 19:24 UTC

Latency issues have resolved on this instance

Degraded2026-10-30 19:00 UTC

We've been recovering and are continuing to monitor

Degraded2026-10-30 18:43 UTC

Some customers in us-west-2 are currently experiencing increased latency as we perform routine maintenance on one of our core databases. We're monitoring and continuing to make progress, and will post an update once it's resolved. Note that this is only affecting users on shared infrastructure on a single legacy instance in us-west-2, not anyone on dedicated / custom / enterprise plans, or on newer instances.

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

About the median

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.cc/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.cc/feed.xml?providers=hatchet
Slack
/feed subscribe https://outages.cc/feed.xml?providers=hatchet

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane