- Level
- confirmed
- Worst impact
- Degraded
- Components
- Ashby API
- Down Index
- 23of 100
What to do
Check whether you use Ashby Ashby API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 6h 16m it lasted.
Anything that failed between 2026-07-27 14:56 UTC and 2026-07-27 21:12 UTC may need a replay.Subscribe to Ashby's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=ashby works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Ashby 4
- investigating
We are experiencing elevated latency on the Ashby API available at api.ashbyhq.com, requests may take longer to be processed or time out altogether. The Engineering team is investigating the issue.
provider
- identified
We have mitigated the issue, and response times have returned to normal. We will continue to work towards full resolution.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9086a23530
Is Ashby still down?
No, this incident was resolved 2026-07-27 21:12 UTC. For Ashby's live state, see https://down.guide/ashby.
How long did it last?
6h 16m, from 2026-07-27 14:56 UTC to 2026-07-27 21:12 UTC, by the times Ashby posted.
What was affected?
Ashby named Ashby API.
What caused it?
Ashby hasn't published a root cause. If it does, it shows here.
Where does this come from?
Ashby's official status page, https://status.ashbyhq.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.