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:

• 
  Bosn (@00bosn00) reported 2 minutes ago

  2026 and we’re out here building god-tier AI that can debate physics and write symphonies, but Grok still can’t watch a Dropbox, OneDrive, or Discord video link.“Sorry, I can’t watch videos from Dropbox, OneDrive, or most direct file links.”We’re doing all this magic with AI and the video player is stuck in 2015. Fix it, xAI.

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

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

• 
  Ashley Mathieu (@ashmath34) reported 8 minutes ago

  @DropboxSupport @Kuramichan7 having the same issue — can't create new folders, can't delete folders, can't rename folders, can't upload. incognito browser did not solve the issue, nor did restarting my computer

• 
  ᴾᵒᵗ ᵒᶠ ˢⁿᵉᵉᵈ (@P0tofSn33d) reported 13 minutes ago

  @Revolution61858 @Liliyalyv @2WBIA_Reformed ***** y dont u got yoself a dropbox or getchu a link tree wit all da links to download or some shieet so dat when dey take down 1 link u gots all sorts of avenues? Hustler Mindset *****.

• 
  Adrien Matray (@AdrienMatray) reported 13 minutes ago

  The fix is simple: do not use one generic code/ folder for all long-lived branches. Use separate Dropbox folders whose names encode the intended branch: code_main/ code_experimentation_main/ code_experimentation_main_name1Sandbox/ code_experimentation_main_name2Sandbox/

• 
  Lagoon Labs (@LagoonLabsMv) reported 16 minutes ago

  Dropbox is doubling down on virtual-first while everyone else pushes return to office - their people chief says hybrid is the worst of all worlds.

• 
  fercaton (@fercaton) reported 16 minutes ago

  Writing things down isn't weak—it's like training wheels for your ideas. Your brain's not built to be an infinite Dropbox; it's for connecting dots, not hoarding them.

• 
  YC Insights. (@Aiagent_s) reported 16 minutes ago

  March 23, 2018. Dropbox IPOs on NASDAQ. Surges 40%+ day one. Market cap: $12B First YC company ever to go public. Drew still owned 30%. The real lesson: both rejections were right. Both made the company better. Treat each rejection as a specific diagnosis. Then fix that specific thing.

• 
  Matt Devin (@MattDevin6) reported 18 minutes ago

  @joe4deadcat @Jackal_Protocol It is because these products have no interest. I use stuff like Dropbox, Microsoft Team etc. in my work. And I struggle hard to understand how I can fit these decentralized storage in my workflow. You can’t call it utility if it doesn’t solve a problem ppl have.

• 
  Adrien Matray (@AdrienMatray) reported 19 minutes ago

  The trap: when ~/.claude/ is in Dropbox, it often seems to work. No error message. Sometimes your preferences load, sometimes they do not. The symptom is silent quality drops you cannot trace. Not a visible failure. That is why people miss it.

• 
  No (@cameraplan7) reported 20 minutes ago

  @itskinkerbell drive. If people try to download a photo off of Dropbox in a browser/link, the quality actually goes down. I’ve tested on multiple photos and it doesn’t happen with drive

• 
  Awooingenjoyer (@AwooingEnjoyer) reported 20 minutes ago

  Nah, the dropbox is broken, go speak to Cathy.

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

• 
  Adeyinka Prime™ (@adefilaadeyinka) reported 26 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.

• 
  Chris_Mellor (@Chris_Mellor) reported 27 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.