User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
ashbyhq.com · AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 396 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 03 | 0 | 0.0 | 91 ms | 0 |
| Mon 04 | 0 | 0.0 | 107 ms | 0 |
| Mon 05 | 0 | 0.0 | 218 ms | 0 |
| Mon 06 | 0 | 0.0 | 119 ms | 0 |
| Mon 07 | 0 | 0.0 | 139 ms | 0 |
| Mon 08 | 0 | 0.0 | 159 ms | 0 |
| Mon 09 | 0 | 0.0 | 154 ms | 0 |
| Mon 10 | 0 | 0.0 | 88 ms | 0 |
| Mon 11 | 0 | 0.0 | 122 ms | 0 |
| Mon 12 | 0 | 0.0 | 205 ms | 0 |
| Mon 13 | 0 | 0.0 | 114 ms | 0 |
| Mon 14 | 0 | 0.0 | 269 ms | 0 |
| Mon 15 | 0 | 0.0 | 235 ms | 0 |
| Mon 16 | 0 | 0.0 | 95 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Ashby 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 Ashby goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ashby alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Ashby is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Ashby's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.