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:

• 
  The New Release Guy (@moviesplusgames) reported 6 minutes ago

  @Dropbox Maybe it is a skill issue, like ppl keep saying....bc they're WAY behind a company like X.

• 
  Neural Insights (@neural_insights) reported 12 minutes ago

  Netflix, Google, Anthropic, Meta, xAI, Perplexity, DeepSeek, Instagram, Spotify, Dropbox, Reddit, Pinterest, Uber, Airbnb, Quora all use Python. But sure—Python is “too slow” for your project.

• 
  Rashford Eyo of Jeje Group (@rashfordeyo) reported 14 minutes ago

  2. Solve a problem that hurts. Dropbox got its first 5,000 users from a simple demo video. They didn’t have a following, just a pain point worth talking about.

• 
  Abhishek Singh (@0xlelouch_) reported 14 minutes ago

  A good system design interview question for a Senior/Staff Backend Engineer is: Design Dropbox. At first, Dropbox looks like a simple file upload and download system. User uploads a file, we store it, and later they can access it from another device. But the real complexity is not uploading one file. The real complexity is sync, conflict resolution, versioning, permissions, large file handling, offline changes, metadata consistency, deduplication, and making the system feel instant across laptops, phones, and web. I would start by breaking the system into two major parts: file content and file metadata. File content means the actual bytes of the file. Metadata means file name, folder path, owner, size, checksum, version, permissions, timestamps, and deleted/restored state. These two should not be stored together. File bytes should go to blob/object storage, while metadata should go to a database that supports fast lookups and strong correctness. For upload, the client should not send a large file as one big request. A 2GB video should not restart from zero because the Wi-Fi dropped at 95%. So we should split files into chunks, calculate checksum for each chunk, and upload chunks independently. Once all chunks are uploaded, the server creates a file version that points to those chunks. This gives us resumable uploads, retry safety, and better network usage. A very important optimization is deduplication. If 10,000 users upload the same popular PDF, we do not want to store 10,000 copies of the same bytes. We can hash file chunks and store only unique chunks. Metadata will point to the chunk list. This saves huge storage cost, but we must be careful with privacy and security. Dedup should happen in a controlled way, not leak whether another user already has a specific file. The metadata service becomes the source of truth. Every change like upload, rename, move, delete, restore, or share should create a new metadata version. This is important because Dropbox is not just storage, it is a timeline of changes. If the user deletes a file by mistake, we should be able to restore it. If two devices make changes offline, we should know exactly what changed and when. Sync is the heart of the system. Each client should maintain a local sync token. Whenever something changes, the server writes it into a change log. The client can ask, “give me all changes after token X.” This is much better than scanning every folder again and again. For near real-time sync, clients can use long polling, WebSockets, or push notifications to know when new changes are available. Conflict handling is where naive systems fail. Imagine a user edits the same file on laptop while offline, and also edits it from mobile. When both devices come online, which version wins? For normal files, the safest approach is to keep both versions and create a conflict copy. For collaborative documents, we need deeper merging logic, but for a Dropbox-like file system, versioning plus conflict copies is usually good enough. Permissions should be checked before every sensitive operation. Sharing a folder is not just adding one row in a table. If a folder has thousands of files, permission inheritance becomes tricky. We should model ownership, viewer/editor access, shared links, link expiry, team policies, and audit logs. Permission changes should be strongly consistent because users must trust that removing access actually removes access. Downloads should first go through metadata and permission checks. After that, the system can return a short-lived signed URL from blob storage or CDN. Public/shared files can be cached more aggressively. Private files need careful access control. Performance is important, but leaking private files for speed is not acceptable.

• 
  𝖆𝖍𝖒𝖎𝖗 (@calhalt98) reported 15 minutes ago

  @liabynight Lmk if you ever make a Dropbox, I’d be down to get it

• 
  boogie (@w4nchwarrior) reported 16 minutes ago

  @Chishichusha @Lazei3 Welcome back! Can u fix the dropbox with all yr content?

• 
  That Startup (@ThatStartup_) reported 19 minutes ago

  In 2009, Dropbox had a serious problem. They were charging $99/year and growth had flatlined. Drew Houston made one change to pricing. Revenue grew 3,900% in the next 24 months.

• 
  Isha (@VISportsTalk) reported 19 minutes ago

  @DropboxSupport Still not working

• 
  Damien White (@Visoft) reported 22 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? 🎯

• 
  The Reverend KFidds (@KFidds) reported 25 minutes ago

  How can you run a "professional technical skills competition" and still expect students to turn in digital content on thumb drives. What is this, 2011? Computers don't even have thumb ports. Google Drive and DropBox is industry standard. So small time and outdated. Terrible.

• 
  timbidefi (@timbidefi) reported 25 minutes ago

  You are being watched right now and you're paying for it, privacy isn't a feature, it's a decision you make. Google stores your emails, Apple logs your location, Dropbox reads your files. Every cloud service you pay for is a deal you didn't fully read, with a company whose interests are not yours. He read it, built this instead: Custom rack server in his home, fully self-hosted, zero third party access, every byte of data sitting on hardware he physically owns. Email, storage, VPN, everything, running on his infrastructure, under his rules. Nobody can sell it, subpoena it, or lose it in a breach he had no control over. It cost him a weekend to build and less than $300 to run per year. Your data is somewhere right now, the only question is whose terms it's living under.

• 
  🎀MONA MANIC🧸 (@mona_maniccc) reported 28 minutes ago

  My new Dropbox link is out 1 terabyte dm if you are down 💞

• 
  Raziel (@tryraziel) reported 32 minutes ago

  Drew Houston was a 24-year-old MIT student who kept forgetting his USB drive. His solution? A file-syncing service called Dropbox. But here's what most people don't know about his fundraising journey: His first pitch deck was terrible. 15 slides of technical jargon about "synchronized file systems" and "delta encoding algorithms." VCs glazed over. The breakthrough came when he made a 3-minute demo video instead. No technical explanations. Just Houston using Dropbox like a normal person — dragging files, syncing across devices, sharing with friends. That video got him into Y Combinator in 2007. → Seed round: $1.2M led by Sequoia (2007) → Series A: $7.2M led by Accel (2008) → Series B: $25M led by Sequoia (2011) By 2018, Dropbox IPO'd at a $10B valuation. The lesson: Houston didn't pivot his product — he pivoted his pitch. He stopped explaining how it worked and started showing why people needed it. Sometimes the problem isn't your idea. It's how you're selling it. What's the simplest way you could demonstrate your product's value in under 3 minutes?

• 
  Michael Hartl (@mhartl) reported 36 minutes ago

  For the billionth time @Apple is failing to properly sync my files across devices. It’s hard to believe iCloud is still so incompetent after so many years. I’m sure it’s not a trivial problem, but @Dropbox gets it right every single time. Surely isn’t too hard for Apple?

• 
  Liam McKnight (@liam_mcknight) reported 36 minutes ago

  @MaxNordau I’m getting false positives for phishing on Dropbox so they are being hypersensitive rn. Literally do not share links to the open internet and the number of clicks is probably near zero. Didn’t even get an email telling me about the problem. Then there was a malware false positive today that was quickly resolved within 18 hours >check these digits bro he shares his digits lolol