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:

• 
  Isha (@VISportsTalk) reported 5 minutes ago

  @DropboxSupport @DropboxSupport Now I cannot even remove editors to folders. The Whole system is down

• 
  RealHD (@Purified_HD) reported 5 minutes ago

  Update: I was able to get the download link the mod was using to pull the .exe on launch taken down through Dropbox. It won't stay down for long, but it throws a wrench in their operation for now.

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

  Super chad legendary interviwer at dropbox: You need to store 10 billion small files (1-10KB each). Block storage costs are $100K/month. How will you reduce storage costs? [Real problem at Dropbox]

• 
  Grok (@grok) reported 7 minutes ago

  @richardroop @ihtesham2005 Syncthing pros: Completely free/open-source, zero subscriptions. Private P2P sync—files never touch a company server. Strong encryption, cross-platform (PC, phone, etc.), and reliable once running. Cons: Setup is more technical than Dropbox/iCloud. Devices need to be online (or use relays) for sync to happen. No easy web access or share links. UI feels basic. Not using it: You either pay for clouds (with their rules/privacy tradeoffs) or manually copy files—losing automatic, seamless access across devices. Great if privacy/control matters more than convenience.

• 
  Ravi Joseph (@rjkarmayogi) reported 10 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

• 
  Sara (@monamouroui) reported 10 minutes ago

  Why did Microsoft OneDrive just delete all of my Dropbox files? What a fracking PITA. You just created a huge problem for me. This might make me jump to a Mac. I am so disgusted and frustrated by what Microsoft running Windows 11 just did to my computer. Dozens of years of documents....whoosh. @Microsoft

• 
  Naughty kayla🤤💦 (@Naughtykayla127) reported 11 minutes ago

  Bored and horny 🥺 who is down for my Dropbox and ft Discount price 🤭#jacksonvillemeets #904freaks #jaxfreaks

• 
  Invest Lens (@AIadventure3) reported 11 minutes ago

  @gabrielchua On the outlook email plugin, when you draft replies the formatting is very bad. Is there a fix coming for this? Also, please add Dropbox and Asana plugins.

• 
  Anirudh Sharma (@anirudhology) reported 14 minutes ago

  @0xlelouch_ This is a classic small-file storage problem and Dropbox actually solved it by building "Magic Pocket": an in-house object store. The issue with block storage is that it wastes massive space on per-file metadata and partial-block fills. For 10B files, this overhead can cost up to $ 90K/month. Pragmatically, we can pack small files into large (~4MB) immutable blobs which are called "extents" or "superblobs". We write them sequentially, index with a content-hash to blob-offset mapping stored separately. This removes per-file filesystem overhead, reduces metadata pressure, and allows efficient erasure coding across whole blobs. We should also have a tiering policy where we compress blobs and move cold data to low-cost deep archive. Dedup at file level can also be incorporated. This combination can cut costs by 70-90% while keeping latency bounded by the index lookup.

• 
  Pradeep Kumar Xplorer (@ThaiKumar) reported 15 minutes ago

  Someone is regulating my upload to Dropbox 33 mb file suddenly the network is slow

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

• 
  The Insight Brief (@SimpleTech247) reported 20 minutes ago

  You pay Google $10/month to store your files. On Google's servers. Where Google can read them. You pay Dropbox $12/month. On Dropbox's servers. Where Dropbox can read them. You pay Apple $10/month. On Apple's servers. Where Apple can read them. Dropbox was breached in 2024. User emails, hashed passwords, API keys, and OAuth tokens were exposed. There is a tool that syncs your files directly between your own devices. No cloud. No server. No middleman. Ever. It's called Syncthing. 81,900+ stars on GitHub. Your files go directly from one device to another. Peer-to-peer. They never touch a third-party server. Not even Syncthing's. Here's what it does: → Syncs files between any number of devices in real-time. → Peer-to-peer. No central server. Your files go directly between YOUR devices. → TLS encryption with perfect forward secrecy on every connection. → Every device authenticated with a strong cryptographic certificate. → Works over LAN and internet. No port forwarding needed. → Selective folder sharing. Sync different folders with different people. → File versioning. Deleted or changed something? Roll it back. → Runs on Windows, Mac, Linux, Android, FreeBSD, Solaris, and more. → Web dashboard to monitor everything from your browser. → No account. No sign-up. Install it. Share a device ID. Done. Here's the wildest part: There is no Syncthing server. There is no Syncthing cloud. There is no company storing your data. The protocol is open and documented. There is nothing between your devices except an encrypted tunnel. Google has shut down 293 products. Dropbox has been breached. iCloud photos have leaked. Every cloud service is one policy change away from scanning everything you store. Syncthing can never shut down your files. Because your files were never on their servers. Dropbox Plus: $12/month. $144/year. Google One 2TB: $10/month. $120/year. iCloud+ 2TB: $10/month. $120/year. Syncthing: $0. Unlimited devices. Unlimited storage. Your hardware. Your files. Forever. 349 contributors. 464 releases. 5,000+ forks. Battle-tested since 2013. Run by the Syncthing Foundation. A Swedish non-profit. MPL-2.0 licensed. Open protocol. Peer-to-peer. Free forever. 100% Open Source.

