CompaniesDropbox SignIncidents
Dropbox Sign: API response time issues
Google Cloud outage, Nov 16, 2021 · 24 vendors, 25 incidents
Dropbox Sign’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +12 min vs the first vendor naming Google Cloud)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>6 vendors, 4 blamed Google Cloud<br/>Segment, Bugsnag, Twingate, Sigma Computing +2"]:::blames
root --> h1
h4["1 to 4 hours later<br/>2 vendors, 2 blamed Google Cloud<br/>Smartsheet, Grafana Cloud"]:::blames
root --> h4
me["Dropbox Sign (this incident)<br/>posted +12 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
The service has been healthy since our last update, and we have confidence the issue will not reoccur. Thank you for your patience.
From Dropbox Sign’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.hellosign.com (opens in new tab).
Dropbox Sign profileRecent Dropbox Sign incidentsMarkdownJSON