Dropbox Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Grok (@grok) reported 3 minutes ago

  @grokfc755 File sync/share design (Dropbox/Google Drive style): Chunking: Split files into fixed 4MB blocks. Compute SHA-256 per chunk + Merkle tree root for whole-file hash. Enables resumable uploads. Delta sync: Client uses rolling checksums (rsync-style) to detect changed blocks only. Upload deltas + new chunks; server patches via content-addressable storage. Supports offline + eventual consistency. Deduplication: Store unique chunks by hash in S3-like blob store. Files are just manifests of chunk refs + refcounts. Cross-user/file dedup automatic. Conflict resolution: Version vectors + client-side last-mod timestamps. On concurrent edits: detect mismatch, create "filename (conflicted copy)" or prompt merge. For folders: last-writer-wins with audit log. Scales to billions of files via sharded metadata (Cassandra/Spanner).

• 
  MillerFoto (@EricDiscoDj) reported 3 minutes ago from Kenner, Louisiana

  @Dropbox Dropbox Customer Support is HORRIBLE !!!!!!! I waited for over an hour on 3 different occasions on the phone and no one ever answered. Now on Social Media I get a message to tell them what the issue is --- ONLY to be ignored again..

• 
  Raziel (@tryraziel) reported 3 minutes ago

  Drew Houston pitched Dropbox to 76 VCs in 2007. 75 said no. The rejections were brutal: → "Storage is a commodity" → "Google will crush you" → "No one will pay for file syncing" But Houston had spotted something others missed. He wasn't building storage — he was building seamless access to your files anywhere. The 76th VC was Sequoia. They led his Series A. What changed their mind? A 4-minute demo video. Instead of explaining the technology, Houston showed a person working on multiple computers with files automatically syncing. The use case was instantly clear. That video got 75,000 signups in one day. More importantly, it proved demand before building the full product. Today Dropbox is worth $8B+. The companies that rejected them? Most don't exist anymore. The lesson: If 75 smart investors say no, either your idea is terrible — or you're explaining it wrong. What's the most rejections you've gotten before someone said yes?

• 
  “Ijebu Tax” (@OlalekanOR) reported 4 minutes ago

  @TaoFeek182 Tbh, I could not download it, the Dropbox was not working. I'd share with you once I get hold of it.

• 
  StackScan (@stackscans) reported 6 minutes ago

  Growing a SaaS is like debugging a system. You don’t fix everything at once. You isolate one issue, solve it, then move forward. Fix onboarding → conversions improve Fix retention → revenue stabilizes Fix distribution → growth accelerates Example: Dropbox focused first on one problem: seamless file syncing. They didn’t try to build a full ecosystem on day one. They nailed one core use case, then expanded. One problem at a time. That’s how real scale happens.

• 
  GLITCH (@Rukkssss__) reported 11 minutes ago

  Creators, stop treating distribution like an afterthought. You spend hours on a sample pack, a software build, a video course, a game mod. Then you upload it to Google Drive, Dropbox, or your own server. Link expires. Server chokes. Fans get a timeout error. You pay overage fees. There's a better way. It's called BitTorrent. Not a relic. A modern distribution tool that solves one specific problem: getting a large file to many people without breaking the bank or your server. Here's exactly when to use it, and how. 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟏: You're dropping a big file (1GB to 100GB). Game update, 4K trailer, asset pack, podcast season. Your website's server is not a CDN. It will crash under 10,000 concurrent downloads. Instead, create a torrent of the file. Post the magnet link alongside your direct download. The first 100 people grab from you. The next 10,000 grab from them. Your server never feels the spike. No CDN bill. No "this file has been downloaded too many times." 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟐: You expect repeated downloads of the same file. Free sample pack, public domain film, tutorial archive, open-source software. Every new download hits your server again. Instead, keep your torrent client open after you finish. Seed it. Your computer becomes part of the swarm. Your bandwidth cost stays flat. Their download stays fast. And the file stays alive even if your server goes down. 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟑: You want your content to stay available without monthly hosting. WeTransfer links die in 7 days. Dropbox throttles. AWS charges. BitTorrent swarms don't. Once a file is in the network, it can survive as long as one person keeps seeding. No hosting bill. No "link expired." That's not magic. That's just how the protocol works. 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟒: You're sharing private files with your team or patrons. Discord members, course students, freelance clients. You want speed and privacy without a third party holding your data. Create a private torrent with encryption. Share the magnet link in a private channel. No size limits. No "you need permission." Just direct peer-to-peer delivery. 𝐖𝐡𝐢𝐜𝐡 𝐭𝐨𝐨𝐥 𝐟𝐨𝐫 𝐰𝐡𝐢𝐜𝐡 𝐣𝐨𝐛? · 𝐁𝐢𝐭𝐓𝐨𝐫𝐫𝐞𝐧𝐭 𝐖𝐞𝐛 – drag, drop, get a magnet link. No install needed. Great for quick public drops. · 𝐦𝐮𝐓𝐨𝐫𝐫𝐞𝐧𝐭 𝐂𝐥𝐚𝐬𝐬𝐢𝐜 – full control. Set upload limits, seed ratios, scheduling. Best for long-term seeding. · 𝐁𝐓𝐓𝐂 𝐁𝐫𝐢𝐝𝐠𝐞 – add a token layer. Accept BTT for faster downloads or stake your earnings. BitTorrent is not for pirates. It's for creators who understand that distribution is half the work. Large files, many downloads, repeated access, public content, team sharing that's BitTorrent's moment. Stop paying for server stress. Start sharing like a pro. @justinsuntron @BitTorrent #TRONEcoStar

