# Dropbox Sign: Dropbox Sign was not working as expected for some users.
- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-05-08 01:29 UTC · Resolved: 2026-05-08 00:30 UTC · Duration: -59 min
- Updates: 1
- [Vendor status page: https://stspg.io/k0mbnld4jszb](https://stspg.io/k0mbnld4jszb)
- [Company: Dropbox Sign](https://rewindex.com/company/dropbox-sign.md)
## Part of an outage event
- [AWS us-east-1 outage, May 8, 2026: 38 vendors, 43 incidents](https://rewindex.com/events/2026-05-08-aws-us-east-1)
- This incident blames AWS as the cause. (hop 1, posted +1 h 4 min vs AWS’s own post)
- Evidence: “…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…”
```mermaid
flowchart LR
root["AWS us-east-1
posted 00:25 UTC"]:::root
before["Posted before AWS did
3 vendors, 2 blamed AWS
Neon, Datadog, Convex"]:::blames
root --> before
h1["Within an hour
11 vendors, 11 blamed AWS
Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
root --> h1
h4["1 to 4 hours later
10 vendors, 9 blamed AWS
Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
root --> h4
later["Later
2 vendors, 2 blamed AWS
Wiz, SingleStore"]:::blames
root --> later
me["Dropbox Sign (this incident)
posted +1 h 4 min"]:::me
h4 --- me
```
_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._
## Timeline of updates
- **resolved** 2026-05-08 00:30 UTC: 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.
---
Canonical: https://rewindex.com/company/dropbox-sign/incidents/25b4c6qzznh7 · Markdown: https://rewindex.com/company/dropbox-sign/incidents/25b4c6qzznh7.md · JSON: https://rewindex.com/api/v1/companies/dropbox-sign/incidents/25b4c6qzznh7 · Generated 2026-10-19T23:17:00.876Z