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:

• 
  Kathleen Marie (@lifesavoring) reported 55 seconds ago

  @DropboxSupport I have the same problem as Detroit Media Magazine described below - my Dropbox became unavailable until the latest update. I tried to upgrade my account, but was registered instead for a free trial - ? I have to update my email to get it authenticated - PLEASE RESPOND, thanks.

• 
  Jeff Preshing (@preshing) reported 3 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.

• 
  Kalshi Finance (@Kalshi_Finance) reported 7 minutes ago

  JUST IN: Dropbox CEO Drew Houston to step down

• 
  Jean-Baptiste Emanuel Zorg (@calibrated_lies) reported 8 minutes ago

  3. Incentivizes Centralizing BlockSpace Market Ahhh the crux of the problem "... high-volume data ...". Bitcoin is a monetary protocol used for monetary txs any other use make Bitcoin useless. Monetary txs are small. If you want data then get a DropBox account.

• 
  GLITCH (@Rukkssss__) reported 8 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

• 
  𝓅𝓇𝒾𝓃𝒸ℯ𝓈𝓈 𝓵𝓾𝔁💗👑 (@payprncslux) reported 10 minutes ago

  got a new phone & laptop now I can’t login to my dropbox because I don’t have my old devices .. fml

• 
  🔆 j i k o ⋆₊ ‧ ˚⊹ 🏜️ (@lisey_ann) reported 12 minutes ago

  @joinautopilot @charliebilello I can see why a bunch of those are sagging (joke? Or maybe I'm not joking): - Snapchat is in decline, less users overall. - Streaming subscriptions are becoming too expensive to keep up w/ inflation - X likely sagging ever since its lead advertisers left - Dropbox: user usage declining? (I use Google drive, Mega) - Alibaba: Chinese knockoffs, not bound to survive long - doordash: getting too expensive, way too many fees whenever I've used it, even WITH the discounts - Roblox: declining corporate - Snap: declining user usage, they constantly advertise Snapchat+ and idk anyone who actually uses that - Facebook: meta's side hussles were failing (notable: metaverse shutdown) - coinbase: app is ALWAYS buggy, slow, Base wallet became infested with scam tokens with no way to report, I personally stopped using it for this reason - pinterest: we just have AI to put together mood boards now, Pinterest not needed - Uber: same fee problem as doordash plus majority of gig drivers in my experience are the same few Indian drivers - uipath: likely not keeping up with the AI agent competition - bumble: women are probably tired of it tbh - lyft: same problems as Uber and doordash I can't answer for some others because I'm not as familiar or just can't think of a reason why they have poorer returns, so I dunno.

• 
  TechSnif (@techsnif) reported 17 minutes ago

  Dropbox founder Drew Houston steps down as CEO after 19 years, replaced by SVP Ashraf Alkarmi

• 
  David Llada ♞ (@davidllada) reported 20 minutes ago

  @Dropbox I’ve been dealing with an issue for a few weeks now, and your AI customer chatbox has been unable to resolve it. It keeps looping through the same troubleshooting steps that haven’t worked, and I’ve already spent over three hours on it. "It looks like our chat has wandered into areas I'm not equipped to handle effectively. Unfortunately, I can only help with Dropbox-related questions, and I'm unable to help you with this topic." I’ve been a customer since 2009. It’s disappointing to reach this point, but this level of support is unacceptable.

• 
  ray🥤 (@rayontrack) reported 20 minutes ago

  bookmarked, downloaded, screen recorded, emailed, stored in hard drive, uploaded to cloud, archived, backed up, shared via bluetooth, forwarded, copied to usb, saved offline, synced across devices, added to favourites, printed, password protected, compressed into zip, renamed, organised into folders, duplicated, exported, imported, attached to message, sent to recycle bin, restored from backup, converted to pdf, edited, highlighted, annotated, watermarked, uploaded to google drive, uploaded to dropbox, shared through airdrop, linked to notes, tagged, encrypted, burned to cd/dvd, cached, mirrored to another device, uploaded to server, queued for transfer, dragged into archive, pinned, added to reading list, stored on ssd, embedded in document, linked in spreadsheet, previewed, sent to printer queue, recovered from trash, and indexed for search.

• 
  ScarcityMan (@ScarcityMan) reported 24 minutes ago

  You might not believe it, but it is in fact happening, because it increases the cost, time, and difficulty of running a node. "Large" is a matter of opinion, but is clearly a quantity which would add up over time and have an impact. Why don't you want nodes to be as easy to run for people as possible, so that the maximum number of people can participate in the network, making it more valuable and more resilient? Why is that not something you want, to the extent that you will spend time arguing against it? What exactly is your stake in nodes being more difficult to run than they need to be? Why don't you care about spam? Why don't you care that it obviously, as it does everywhere it exists, degrades the quality of the thing being used? Why do think bitcoin will just be fine and go on forever while watching it transform into a poor imitation of dropbox? Why would anyone interested in bitcoin as money continue to use it when it becomes more and more infested with non-monetary data? Why don't you care about the possibility of truly bad stuff ending up on chain until the end of time? Do you think Satoshi made a mistake? Should he have created "Bitdata" instead? Do we not need to fix the world's money? You good with USD or whatever else is inflating away to nothing? So many questions that will never be answered...

• 
  CHItrader (@CHItrader) reported 25 minutes ago

  $DBX Dropbox CEO to step down, CNBC reports

• 
  Auntieesq (@daniell0930) reported 25 minutes ago

  @MikeJShowalter The issue is the use of the data to train models not retention. Acting as if this is the same a Dropbox is disingenuous. They will not use the data to train for non-safety issues. Non-safety issue is doing some heavy lifting there. Do they have an outline of what this means?

• 
  Chuck Thies (@ChuckThies) reported 26 minutes ago

  Apples to oranges. 2024 was not a mayoral election. The best comparison is 2022/2026. Last week, mail/dropbox performance was down about 15% as compared to the 2022 primary.

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