User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 22 min ago. Last stored result reached it in 225 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 255 ms | 0 |
| Mon 20 | 0 | 0.0 | 203 ms | 0 |
| Mon 23 | 0 | 0.0 | 191 ms | 0 |
| Tue 01 | 0 | 0.0 | 180 ms | 0 |
| Tue 03 | 0 | 0.0 | 250 ms | 0 |
| Tue 05 | 0 | 0.0 | 188 ms | 0 |
| Tue 07 | 0 | 0.0 | 330 ms | 0 |
| Tue 09 | 0 | 0.0 | 184 ms | 0 |
| Tue 11 | 0 | 0.0 | 188 ms | 0 |
| Tue 13 | 0 | 0.0 | 203 ms | 0 |
| Tue 16 | 0 | 0.0 | 245 ms | 0 |
| Tue 18 | 0 | 0.0 | 192 ms | 0 |
| Tue 20 | 0 | 0.0 | 268 ms | 0 |
| Tue 22 | 0 | 0.0 | 252 ms | 0 |
| Wed 01 | 0 | 0.0 | 357 ms | 0 |
| Wed 03 | 0 | 0.0 | 324 ms | 0 |
| Wed 05 | 0 | 0.0 | 215 ms | 0 |
| Wed 07 | 0 | 0.0 | 258 ms | 0 |
| Wed 10 | 0 | 0.0 | 336 ms | 0 |
| Wed 12 | 0 | 0.0 | 252 ms | 0 |
| Wed 14 | 0 | 0.0 | 269 ms | 0 |
| Wed 16 | 0 | 0.0 | 267 ms | 0 |
| Wed 18 | 0 | 0.0 | 270 ms | 0 |
| Wed 20 | 0 | 0.0 | 277 ms | 0 |
| Wed 23 | 0 | 0.0 | 242 ms | 0 |
| Thu 01 | 0 | 0.0 | 300 ms | 0 |
| Thu 03 | 0 | 0.0 | 170 ms | 0 |
| Thu 05 | 0 | 0.0 | 242 ms | 0 |
| Thu 07 | 0 | 0.0 | 204 ms | 0 |
| Thu 09 | 0 | 0.0 | 292 ms | 0 |
| Thu 11 | 0 | 0.0 | 273 ms | 0 |
| Thu 13 | 0 | 0.0 | 252 ms | 0 |
| Thu 15 | 0 | 0.0 | 289 ms | 0 |
| Thu 17 | 0 | 0.0 | 217 ms | 0 |
| Thu 19 | 0 | 0.0 | 289 ms | 0 |
| Thu 21 | 0 | 0.0 | 293 ms | 0 |
| Fri 00 | 0 | 0.0 | 241 ms | 0 |
| Fri 02 | 0 | 0.0 | 211 ms | 0 |
| Fri 04 | 0 | 0.0 | 380 ms | 0 |
| Fri 06 | 0 | 0.0 | 267 ms | 0 |
| Fri 08 | 0 | 0.0 | 246 ms | 0 |
| Fri 10 | 0 | 0.0 | 222 ms | 0 |
| Fri 11 | 0 | 0.0 | 204 ms | 0 |
| Fri 13 | 0 | 0.0 | 215 ms | 0 |
| Fri 15 | 0 | 0.0 | 181 ms | 0 |
| Fri 17 | 0 | 0.0 | 341 ms | 0 |
| Fri 19 | 0 | 0.0 | 289 ms | 0 |
| Fri 21 | 0 | 0.0 | 225 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Hatchet yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Hatchet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Hatchet alerts to Slack, Discord or a webhook — free.
Hatchet, at hatchet.run, is one of the AI services we monitor. Hatchet is a single platform for orchestrating AI agents, scheduling background tasks, and running mission-critical workflows.
Hatchet publishes an official status page at status.hatchet.run; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 251 ms average, 181–380 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Hatchet incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
251 ms on average over the last 24 hours (181–380 ms).
Yes, at https://status.hatchet.run.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Hatchet here at once, the problem is on Hatchet's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Hatchet. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.