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:

• 
  Lazaro M. (@Lzmrtn66) reported 4 minutes ago

  @Dropbox I'm having trouble regaining access to my Dropbox account. I have access to the registered email. I request a password change, you send the password, I log in with the password, then you say you'll send an SMS to my cell phone, but that SMS never arrives.

• 
  ✨️Ascendant (@ascendant32) reported 5 minutes ago

  yo laptop people, is 2tb of ssd necessary on a laptop these days or is 1tb enough? assuming 32gb ram i work w huge datasets sometimes as for storage needs i use dropbox so it's never been an issue but sometimes loading datasets can be an issue bc not enough ram lol

• 
  onehourman (@onehourlong) reported 6 minutes ago

  @w0nt_cry I agree with Slow. There’s also dropbox

• 
  Anuroop Kumar (@anuroopk4u) reported 14 minutes ago

  @jasonlk I remember as a teen, Dropbox set the standard. It was Dropbox, AirBnB, and Uber - as these “new economy” startups that were changing the world. Frankly speaking, Google Drive just started to do more for me and integrated easier sharing down the road. There was no value add I was getting from Dropbox once storage got commoditized.

• 
  Hany (@kmhaneem) reported 17 minutes ago

  Dropbox launched in 2008 with a simple promise. Put your files in this folder and we will sync them everywhere. Every sync goes through their servers first. Their infrastructure. Their terms. Your files sit on their machines until you need them back. A developer named Jakob Borg decided that was the wrong architecture. Not inconvenient. Wrong, at the level of who owns what. In December 2013 he shipped the first public release of Syncthing. Peer-to-peer file sync. Your devices talk directly to each other. No company in the middle. No server reading the transfer. Syncthing is free, open-source, and has 67,000+ GitHub stars. The project's own stated mission: your data is your data alone, and you deserve to choose where it is stored. Most sync tools list speed and storage first. Syncthing's README lists data protection as priority 1 and priority 2. Speed does not even make the list. That tells you exactly what this project is. -> Your files go from your laptop to your phone. Nowhere else. -> Works on Windows, Mac, Linux, Android, and more. -> No storage cap. Your limit is your own hardware. -> Peer-to-peer sync. Direct device to device, encrypted in transit. -> Runs silently in the background. Zero clicks after setup. -> Web UI included. No command line required to use it daily. -> Open protocol means no vendor can quietly change the rules on you. -> GPG-signed releases. You can verify every binary before running it. -> Versioning built in. Deleted something? You can get it back. -> Self-hostable discovery servers if you want to go fully off-grid. By 2019, Syncthing was getting roughly a million downloads per stable release and syncing hundreds of terabytes of data every day. It is now backed by the Syncthing Foundation, a Swedish non-profit, so no company can buy it, pivot it, or shut it down. Last commit: this week. Shipping continuously since 2013. 300+ contributors. Still pushing updates in 2026. Dropbox: $9.99/month. Google Drive: $9.99/month. Syncthing: $0. Forever. No account to create. No server holding your files hostage. No price hike email arriving on a Tuesday morning. No terms-of-service update quietly granting them new rights to your content. Cancel Dropbox and your access dies with it. Run Syncthing and nothing changes. Your files are on your machines. They stay there whether you open GitHub tomorrow or never again. That is not a feature. That is a different relationship with your own data. 67,000+ stars. MPLv2 license, which means no corporation can quietly close it down. 300+ contributors across a decade. Updated this week. The people who switch to Syncthing are not always the most technical. They are the ones who read the terms of service once and could not unsee them. If that sounds like you, the link is worth a look. (Link in the comments)

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

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

• 
  Adeyinka Prime™ (@adefilaadeyinka) reported 18 minutes ago

  @aarondfrancis @Shpigford Exactly - when sharing solves a problem for the person sharing, it doesn't feel like marketing. Dropbox nailed this because storing files alone was less useful than storing them with others. The product itself created the reason to invite.

• 
  Abhishek Singh (@0xlelouch_) reported 18 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.

• 
  Isha (@VISportsTalk) reported 23 minutes ago

  @DropboxSupport Still not working

• 
  VestaCreds (@vestacreds) reported 26 minutes ago

  Pilot finding I didn't expect: Credentialing isn't a technology problem first. It's a paper problem. Every clinician we've onboarded shows up with the same chaotic Dropbox folder of PDFs nobody has ever sat down and organized. Fix the paper. Then the workflow gets easy.

• 
  divyansh tiwari (@DivyanshT91162) reported 28 minutes ago

  The craziest part? Google and Dropbox built billion-dollar businesses… around a problem open source already solved for free years ago.

• 
  Michael Hartl (@mhartl) reported 34 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?

• 
  Surya Moorthy (@suryabuilds) reported 35 minutes ago

  🧵Thread... Dropbox in 2012 introduced 2FA due to some security issues in those days and following 6 months before they introduced 2FA. 👇👇

• 
  Blackbox RMS (@blackboxrms) reported 36 minutes ago

  Running a record label in 2026 is pure chaos: spreadsheets, Dropbox, endless emails. We built Blackbox RMS to fix it. One desktop app for releases, artists, contracts, promo & royalties. Built by a label, for labels. Link in bio. What's your biggest headache? 👇

• 
  0xMarioNawfal (@RoundtableSpace) reported 38 minutes ago

  You pay Google $10/month to store your files on Google's servers where Google can read them. Dropbox was breached in 2024. Emails, passwords, API keys all exposed. There's a tool that syncs files directly between your devices. No cloud. No server. No middleman. It's called Syncthing. 81,900 stars on GitHub. - Peer-to-peer, files never touch a third-party server - TLS encryption with perfect forward secrecy - No account, no sign-up, install it, share a device ID, done - File versioning, selective folder sharing, works over LAN and internet - Runs on Windows, Mac, Linux, Android, and more Dropbox: $144/year. Google One: $120/year. Syncthing: $0. Unlimited devices. Unlimited storage. Forever. There is no Syncthing server. Nothing between your devices except an encrypted tunnel.