• 
  Stone Kidman Writes (@StoneKidman) reported 22 minutes ago

  @AyakaMods I had this problem that's why I use Dropbox

• 
  GLITCH (@Rukkssss__) reported 23 minutes ago

  𝗕𝗧𝗙𝗦 is BitTorrent's decentralized file storage system, and it fundamentally changes how you store and share data. Think about traditional cloud storage: Google Drive, Dropbox, iCloud. Your files live on servers owned by a single company. That company controls access, sets prices, and can delete your data at any time. Your files are only as safe as that one company's security. And if their server goes down? You lose access. 𝗕𝗧𝗙𝗦 works completely differently. Instead of relying on a single server, your files are split into tiny encrypted pieces and stored across thousands of independent nodes worldwide. No single point of failure. No single company holding your data hostage. This architecture delivers 𝗙𝗼𝘂𝗿 𝗠𝗮𝗷𝗼𝗿 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀. First, security. Because files are fragmented and distributed, an attacker would need to compromise thousands of nodes to reassemble your data practically impossible. Second, censorship-resistance. No government or corporation can shut down BTFS because there's no central target to attack. Third, fault-tolerance. If some nodes go offline, thousands of others still serve your files. Fourth, speed. Peer-to-peer retrieval means you often download from the closest node, not a distant data center. So how does it work for actual users? You upload a file. 𝗕𝗧𝗙𝗦 splits it, encrypts each piece, and distributes those pieces to storage providers around the world users who have volunteered their spare hard drive space. When you need the file back, BTFS locates all the pieces from the fastest available nodes and reassembles them. But here's what makes BTFS sustainable: 𝗥𝗲𝘄𝗮𝗿𝗱𝘀. If you have unused storage space on your computer say, 100 GB sitting empty you can lease that space to the BTFS network. You earn 𝗕𝗧𝗙𝗦 𝗧𝗼𝗸𝗲𝗻𝘀 for every byte you store and serve. Your idle hard drive becomes an income stream. For everyday users, this means cheaper cloud storage. Without a centralized company setting monopolistic prices, storage costs drop to market rates determined by supply and demand. It means safer backups. Your encrypted, fragmented files survive disk failures, server outages, and even natural disasters. It means faster file sharing. The more popular a file is, the more nodes store it, and the faster everyone downloads it the opposite of centralized servers that slow down under load. All of this runs on 𝗕𝗹𝗼𝗰𝗸𝗰𝗵𝗮𝗶𝗻 𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 combined with BitTorrent's massive existing network. BitTorrent already has hundreds of millions of users worldwide. BTFS taps into that peer-to-peer infrastructure, adding incentives and persistence to what was once just a sharing protocol. Upload, store, retrieve. Or share your spare space and earn. No corporate servers. No hidden fees. No single point of failure. That's 𝗕𝗧𝗙𝗦 decentralized storage built for the real world. @justinsuntron @BitTorrent #TRONEcoStar

• 
  Gavin (Owner 67 Designs) (@67Designs) reported 23 minutes ago

  @DumbMoneyCapitl That could be argued, sure. But it misses the bigger picture. The real issue isn’t whether Jim and SCS have a working Dropbox—they clearly do. The problem is that VC funds are desperately hunting for places to deploy all their capital, and businesses like this simply can’t deliver the returns those funds require because of their heavy capex profile. It’s a classic square peg in a round hole from a funding and returns standpoint.