- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Ashby. 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 0m it lasted.
Anything that failed between 2026-07-06 20:46 UTC and 2026-07-06 18:30 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 1
- resolved
From 11:30am until 1:40pm PDT, candidate PDF exports failed with a generic message. The cause of this issue has already been identified and fixed.
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-f1c7b0decb
Is Ashby still down?
No, this incident was resolved 2026-07-06 18:30 UTC. For Ashby's live state, see https://down.guide/ashby.
How long did it last?
0m, from 2026-07-06 20:46 UTC to 2026-07-06 18:30 UTC, by the times Ashby posted.
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.