CompaniesDropbox SignIncidents
Dropbox Sign: Dropbox Sign was not working as expected for some users.
AWS us-east-1 outage, May 8, 2026 · 38 vendors, 43 incidents
Dropbox Sign’s incident blames AWS as the cause. (hop 1, posted +1 h 4 min vs AWS’s own post)
“…Dropbox Sign was not working as expected for some users. Dropbox Sign was impacted by AWS -EAST-1 outage, and some services may not have been working as expected from 00:25 to 00:53 UTC on May 8, 2026…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>posted 00:25 UTC"]:::root
before["Posted before AWS did<br/>3 vendors, 2 blamed AWS<br/>Neon, Datadog, Convex"]:::blames
root --> before
h1["Within an hour<br/>11 vendors, 11 blamed AWS<br/>Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
root --> h1
h4["1 to 4 hours later<br/>10 vendors, 9 blamed AWS<br/>Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
root --> h4
later["Later<br/>2 vendors, 2 blamed AWS<br/>Wiz, SingleStore"]:::blames
root --> later
me["Dropbox Sign (this incident)<br/>posted +1 h 4 min"]:::me
h4 --- 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
Dropbox Sign was impacted by AWS -EAST-1 outage, and some services may not have been working as expected from 00:25 to 00:53 UTC on May 8, 2026.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Dropbox Sign profileRecent Dropbox Sign incidentsMarkdownJSON