The January 2014 outage: hours of downtime and a fake 'hack' claim
January 2014
On 10–11 January 2014 Dropbox went dark for roughly two hours after an internal maintenance error, while a group calling itself 1775 Sec falsely claimed to have breached it — a hoax that briefly stoked panic about user data.
What happened
On the evening of 10 January 2014 (around 6 p.m. PST) Dropbox suffered a service outage that left users unable to reach the website and sync for roughly two hours, with knock-on disruption continuing for some into the next day. Dropbox attributed the outage to an internal maintenance operation that went wrong: a routine process intended for one set of servers was applied to active production machines, taking the service down.
While the service was down, a group calling itself 1775 Sec announced on social media that it had 'compromised the Dropbox database,' posted purported user data, and framed the action as a tribute to internet activist Aaron Swartz on the anniversary of his death. The claim spread quickly before Dropbox refuted it. The company's engineering leadership stated plainly that users' files were always safe and that no hacking or DDoS attack was involved. The group itself subsequently admitted the breach claim was fabricated — a stunt partly designed to expose how readily the claim would be reported as fact.
Impact
The outage itself was a reliability failure caused by Dropbox's own maintenance process, underscoring how a single configuration mistake can take an entire cloud service offline for millions at once. The accompanying hoax added a second dimension of harm: even a fake breach claim can trigger real anxiety, password changes, and reputational damage for a custodian of private files — and it highlighted how thin the public's ability is to distinguish a genuine compromise from a fabricated one during a live outage.