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:

• 
  Luna (@_LunarLunaa) reported 5 minutes ago

  @ilovetmrmygffr did the dropbox link work? got taken down a bit ago

• 
  Grok (@grok) reported 7 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.

• 
  E.Matsumoto🔥🔥🔥 (@hotcoffee_cake) reported 7 minutes ago

  This happens to files sent after signing with Dropbox Sign. No issues occur when archiving directly in Dropbox.

• 
  John Cartwright°͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌ 🐈 🐈 🐈 (@bejiitas_wrath) reported 13 minutes ago

  Windows Defender, the built-in antivirus running on every Windows machine, has a working zero-day exploit with full source code sitting on GitHub. No patch, no CVE, and confirmed working on fully updated Windows 10 and 11. A researcher who says Microsoft went back on their word just handed every attacker paying attention a privilege escalation that takes any low-privileged account straight to NT AUTHORITY\SYSTEM. On Windows Server, the result is different but still serious: a standard user ends up with elevated administrator access. The vulnerability is called BlueHammer. On April 2nd, the researcher posted the public disclosure on a personal blog, and on April 3rd, the full exploit source code went live on GitHub. Both were published under the alias Chaotic Eclipse, also known as Nightmare Eclipse, with a message to Microsoft's Security Response Centre that comes down to: I told you this would happen. In late March, the same researcher opened a blog with a single post explaining that they never wanted to come back to public research. Someone had agreed with them and then broken it, knowing exactly what the consequences would be. The post says it left the researcher without a home or anything. A week later, BlueHammer went live on GitHub, with a message specifically thanking MSRC leadership for making it necessary. That is not someone annoyed with a slow review process. That is someone with nothing left to lose. BlueHammer is not a traditional bug, and it does not need shellcode, memory corruption, or a kernel exploit to work. What it does is chain five completely legitimate Windows components together in a sequence that produces something their designers never intended. Those five components are Windows Defender, Volume Shadow Copy Service, the Cloud Files API, opportunistic locks, and Defender's internal RPC interface. One practical limitation worth knowing: the exploit needs a pending Defender signature update to be available at the time of the attack. Without one in the queue, the chain does not trigger. That makes it less reliable than a push-button exploit, but it does not make it safe to ignore. When Defender runs an antivirus definition update, part of that process involves creating a temporary Volume Shadow Copy, which is the same snapshot mechanism Windows uses for backup and restore. That shadow copy contains files that are normally completely locked during regular operation, including the SAM database, which stores the password hashes for every local account on the machine. BlueHammer registers itself as a Cloud Files sync provider, the same kind of thing that OneDrive or Dropbox uses to sync files. When Defender touches a specific file inside that folder, the exploit gets a callback and immediately places an opportunistic lock on that file. Defender stalls, blocked, waiting for a response that is never coming. The shadow copy it just created is still mounted. The window is open. With Defender frozen in place, the exploit reads the SAM, SYSTEM, and SECURITY registry hives directly from the snapshot. It decrypts the stored NTLM password hashes using the boot key pulled from the SYSTEM hive, changes a local administrator account's password, logs in with that account, copies the administrator security token, pushes it to the SYSTEM level, creates a temporary Windows service, and spawns a command prompt running as NT AUTHORITY\SYSTEM. Then, to cover its tracks, it puts the original password hash back. The local account password looks completely unchanged. No crash, no alert, nothing. The Cloud Files provider name hardcoded in the exploit source code reads IHATEMICROSOFT. The administrator password used during the escalation is hardcoded as $PWNed666!!!WDFAIL. These are not bugs left by accident. They are messages, written directly into the code, and there is only one intended reader.

• 
  Raziel (@tryraziel) reported 13 minutes ago

  Drew Houston got rejected by every VC in Silicon Valley. His idea? "Another cloud storage company." The year was 2007. Dropbox was just a simple demo video of files syncing between computers. VCs said the market was too crowded — Microsoft, Google, and Apple all had cloud products. But Houston had spotted something others missed: people didn't want another cloud product. They wanted their files to just work. Here's what happened next: → Instead of pivoting, Houston doubled down on simplicity → He focused on seamless sync, not storage capacity → The demo video got 75,000 signups overnight → He used that traction to get into Y Combinator The breakthrough moment: Houston realized he wasn't selling storage. He was selling the elimination of emailing files to yourself. First investor meeting after YC: Sequoia wrote a $1.2M check. Same VCs who rejected him before suddenly wanted in. The product hadn't changed — the story had. Houston learned to position Dropbox as solving a universal pain point, not competing in cloud storage. Dropbox IPO'd at $10B in 2018. The lesson: Sometimes the market isn't wrong about your category. You just haven't found the right way to explain why you're different. What's the most rejections you've gotten on the same idea before finding the right investor?

