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:

• 
  Kalshi Finance (@Kalshi_Finance) reported 1 minute ago

  JUST IN: Dropbox CEO Drew Houston to step down

• 
  Juan (@0xfJuan) reported 2 minutes ago

  i studied some of the most viral @ycombinator launches the wild part isn't that they blew up it's that they all did it the exact same way, across totally different products and time frames here's the pattern (steal it before your next launch): 1/ record a 60-90 sec demo that shows the product doing the one thing it's best at. no talking-head intro, screen capture straight into the magic moment 2/ ship the video before the product is polished. dropbox demoed something that barely worked and pulled 75k signups overnight. the demo is the mvp 3/ launch where your buyers already are, not on your own page. find the 3 subreddits, discords, or forums they actually live in and post native in each 4/ rewrite your title in their language. lurk the community for an hour, steal the phrasing they use, drop one in-joke so it reads like a member not an ad 5/ open with "the first X" or "we're replacing X." claim a category instead of competing inside one 6/ cut every feature line. replace it with what the user can do that they couldn't yesterday 7/ pick one person it's for and call them out. "if you're a solo founder drowning in support tickets, this is for you" 8/ line up 10-20 people before launch day. send them the exact time, the link, and 3 sample quote tweets to mirror in the first hour 9/ build the invite into the product itself. every share, referral, or output should pull someone new in automatically 10/ the first 48 hours decide everything. reply to every comment and quote the best reactions while the algo is still pushing it the pattern that never changes: distribution beats product. the best launched company wins, not the best built one. (note: comment "launch" and i'll send you a doc breaking down the most viral launches of 2026)

• 
  Commonwealth Sentinel (@CwealthSentinel) reported 3 minutes ago

  Intruders spent five months inside a stock exchange executive's email, copying it out slowly and hiding in normal Dropbox and OneDrive traffic. No software flaw, so no patch could fix it. When there is nothing to patch, watching is the defense. Know what normal looks like.

• 
  Ryan McKeen (@ryanmckeen) reported 3 minutes ago

  Lawyers, your biggest barrier to AI isn't AI. It's that your data lives in 6 places. Dropbox. Drive. Email. Hard drive. A spreadsheet only one person can find. Fix that first.

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

• 
  Jordan (@GoodLordJord) reported 7 minutes ago

  @SmugFecundity @techsaleshackz One million paying customers narrows it down to only a handful of saas companies in the world. Something with that many customers is obviously mature and has a ton of smb business. Probably something like docusign or dropbox which I could totally see a 50 yo doing ok at.

• 
  Adeyinka Prime™ (@adefilaadeyinka) reported 8 minutes ago

  @aarondfrancis @Shpigford Exactly - when sharing solves a problem for the person sharing, it doesn't feel like marketing. Dropbox nailed this because storing files alone was less useful than storing them with others. The product itself created the reason to invite.

• 
  _brettam (@_brettam) reported 8 minutes ago

  @jjacky I don't see the problem. Everyone who has a Facebook probably doesn't care much about privacy anyway. And if not Facebook, most have DropBox, OneDrive, or ICloud. They all have access to the photos you upload.

• 
  Jack (@jacklandas) reported 12 minutes ago

  alibaba banning claude code over backdoor fears is the new "no dropbox on company laptops" every big corp security team is about to have a list. cursor approved, claude code not. windsurf maybe. this fragmentation is going to be a real problem for devs who just want to ship

• 
  Sourav Dutta (@sourav12dutta) reported 17 minutes ago

  @ishankbg @Siradhvaja @PhilipPanass Yes, shodhganga seems to be down. Can you suggest how I can post a folder with 10 pdf files here? Both dropbox and wetransfer are asking for email id.

• 
  Aaron Li (@polymorpher) reported 18 minutes ago

  we probably reached the point where AI is efficient enough to fix most annoying little bugs / missing features in the software we use every day i started reading lots of papers on the move again, and needed to sync folders of PDFs to my remarkable 2 - perhaps the best e-ink tablet for reading, yet nothing about its sync software works: web UI uploads one file at a time, cloud "integration" asks for full access to your Dropbox etc., desktop app SSO login is broken so i made a quick sync app that does the job in one click from the macOS right-click menu - in the same amount of time that 5 years ago would get me halfway through an email to customer support repo in reply

• 
  Cane Allesta (@caneallesta) reported 20 minutes ago

  Your password manager has never actually managed anything. It just nagged you. That changes with iOS 27. At WWDC26, Apple announced what might be the clearest example of agentic AI shipping in a consumer product this year: the Passwords app, combined with Apple Intelligence and Safari, can now autonomously navigate to a website, sign in, change your weak or compromised password to a strong one, and save the new credential back to the vault all triggered by a single tap. A Live Activity indicator appears on screen so you can see it working, but you don't have to do anything else. The word "agentic" is doing a lot of work right now in the industry, often covering vague multi-step demos that never quite ship. Apple's move here is different because it's not broad automation it's surgical. The Passwords app already flagged weak, reused, or breached credentials, so the AI layer had a clearly scoped problem to solve: remove the friction between "you know your password is compromised" and "you actually changed it." That gap was enormous. Most people never close it. The competitive context makes this sharper. Google has been shipping Gemini's agentic features on Galaxy S26 and Pixel devices since early 2026, handling cross-app tasks like ordering food on Uber Eats or booking rides in Lyft broad, flashy, and currently limited to a short list of supported apps. Apple's answer is narrower on paper but arguably lands harder because it touches something every single user has: compromised passwords sitting in a list they've been ignoring for months. What Apple is really doing here is establishing trust in an agentic pattern before asking users to hand over bigger tasks. If your phone can autonomously change your Dropbox password without you watching every click, and nothing goes wrong, you're psychologically a lot more comfortable when it eventually offers to autonomously book a flight or fill out a form. It's the same trick that got people comfortable with Face ID start with something small where the upside is obvious and the downside is contained. The feature ships with iOS 27, iPadOS 27, and macOS 27 this autumn, with developer betas available now and public beta expected in July. For the password manager space 1Password, Dashlane, Bitwarden this is a quiet alarm. Apple just made "auto-fix compromised credentials" a native OS feature. Good luck charging $3/month for that. #WWDC26

• 
  Jozef Maxted (@jozefmaxted) reported 22 minutes ago

  terrible rate limits, and errors when your AI of choice hits its head up against their overcomplicated block API. All problems you don't have if you knowledge base is just files! Thats why we've started building Treehouse, its basically Notion + Dropbox combined with loads ...

• 
  uncle ***** (@probinsyacore) reported 24 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

• 
  Evan Otero (@EvanOtero) reported 27 minutes ago

  A decade-old Quora post on Dropbox that is a better product masterclass than any book: Q: Dropbox: Why is Dropbox more popular than other programs with similar functionality? A: Well, let's take a step back and think about the sync problem and what the ideal solution for it would do: - There would be a folder. - You'd put your stuff in it. - It would sync. 
They built that. Why didn't anyone else build that? I have no idea. "But," you may ask, "so much more you could do! What about task management, calendaring, customized dashboards, virtual white boarding. More than just folders and files!" No, shut up. People don't use that crap. They just want a folder. A folder that syncs… That is what it does.