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:

• 
  BadUncle (@BadUncleX) reported 23 seconds ago

  @mitsuhiko Similarly, I still use the old version before 7. They try to force you to bind to their server-dependent version. I prefer to use dropbox to synchronize.

• 
  Abhishek Singh (@0xlelouch_) reported 31 seconds ago

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  Ashutosh Rana ⛓️ (@ashutoshrana_20) reported 3 minutes ago

  Most developers think Rust 🦀became popular because of ownership and borrowing. That's only half the story. Companies aren't adopting Rust because they enjoy fighting the borrow checker. They're adopting it because they're tired of C++-level performance coming with C++-level disasters. Look at where Rust is running today: • Linux kernel components • Windows security systems • Android services • Cloudflare edge infrastructure • AWS Firecracker microVMs • TiKV and Materialize • Discord and Dropbox backend systems • Solana and Polkadot Notice what these systems have in common. They're expensive to get wrong. A memory bug in a toy project is annoying. A memory bug in an operating system, cloud platform, database, or blockchain can cost millions of dollars, create security vulnerabilities, or bring down critical infrastructure. That's why Rust keeps showing up in the same places: • Systems software • Networking • Databases • Cloud infrastructure • Developer tools • Blockchains Not because it's trendy. Because the cost of unsafe software keeps rising. For years, engineers accepted the tradeoff: Performance → use C++ Safety → sacrifice performance Rust challenged that assumption. The result? A growing number of teams no longer see memory safety as a nice-to-have. They see it as a requirement. The ecosystem is still maturing. But Rust isn't fighting for relevance anymore. It's becoming one of the default choices for software where performance, reliability, and security are non-negotiable.

• 
  Hospital Hell (@HospitalHell) reported 6 minutes ago

  @SteveHiltonx The mostly mail-in/dropbox election system in California is painfully slow, but that doesn’t make it in any way fraudulent.

• 
  Kirby (@StewartKirbyTNP) reported 7 minutes ago

  @Syndicate You seriously need to get a NAS and and ftp server for the vlogs. It would make Orion or whoever has to edit that days life easier as websites like dropbox, drive ect crawl to a stop when it comes to large volumes of data. An FTP server goes WHEEEEEEEE

• 
  Polsia (@polsia) reported 9 minutes ago

  Files become clutter quietly. By the time you notice, you have months of stale files, duplicates, and forgotten shared links. ClearCloud monitors Google Drive, Dropbox, and Notion 24/7—surfacing issues before they compound. Weekly reports. You approve everything.

• 
  Simple American News 🗞️ (@TSimpleAmerican) reported 9 minutes ago

  Dropbox CEO Drew Houston is stepping down after 19 years, with chief product officer Ashraf Alkarmi being promoted, per CNBC

• 
  ScarcityMan (@ScarcityMan) reported 11 minutes ago

  @balkanhodl @hodlonaut Even worse than that. It's dropbox except every archival node runner is providing storage space for free, so like, dropbox where you host your data and pay for your own server...

• 
  Pelicart (@pelicartza) reported 16 minutes ago

  @lukey_stephens @_avdept real also - dropbox??? why would you pay $5 and not just set up an sftp server

• 
  Mohit Sindhwani (@onghu) reported 21 minutes ago

  @ocornut @RichardKogelnig Actually, some times the new menu is faster and the classic menu is much slower... but then sometimes, the new menu shows 3 entries called "Loading..." and that's terrible, too! I think one of my W11 PCs has almost instant context menu - the Dropbox notes were from that one.

• 
  Random Poser (@rndposer) reported 22 minutes ago

  @iHerbMiddleEast Problem with iHerb is your delivery service to consumers. They’re a challenge to work with. I wouldnprefer if there is option to get my deliveries directly in a dropbox somewhere near and not go thru the 3rd party delivery service.

• 
  Jeff Preshing (@preshing) reported 22 minutes ago

  What's the point of using smarter models if "smarter" means 10% better at finding obscure bugs and having a sassy attitude? Most of the true productivity gains that coding agents have to offer, which are finite, can be obtained using open-weight models for literally 1/100 of the price. The catch is that you actually need to understand the code you are working on. At the same time, I still think there's a viable business serving proprietary models. People are willing to pay for Dropbox even though FTP is free, and it's nice to throw a tough problem at a stronger model occasionally (if intellectual property limitations allow it). Plus, there's a whole frontier productizing this stuff. Unfortunately, Anthropic is currently in the business of spreading tall tales about future improvements, then shaking down enterprise customers. Most of it is based on 2010s LessWrong posts full of category errors, some of which I remember reading back in those days. And their recent hostility toward users in the name of safety is a result of the same ideological recklessness.

• 
  𝙳𝚛𝚊𝚌𝚞𝚕𝚊 𝙱𝚛𝚊𝚗𝚍 𝚃𝚊𝚖𝚙𝚘𝚗𝚜 𝙻𝙻𝙲. (@mynameisFACE) reported 27 minutes ago

  You ever login to your old Dropbox and see pics/vids you don’t even remember? Boyyyy, some mistakes were made 😩

• 
  Adam (@aclater) reported 27 minutes ago

  Hey @FedEx @fedexhelp - you've got the wrong address on a dropbox in alexandria, and I keep getting your angry customers and packages. Happy to work together to fix it? I can DM details.

• 
  CHRISTOPHER BLAZ✨ (@Blaz_Dao) reported 31 minutes ago

  Walrus 🦭 and Walrus Memory explained in a lay man's understanding. Let's dive in: 1. What is" Walrus🦭" ?? Firstly, I want you to think of Walrus as a gaint decentralised hard drive built on Sui protocol or ecosystem. Walrus is trying to become the decentralized version of cloud storage services like Google Drive, Dropbox, or Amazon S3, but built for Web3. In a simple analogy, think of it like this; Google Drive vs Walrus With Google Drive, your files are stored on Google's servers and Google controls the storage. If Google removes a file or service, you're dependent on them. But, With Walrus🦭 it's a different case as your files are split into many pieces. Those pieces are stored across many independent storage providers in a cheap manner as no single company controls all of your data. And the most fascinating thing is as long as enough storage providers remain online, your files can be recovered whenever you want. 2. What is "Walrus memory"?? In plain English, Walrus memory is simply the storage space used to keep data on the Walrus network. That data can be:Images, Videos, Documents, NFT media, AI datasets, Website files, Backups etc. Why does it matter? Imagine a viral meme image on Sui. Normally, the blockchain only stores a reference to the image because storing the image itself would be too expensive. Most blockchains are good at storing transactions but terrible at storing large files. @WalrusProtocol is designed to store large amounts of data cheaply while remaining decentralized. ~BlazCares