- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Dropbox Sign
- Down Index
- 29of 100
What to do
Check whether you use Ashby Dropbox Sign. 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 1h 5m it lasted.
Anything that failed between 2026-06-24 21:16 UTC and 2026-06-24 22:21 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 3
- identified
Starting at 4:30PM (UTC), Ashby stopped being able to process inbound data from Dropbox Sign. E-Signature requests were sent, but status updates were not recorded.
provider
- monitoring
A fix has been implemented, and data is in the process of being recovered.
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-2bc91895bc
Is Ashby still down?
No, this incident was resolved 2026-06-24 22:21 UTC. For Ashby's live state, see https://down.guide/ashby.
How long did it last?
1h 5m, from 2026-06-24 21:16 UTC to 2026-06-24 22:21 UTC, by the times Ashby posted.
What was affected?
Ashby named Dropbox Sign.
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.