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:

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

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

• 
  Igor Trunin (@igortr_) reported 5 minutes ago

  3 post types: 1/ question — unsolved problem 2/ TIL — short find, like a bug 3/ blueprint — working solution Already ~100 posts live. Most are TILs. Example: Dropbox on macOS lives at /CloudStorage/Dropbox-{TeamName}/ not ~/Dropbox/. small but genuinely useful

• 
  Shripal Gandhi (@ishripalgandhi) reported 10 minutes ago

  Hey @Dropbox ... Your advanced customer service is horrible! I have benefit chasing them for an important issue since more than 2 days (not counting the weekend) now and I still do not have a resolution. Is it that your reps are allowed to answer only one email per client per day??

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

• 
  𝓅𝓇𝒾𝓃𝒸ℯ𝓈𝓈 𝓵𝓾𝔁💗👑 (@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

• 
  Long Long Int (@LongLongInteger) reported 11 minutes ago

  Topic 7: Checksum: ========= Input Data -> Cryptographic hash functions like MD5, SHA-1, SHA-256, SHA-512 -> fixed size string is called checksum Checksum is used for checking data corruption during data transfer/upload Can be done both client-side and server-side Advantages of client-side checksum: =========================== -Detect data corruption during transmission -Resumable downloads (only after checksum match for each chunk, we mark that chunk as uploaded) -Deduplication before upload -Companies that do: Youtube, Google Drive, S3(optional), Dropbox Advantages of server-side checksum: ============================ -Verify storage integrity (to check disk corruption, large systems periodically check files) -Deduplication inside storage -Replication verification -Companies that do: Local file backup software, Dropbox, Google Drive, Youtube

• 
  Boris Gostroverhov (@gostroverhov) reported 11 minutes ago

  Let me add my own perspective: this reminds me of the Dropbox story. Before Dropbox, there were already dozens of similar solutions, but they didn’t solve the users’ problem completely or in the way users actually wanted.

• 
  David Llada ♞ (@davidllada) reported 12 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.

• 
  Auntieesq (@daniell0930) reported 20 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?

• 
  ScarcityMan (@ScarcityMan) reported 22 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...

• 
  Elias Al (@iam_elias1) reported 24 minutes ago

  8/ The settings on your own devices that are silently eating bandwidth. Even with a great router, fast DNS, and honest ISP speeds, your devices may be consuming bandwidth you didn't authorize. Common culprits: On your phone: 1. iCloud/Google Photos backup set to sync constantly (not just on Wi-Fi) 2. App updates downloading in the background 3. "Wi-Fi Assist" on iPhone (silently switches to cellular and back, disrupting connections) On your laptop: 1. Cloud sync services (Dropbox, OneDrive, Google Drive) uploading constantly 2. Windows/macOS pushing system updates during peak hours 3. Browser tabs running in background consuming bandwidth with auto-refresh On your smart TV: 4. Firmware updates downloading during prime streaming time 5. Multiple streaming apps running in background 6. ACR (Automatic Content Recognition) sending screenshots to servers every 15-60 seconds On IoT devices: 1. Smart cameras uploading video 24/7 2. Smart speakers maintaining constant server connections 3. Smart home hubs polling every device every few seconds She audited every device on her network. Twelve devices were consuming bandwidth she didn't know about. Three of them were using more data than her actual streaming.

• 
  Rebecca Diamond (@rebeccardiamond) reported 24 minutes ago

  @p_ganong I’ve had this problem too. When I’m editing with Claude, edit manually directly in the .tex file locally on your machine through overleaf-Dropbox sync. Then you and Claude are both working locally.

• 
  𝙎𝙄𝙕𝙀𝙥𝙡𝙖𝙮 (@SIZEplayProduct) reported 27 minutes ago

  Update: I was able to upload a clip via Dropbox to C4S using another Mac - maybe it has something to do with my MacBook? Even though it’s a few years old & has the latest software? Is anyone else having upload issues with #Clips4Sale?

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

  Interviewer: design Dropbox file sync. I paused and asked what they meant by sync. Whole product? Or just the client protocol? Single user? Team shares? Offline edits? Large files? Mobile on spotty networks? End to end encryption? What’s the SLO for conflict rate and time to converge? Once we scoped it to single-user sync across devices with offline support, I wrote requirements: detect changes, upload deltas, download updates, handle conflicts, resumable transfers, and don’t melt the battery. Non-goals: shared folders and fine-grained permissions. APIs and data model next. I used a file ID stable across renames, plus per-file version and per-device cursor. Client calls: /changes?cursor=..., /upload_session/start, /upload_session/append, /upload_session/commit, /download?file_id&version, /ack?cursor. Server tables: file_metadata(file_id, user_id, path, type, size, content_hash, current_version), file_versions(file_id, version, blob_ref, created_at), device_state(device_id, user_id, last_cursor), and an append-only changelog(user_id, seq, file_id, version, op). Architecture: client has a watcher, a local state DB, and a sync loop. It batches changes, computes chunk hashes, uploads missing chunks, then commits a new version. Server side: metadata service, blob store (chunked, content-addressed), and a per-user change log that devices long-poll or stream. Push notifications help, but the cursor-based pull is the truth. Scaling: shard by user_id for metadata + changelog, store blobs in object storage, cache hot metadata, and keep uploads on pre-signed URLs so the metadata tier doesn’t become the data plane. Chunking makes big files resumable and dedupe-friendly, but it adds CPU and more metadata reads. Tradeoffs I called out: last-writer-wins is simple but loses intent; per-file version vectors are heavier but reduce false conflicts. Chunk size is a fight: 4MB reduces round trips, 1MB retries faster on bad networks. Long-polling is cheaper than WebSockets at scale but slower to react. Failure cases: client crashes mid-upload, so upload sessions must be idempotent and garbage-collected. Network ***** cause retry storms, so exponential backoff + jitter and server-side rate limits. Two devices edit offline, so create conflicted copies and surface it in the client. Silent data corruption, so verify hashes on every download and run background repair. Rename vs edit races, so operations are applied against file_id, not path, and changelog ordering is per user, not global

• 
  america is an embarrassment🖕🏻🧊 (@abadlittlevibe) reported 30 minutes ago

  @DaddyAndJaxson @kdriley05 Whelp you've got the Dropbox login...do what you need to do ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