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:

• 
  Sunkanmi Fafowora (@the_jonin_) reported 5 minutes ago

  @hashnode Thank you! It's back up now. That was so weird. I didn't even receive an explanation as to why it was taken down, but my work is back up now, which makes me happy, but still very cautious without an explanation. I think I'll have to keep using Dropbox in the meantime

• 
  Arthur "lynch mob" van Pelt 🔥 ∞/21M ⚡ (@Arthur_van_Pelt) reported 6 minutes ago

  @laz1m0v @adam3us You want a multifunctional database. Go try BSV or Microsoft SQL Server or Arweave. They have what you want. Bitcoin is money. Not a Pepe Dropbox. Go take your Pepes elsewhere, please. Then we wouldn't even need filters if everyone behaved in the spirit of Cash instead of Pepe.

• 
  ṢƘĪÑlÖVẸ́R̃ṢX🇺🇲🌷 (@skinloversx) reported 6 minutes ago

  Hey Daddy I'm down for FaceTime 💧 Dropbox and all kind of nasty content message me for menu 💦💦🍆 #dmvfreaks

• 
  Alchemist - τ (@SubnetSummerT) reported 10 minutes ago

  @Dropbox piloting @LeadpoetAI is worth slowing down on. Dropbox spends around $370m a year on sales and marketing. That's the budget Leadpoet is now piloting inside. For context, SN71's entire market cap is about $4m. The annual sales budget of one pilot customer is roughly 85x the value of the whole subnet. Leadpoet doesn't need to win the budget. Capturing even a fraction of a percent of enterprise sales spend at companies like this is meaningful revenue. And revenue is where the flywheel starts. Usage burns alpha. Burn supports the token. Stronger emissions attract better miners. Better miners produce better leads. Better leads win more budget. Repeat. @webuildscore (SN44) showed what happens when a subnet ties real commercial usage to its token. Leadpoet is running the same playbook against enterprise sales budgets, which are measured in hundreds of millions per company.

• 
  Hawk (@iamhawkspire) reported 14 minutes ago

  @TheMilitiaGamer @Google nah lol, i'm just rawdogging without any online backups for my larger files atm. might end up checking out dropbox, tho their speeds are super slow on my end.

• 
  Mike Nolan - ⌬CatalyticComics⌬ (@CatalyticComics) reported 15 minutes ago

  As a developer I wanted to build something that addresses every issue I've run in to as a reader. These are my top ones: - Campaigner emails a Dropbox link and maybe you miss it - DRM/server requirements that amount to "you don't really own it" - No above-board way to share

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

• 
  J.F. Lawrence | Author (Jesse) (@jflWrites) reported 18 minutes ago

  @spaceemotion All good ideas. I've thought about Dropbox, Google Drive, and OneDrive. They suffer from persistence, login requirements, and users fiddling with things that change permissions. AWS is cheap, and I'm considering it, but I'm trying to pay for this off of my measly book sales, so...

• 
  ray🥤 (@rayontrack) reported 19 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.

• 
  i-LevelUP (@CryptoScout24) reported 19 minutes ago

  Popular Services/Messengers That Are Typically NOT (Fully) End-to-End EncryptedThese are the ones affected by scanning under the current EU Chat Control setup which has passed today in the EU: Email services (most standard ones): - Gmail (Google) - Outlook/Hotmail (Microsoft) - Yahoo Mail - iCloud Mail (Apple, standard) - Many others without E2EE enabled - Facebook/Instagram Messenger (standard mode) — Often not fully E2EE unless "Secret Conversations" are turned on - Skype (standard chats) — Microsoft can access content. - Snapchat — Chats and snaps are not E2EE by default (some features have it, but not comprehensively) - Telegram (standard/cloud chats) — Encrypted between device and server, but Telegram holds the keys and can access content. Only "Secret Chats" are protected. - Discord — Messages are not E2EE; the company can moderate/scan - Older/traditional SMS/MMS — Completely unencrypted. - Xbox Live messaging and some gaming platforms. - Cloud storage/file sharing tied to chats (e.g., Dropbox, iCloud, Google Drive in some contexts) — Often scanned Let that sink in ! allegedly to fight against child abuse

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 21 minutes ago

  @DropboxSupport Turns out it wasn't normal. Forcing a Rebuild inside of Windows Indexing Options was the fix. Windows Issue. Resolved for now.

• 
  Zafar (@zafartalks) reported 21 minutes ago

  @asidorenko_ I understand but sometimes at some point our brain started telling us just make it public. You never know. Let’s not forget Dropbox which layed the foundation for their file sharing competitors. He was solving a problem for himself which turned out to be a successful business.

• 
  uncle ***** (@probinsyacore) reported 22 minutes ago

  nraas still down but a reddit user has saved most of their mods in a dropbox link oh my god sometimes i do love the internet

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

  System design question. How would you design Dropbox file sync with conflict handling? Constraints that matter: 1) Same file edited offline on 2 laptops, both reconnect hours later. No central lock. What wins, how do you surface conflicts, can you auto-merge for some types? 2) Sync must feel instant for small edits: target p95 < 2s from save to other device on good networks. 3) Files up to 10GB. Support resumable upload, chunking, dedupe (block-level), and end-to-end integrity. 4) Must work across flaky networks, NAT, and clock skew. You cannot trust client timestamps. 5) At-least-once delivery of change events. Idempotency required for apply/ack. 6) Millions of clients polling/streaming. Avoid a thundering herd after an outage or deploy. 7) Rename/move storms and folder deletes. Preserve history and allow restore without corrupting sync state. 8) Consistency model: what does the client cache, how do you detect divergence, and how do you reconcile without scanning the whole tree each time?

• 
  leveltu (@leveltu144) reported 27 minutes ago

  Most people look at this box and see a home storage system for old drives. In reality, it can become a small business built around local AI, backups, and private data. The more companies use AI, the faster they accumulate documents, videos, call recordings, knowledge bases, backups, and files for RAG systems. Keeping everything in Google Drive or Dropbox becomes expensive, slow, and risky, so small businesses increasingly need local NAS servers with automated backups and secure private-cloud access. The business model is straightforward. You target small agencies, dental clinics, accounting firms, video studios, e-commerce companies, and manufacturers that already hold 2–10 TB of data but still store it across random external drives. Then you sell them a complete solution: NAS installation, RAID configuration, automated backups, remote access, protection against data loss, and local storage for AI workflows. You can charge €400–€900 for installing and configuring the system, excluding the hardware itself. Monthly maintenance, backup verification, and monitoring can add another €80–€200 per client. Close five companies within the first two or three months at an average setup fee of €600, and you generate €3,000 from installation plus roughly €600 in recurring monthly revenue. Ten clients can produce €1,200–€2,000 per month from support alone. The real profit is not in reselling hard drives. The client pays for the equipment, while you sell the audit, configuration, data migration, automation, and responsibility for keeping the system operational. The service layer can carry far higher margins than the hardware. No one can honestly guarantee income within 90 days, because without sales there is no business. But reaching your first €500–€1,500 per month within two or three months is realistic if you build one demonstration NAS, package the offer clearly, and contact at least 30–50 potential clients every week. While everyone else is trying to make money from another AI chatbot, a more durable business is forming around the infrastructure AI cannot function without: data, storage, backups, and private computing.