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:

• 
  Atish (@AtishhAmte) reported 8 minutes ago

  @balyberdin_dev I was facing an issue with my clients with file chaos Tried everything from drive to dropbox, WhatsApp, email but nothing helped there So I listed my problem and derived solution around it

• 
  frank goertzen (@frankgoertzen) reported 8 minutes ago

  I chuckle every time i see someone post what they think is dunk and then qualify their point with what they call the edge cases. Dropbox is just ftp with a few edge cases. LLMs are just autocorrect with a few edge cases. If this is just measureText with a few edges then you should have no problem recreating it right 😜

• 
  Square Circle 556 (@ragtop25) reported 12 minutes ago

  @mistressdivy I hate OneDrive but I have to use it. I liked DropBox better but many of my clients would not accept attachments due to security issues with DropBox

• 
  avrl ☘ (@avrldotdev) reported 14 minutes ago

  Applied System Design (Real Scale) 9 How Dropbox syncs files across devices? Problem You & a colleague are offline. You both move 10,000 files into different subfolders. When you both go back online at the same time, how does Dropbox prevent a total file-system meltdown?

• 
  Sea (@norfaerie) reported 19 minutes ago

  I just gave myself a five hour anxiety attack by trying to move all of my backups of pictures from Google to Dropbox and then running out of space on Dropbox and not being able to increase my storage because Google Play is broken on my laptop 🫠

• 
  Shirochenko Dmitriy (@dmshirochenko) reported 20 minutes ago

  Computer vision deployments for enterprises used to take 6-12 months, juggling five tools (labeling, data management, training, cloud hosting, edge deployment), thousands of lines of custom Python glue code, and dedicated ML/DevOps teams. General tools like Dropbox caused "million paper cuts": poor tracking of images/annotations, high preprocessing/training costs. CV stayed trapped in research labs, out of reach for small teams. Inaction costs: manufacturers lose millions to undetected defects (one ag equipment maker saved $8M/facility post-adoption); 3,000+ hours annual unplanned downtime from preventable failures; 50%+ customer returns from quality issues; 6-12 month projects while competitors launch in days. Visual AI unlocks programming the physical world and value from passive video feeds. #AI

• 
  Nil (@Nil053) reported 21 minutes ago

  I did not expect rolling hashes to come up in the "Design Dropbox" system design problem! When designing Dropbox, it is important to discuss chunking for large files: To upload 50GB file, we split it into smaller chunks (say, 4MB each) and upload them individually. This makes uploads fault-tolerant: a network disconnect doesn't ruin the entire upload; we just resume the remaining chunks. But what if the file changes locally? Do we reupload the whole thing? The next idea is to store the hash of each chunk as metadata, locally and remotely. Then, we only reupload chunks whose hash has changed. But that's just normal hashing; we haven't got to the rolling hash part yet... Consider the worst case: append one byte at the *start* of the file. Every chunk boundary shifts by one byte, every chunk hash changes, and we reupload everything. The chunks we previously uploaded are still physically present in the local file, just not aligned to 4MB offsets. That's where the rolling hash comes in: we use it to compute, in linear time, the hash of every 4MB window in the local file - not just those aligned to offsets that are multiples of 4MB. This way, if a chunk we previously uploaded is still intact *anywhere* in the local file, even if it moved around, we will detect it, and we can skip uploading it. We only need to upload the bits between those chunks (and accept that our chunks will not always be exactly 100MB).

• 
  Gregor (@bygregorr) reported 23 minutes ago

  @rseroter @Dropbox Dropbox still at 87GB before the fix is wild. Mono repo size creep is silent until someone's waiting an hour to clone on day one.

• 
  れいもんReymon💅✨vivid (@ShaddollReymon) reported 25 minutes ago

  @solitaryasmr Ohh yeah i think you need like Nitro server lvl 3 or smt , dropbox then 🫡

• 
  BlackhillsEd (@blackhillsed) reported 26 minutes ago

  @SgtJulier1776 @CoffeeBlackMD I would suggest @HunterEsoteric Go to his website, sign up for the emails and look at his resources. He is on YT (Taken down before) and Spotify. Once you get the 1st email go to the bottom of the page and get the complete Dropbox vids. Get his cheatsheet as well!

• 
  Chris_Mellor (@Chris_Mellor) reported 33 minutes ago

  All of a sudden, when trying to upload Voice Record 7 audio recording files from my iPhone to Dropbox I now have to login to Dropbox and get an emailed verification code .... WHY??? All the convenience has gone. It's enshittification.

• 
  Damien White (@Visoft) reported 35 minutes ago

  User-centric design isn't optional anymore. Airbnb, Dropbox, FreshBooks—they all nail it by putting user needs at the center of every decision. Your homepage should solve problems, not create them. What's your biggest design friction point right now? 🎯

• 
  Aakash Gupta (@aakashgupta) reported 35 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.

• 
  Josh Peterson (@jdpeterson) reported 37 minutes ago

  The connectors are trash. Tried them yesterday. First off, there's no Dropbox connector, so had to install the Dropbox MCP. It forgets Dropbox is installed. And then tried installing a Slack MCP, but it kept saying it wasn't recognized. And then finally, I tried having it use connectors in a Grok Task, creatinga markdown report in Google Drive, update a CRM in Sheets, and create an accompanying issue in Linear. Grok lied multiple times saying it completed the tasks when it didn't touch the CRM, it created half baked headings for the report, and the Linear issue was a bare skeleton, all tasks ChatGPT and Codex can do with ease. The connectors are not ready for prime time

• 
  Raziel (@tryraziel) reported 39 minutes ago

  Drew Houston was a college kid who kept forgetting his USB drive. Today Dropbox is worth $8B. Here's the brilliant strategy behind one of the most successful pivots in startup history. In 2007, Houston built a personal tool to sync files between computers. Simple problem, simple solution. But investors weren't buying it. Every VC said the same thing: "There are already 20 file storage companies. What makes you different?" Houston's breakthrough wasn't technical — it was psychological. Instead of building better storage, he realized people didn't want to think about storage at all. The magic wasn't in the cloud. It was in making the cloud invisible. The pivot: → Original idea: Online backup service (like everyone else) → New idea: Your files, everywhere, automatically → Key insight: Sync, don't store Houston spent months perfecting the demo video. No fancy features. Just a file appearing on multiple computers simultaneously. It looked like magic because it solved the real problem: friction. That video got 75,000 signups overnight. The lesson: Sometimes the billion-dollar idea isn't what you build — it's how you frame what already exists. Houston didn't invent cloud storage. He invented the feeling that your files just worked everywhere. What "obvious" problem in your daily life could be the next Dropbox?