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:

• 
  Pato (@pvicens_) reported 2 minutes ago

  @ihtesham2005 syncthing is great until you realize you just became your own IT department. dropbox charges you money, selfhosting charges you time might be down to try it anyways :)

• 
  ZeroBANG (@Z3R0B4NG) reported 4 minutes ago

  @Pirat_Nation Does the EU also force Google/Samsung to keep the Android OS compatible for 10 years? 2013 Android 8 phone here, bit of OLED burn-in, battery still fine! Problem is Dropbox, or my Moms hearing aid config app are saying NOPE to the ancient Android 8 OS, forcing me to upgrade.

• 
  Dan Shipper 📧 (@danshipper) reported 6 minutes ago

  @drummatick dropbox is just an FTP server!

• 
  Jim Jensen (@jensenje) reported 7 minutes ago

  @WindowsCentral ZeroDrive has always been buggy! Even though I get 6TB included with my Microsoft 365 subscription, I still pay for a @Dropbox subscription to ensure 24x7 access to my files, error free!

• 
  Gabriel Amzallag (@gabrielamzallag) reported 8 minutes ago

  Notion’s homepage doesn’t start with features. It starts with chaos. A cartoon of people drowning in tools. Google Docs. Quip. Jira. Evernote. Trello. Confluence. Dropbox Paper. Eight logos piled on top of each other like a mess on your desk. Then one calm line: “With Notion, all your work is in one place.” No feature grid. No “powered by AI.” No “trusted by 10,000 teams.” Just: here’s your mess. We clean it up. They didn’t trash competitors. They named them. The pile IS the argument. Drift did this too. Called out forms as the “old way” right on their homepage. Basecamp painted projects spiraling into chaos. Churnbuster showed you every failed fix you already tried. Same playbook: diagnose before you prescribe. If your homepage jumps straight to features, you’re skipping the part where your visitor goes “that’s exactly my problem.” Most founders sell the destination. The best ones describe the traffic jam you’re stuck in right now. Day 45 — Problem-First Homepage Copy Follow for a new distribution strategy every day

• 
  Robert DC🛸🦾 (@RDecrypto) reported 9 minutes ago

  5/ Cursor turned down SpaceX's $60B offer. Now valued at $50B. 2 years ago: an open-source side project. Today: worth more than Dropbox + Slack + Pinterest combined. AI dev tools: biggest opportunity or biggest bubble in tech? What did I miss this week? 👇

• 
  Cryptosailor (@robertdavid010) reported 9 minutes ago

  @zmanian The issue was not focusing on the actual innovation being done in the Cosmos eco, & instead getting wrapped up in crypto casino degen hype. Eg. @Jackal_Protocol delivers on a decentralized 'Dropbox' @gitopiaDAO delivers on decentralized 'GitHub' (all Cosmos project should use)

• 
  Grok (@grok) reported 10 minutes ago

  @0x_levy @Morh_gan12 SaaS = Software as a Service. It's apps delivered over the internet on subscription, hosted by the provider—no install, no server management, auto-updates. Used for: email (Gmail), productivity (Google Workspace, Microsoft 365), CRM (Salesforce), storage (Dropbox), streaming (Netflix), collaboration (Slack, Zoom), etc. Basically, pay monthly and use it from any device.

• 
  Ravi Joseph (@rjkarmayogi) reported 11 minutes ago

  @signulll Google search - I LLM chat about general queries and usually only google for specific pages now Dropbox - eaten by iCloud and Google Drive Meetup - used to be good for local niche event discovery but that seems broken now

• 
  onehourman (@onehourlong) reported 14 minutes ago

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

• 
  Luan Teles ❁ (@LuanTeles) reported 20 minutes ago

  @uppastdark It looks like dropbox links are not working on the ps3 anymore.

• 
  Sarah 🎧🎛🎚 (@sarahb_paw) reported 25 minutes ago

  Look Dropbox, I know it's Friday afternoon but if you refuse to upload my files we both can't shut down for the weekend 😩

• 
  Shal (@mzshal) reported 29 minutes ago

  @bigcountrylax15 Ill have to remember my old dropbox password - it was on another email login that i dont use anymore so can't just click on forgot password 😭

• 
  Adel Bucetta (@adelbucetta) reported 34 minutes ago

  @heynavtoor most people just upload to google drive or dropbox, but nobody's talking about how terrible their video quality is afterwards

• 
  John Cartwright°͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌ 🐈 🐈 🐈 (@bejiitas_wrath) reported 34 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.