Ashby: DropBox Sign updates not reflecting in Ashby
Major Dropbox Sign incident: Ashby could not process inbound data starting at 4:30PM (UTC); e-signature requests were sent, but status updates were not recorded. Tracked from 2026-06-24 21:16 UTC until resolution at 2026-06-24 22:21 UTC (1 h 4 min), after a fix was implemented and data recovery began.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Dropbox SignThird-Party Integrations - Dropbox Sign
Timeline of updates
- 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.
- monitoring
A fix has been implemented, and data is in the process of being recovered.
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Major incident: DropBox Sign updates not reflecting in Ashby 2026-06-24 21:16 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Ashby profile · Recent Ashby incidents · Markdown · JSON