• 
  busra ᢉ𐭩 (@sylustoy) reported 13 minutes ago

  @molaguya i never had such bugs but i have seen the scary ones 😭 idk how many ppl work for lads or devs but it sad how so much lacks and in case it shuts down i guess screenrecording is for better... do you save it in an app like dropbox or for usb stick?

• 
  The Bingus Man (@NotNordgaren) reported 14 minutes ago

  @Dropbox you guys wanna shut down the links I sent you that are hosting malware or are you gonna sit on it another week?

• 
  Dropbox Support (@DropboxSupport) reported 15 minutes ago

  @SergeiShiryayev Hi Sergei, thanks for writing in. Are you downloading the file immediately, after renaming it? There could be a slight delay in the server updating the file's index, so you'll need to refresh it first. For better accuracy, you can rename the files using the Dropbox app, instead.

• 
  Joe Devon (@joedevon) reported 16 minutes ago

  Yes, every time you pay that bill, let the anger be a prompt to install tailscale lol. That's what I do because I have wasted a small fortune on useless subs. Now I can login to all my private devices, vpn through my NAS. Who needs dropbox when your files are available everywhere? Time machine works from your hotel in another city. No blocking of API calls. All free.

• 
  Ezaz (@0xEzaz) reported 17 minutes ago

  “Delete Your Dropbox.” Sounds extreme until you realize how much of your life sits on someone else’s server, quietly monitored, limited, and one policy change away from disappearing. This isn’t just a challenge. It’s a wake-up call. The idea is simple: 24 hours. Move your files out of centralized storage and into the BitTorrent ecosystem. No gatekeepers. No single point of failure. Just your data, distributed across a network that doesn’t need permission to exist. We turn it into a movement. A live leaderboard tracking how much data people “liberate” from traditional cloud silos. A real-time counter ticking upward gigabytes, terabytes, petabytes each number representing users taking back control. Not just deleting accounts, but changing how they think about ownership. Because that’s what this is really about. Centralized platforms trade convenience for control. They decide uptime, access, even what’s allowed to exist. The BitTorrent ecosystem flips that model. Your files don’t sit in one place waiting to fail they live everywhere, secured by participation, not policy. So yeah, delete your Dropbox or don’t. But understand the difference. One system rents you space. The other gives you sovereignty. And once you see that, it’s hard to go back. @BitTorrent @justinsuntron #TRONEcoStar

• 
  njm ⚡️🏴󠁧󠁢󠁥󠁮󠁧󠁿🏴󠁧󠁢󠁳󠁣󠁴󠁿🏴󠁧󠁢󠁷󠁬󠁳󠁿⚡️ (@nathan_j_morton) reported 19 minutes ago

  i have housekeeping todo before i can tackle fun tech stuff like aws new s3 files (objects are temporarily mounted, as they are touched, into efs aka nfs on aws), the dropbox clone and dan just dropped an email about refashioning the internet with atproto. i need to finish this hazmat course and a few accounting tax intuit turbotax courses for my business. then i want to step through this oauth project on manning which references a book title, up and running with oauth 2 or something, and steps through building 1 auth server 2 api 3 spa. there are a bunch of good all-in-one services in this area i want to crib notes on too such as dexidp, stack-auth, curity, and w/e theo is cooking. he likes better-auth iirc.

• 
  Kirksville Attorney Patrick Nolan (@PatTalksLaw) reported 23 minutes ago

  @kirkjangel I agonized about that for a long time too. Here is where I came down: I have corporate or enterprise plans with OpenAI and Claude. That give the same privacy protections as mycase and dropbox. I used to keep them entirely separate and only use self-hosted llms for client data, then I realized that claude code had access to my entire network through a gap in my pc. So I modified my policy because my use case uses AI. However, that is not allowing AI to practice law for me, but rather accelerating data analysis, document assembly and a myriad of behind the scenes actions.

• 
  Grok (@grok) reported 25 minutes ago

  @GwcSpm I couldn't access the Dropbox link (got a 400 error). Web searches for the paper title show no mainstream physics sources supporting "proton memory" via RC mechanisms—it's likely speculative, not aligned with QCD. If you paste key sections, I'll review!

• 
  Gregor (@bygregorr) reported 30 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.

• 
  Grok (@grok) reported 31 minutes ago

  @imtiaznabi_ @abhijitwt Verified: All claims check out. AWS uses Rust for Nitro/Enclaves. Microsoft is migrating core Windows/Azure/C++ to it. Google cut Android memory vulns with Rust. Cloudflare rebuilt proxies in Rust. Discord switched perf services from Go. Dropbox rewrote backend/client parts. Figma uses it for multiplayer/server/canvas. Solana/Polkadot/NEAR/Aptos/Sui all center Rust for runtimes/programs/SDKs. The post's solid but overhypes "everyone's doing it" as if Rust fixes all. It excels for safety/performance-critical code—not your average CRUD app. Nothing's stopping you if it fits your stack; otherwise, no shame in skipping the borrow checker bootcamp.