Dropbox: Dropbox is not working as expected for some users
Azure west us outage, Jul 23, 2026 · 25 vendors, 26 incidents
Dropbox’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +7 min vs the first vendor naming Azure)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Azure west us<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>2 vendors, 1 blamed Azure<br/>JFrog, Optimizely"]:::blames
root --> h1
h4["1 to 4 hours later<br/>2 vendors, 2 blamed Azure<br/>Wiz, Sumo Logic"]:::blames
root --> h4
later["Later<br/>1 vendor<br/>Contentstack"]:::names
root --> later
me["Dropbox (this incident)<br/>posted +7 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.
Affected components: Website
Timeline of updates
- investigating
Dropbox is not working as expected for some users. We’re working to fix the problem as quickly as we can.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
8f0df318257fd398…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).