Changes / Ashby / DropBox Sign updates not reflecting in Ashby
Ashby: Major incident: DropBox Sign updates not reflecting in Ashby
Summary
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 diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: DropBox Sign updates not reflecting in Ashby
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-06-24 21:16 UTC
Before: not present
After: 2026-06-24 22:21 UTC
Before: not present
After: Dropbox Sign, Third-Party Integrations - Dropbox Sign
Before: not present
After: 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.
Before: not present
After: A fix has been implemented, and data is in the process of being recovered.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: DropBox Sign updates not reflecting in Ashby (this change) 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. | Major incident |