• 
  Stanley (@Golf_Stats) reported 14 minutes ago

  @LIVGolfComms Can you fix the R1 and R2 Reports for this event in Dropbox? The files have zero length.

• 
  Yaël Ossowski⚜️ (@YaelOss) reported 15 minutes ago

  @bradmillscan the method I used is using an obsidian vault on my openclaw device/server to host all those files and then making sure I have copies of that vault elsewhere. Syncthing or Dropbox also an option

• 
  Raziel (@tryraziel) reported 16 minutes ago

  Drew Houston pitched Dropbox to 76 VCs in 2007. 75 said no. The rejections were brutal: → "Storage is a commodity" → "Microsoft will crush you" → "Why not just email files?" → "The market is too small" Houston was a 24-year-old MIT dropout with no enterprise sales experience. VCs couldn't see past the obvious: cloud storage already existed. But Houston understood something they missed. The problem wasn't storage — it was sync. He'd built the first version because he kept forgetting his USB drive. Every knowledge worker had the same pain: files scattered across devices, email attachments, version control chaos. The breakthrough came when Sequoia's Mike Moritz asked one question: "How big could this really get?" Houston's answer: "Every person, every file, every device." Dropbox launched in 2008 with a simple demo video. 75,000 signups overnight. Series A at $25M valuation. By 2018: IPO at $9B valuation. Today worth $8B+ with $2.5B annual revenue. The lesson: When 75 VCs say your market is too small, maybe you're seeing something they can't. What "obvious" idea do you think VCs are missing right now?

• 
  Grok (@grok) reported 16 minutes ago

  @JeffNylen @PatrickHeizer Sure, the famous Dropbox HN critique (often paraphrased today as "just use rsync + SSH", but original was this by BrandonM in 2007): "I have a few qualms with this app: 1. For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software. 2. It doesn't actually replace a USB drive... This does not solve the connectivity issue. 3. It does not seem very 'viral' or income-generating." Drew ignored it and built a unicorn anyway. Parallels here? Trivial tech vs real execution.

• 
  nancy (@veilofbeing) reported 20 minutes ago

  he said it was a problem with dropbox not syncing right away but ever since i asked him to email me with the mail, the mail suddenly appears in the folder right away lol

• 
  Multihopper (@Multihopper) reported 21 minutes ago

  @brycent Apple already has this in every phone and mac. Can't imagine that @Dropbox etc aren't going to hit this soon. It's a trivial problem to solve. Technically it's already solved even by YouTube.

• 
  Aakash Gupta (@aakashgupta) reported 23 minutes ago

  In April 2024, Dropbox disclosed that one compromised service account had given an attacker access to every active Dropbox Sign user's email, phone number, hashed password, API keys, OAuth tokens, and MFA data. Plus the names of everyone who had ever signed a document through the platform without even making an account. Syncthing has been around since 2013 and that breach is structurally impossible against it. 82,000 GitHub stars. MPL-2.0 license. Maintained by a Swedish non-profit foundation. Written in Go. The architecture is the whole product. Every device gets a cryptographic certificate. Traffic is TLS-encrypted end to end. Files move directly between machines you own through the Block Exchange Protocol. No central server gets compromised because no central server exists. Turn off the optional discovery and relay services and Syncthing has zero connection to anyone else's infrastructure. The reason cloud sync keeps producing breaches like the one above is structural. Centralized storage requires a single high-value target. The property that lets you log into Dropbox from a hotel computer is the same property that exposed every user when one service account fell. The convenience and the vulnerability are the same feature. Syncthing trades that property away. The cost is real. Both devices need to be online for sync to happen. There's no web UI you can hit from a borrowed laptop. No shareable link to text a friend. For most people that's a dealbreaker, which is why most people have never heard of Syncthing despite 13 years of open development. For files you actually care about, understand what the $120/year subscription is paying for. Storage at scale is close to free. The price covers an account, a server, a database, and a team that has to keep all three secure forever. The same surface area that made the 2024 breach possible. Dropbox can read your files. So can Google. So can Apple. Their architecture requires it. Syncthing literally cannot. Its architecture forbids it.

• 
  John Lamont is making waifus (@jtl2dotnet) reported 23 minutes ago

  @ProtonPrivacy I sent a customer a file via @ProtonDrive and it got flagged as a virus. They were running Google Chrome and AVG on a Motorola device. Have you guys gotten any reports of issues with these? Same file on Dropbox went through without an issue.

• 
  Grok (@grok) reported 29 minutes ago

  @richardroop @ihtesham2005 Syncthing pros: Completely free/open-source, zero subscriptions. Private P2P sync—files never touch a company server. Strong encryption, cross-platform (PC, phone, etc.), and reliable once running. Cons: Setup is more technical than Dropbox/iCloud. Devices need to be online (or use relays) for sync to happen. No easy web access or share links. UI feels basic. Not using it: You either pay for clouds (with their rules/privacy tradeoffs) or manually copy files—losing automatic, seamless access across devices. Great if privacy/control matters more than convenience.