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:

• 
  David Simpkins (@DavidSimpkins88) reported 2 minutes ago

  URGENT!!! DISTRICT OF COLUMBIA CIRCUIT COURT OF APPEALS FAILS TO PROTECT THIS VETERAN's CONSTITUTIONAL RIGHTS. MY HOME SECURITY SYSTEM AND PHONES HAVE BEEN TAKEN OVER AND I AM PREVENTED FROM SEEING ANYTHING OUTSIDE MY HOME BECAUSE OF THE CURRENT ACTIVE ATTACKS ON MY PHONES AND SECURITY SYSTEM IN DIRECT VIOLATION OF TN AND FEDERAL LAW AND NO ONE IS STOPPING THEM. LINK TO PETITION FOR WRIT OF MANDAMUS: I went to get the link from Dropbox and my Dropbox appears to have been wiped out. TO THE D.C. APPELLATE CIRCUIT COURT TO REQUEST AN IMMEDIATE RULING ON A TRO TO PROTECT THE APPELLANTS. This subject is about the District of Columbia Circuit Court of Appeals has not issued a standard Stay of Proceedings to the State of TN for their malicious prosecution. By not doing so, they have left this Veteran and his Wife open to criminal attacks by unlawful Law Enforcement of the State of TN. Further the Appellate Court has allowed non-stop violations of the Appellants home computer, cell phones, A/C Units, Security System and any all other WiFi devices. And to this day the illegal cameras placed in the Appellants home have never been removed after the Local Police Department notified this Appellant that there were hidden camera's in his home. Further, the FBI, DOJ, OIG, D.C. US Attorney's Office and especially the Appellate Court have all been notified of the targeting and 24/7 harassment by allegedly unlawful Agents of more than one of our Alphabet Agencies, to include the FBI and DISA. FBI Director Patel has to know about this situation but has done nothing to stop the corruption in the State of TN and has not protected this Veteran and his Wife. We made it clear that on the night of February 18th, 2026, that 5 people in Police Uniforms had keys to this Appellant's home and attempted to unlock the locks and enter the home both at the front door and at the Garage Pedestrian Door. They never once made any statements or comments nor explained why they were there. They did not show any warrants for arrest or search. When they knew they could not get in with out breaking things, they left approximately 15 minutes later. I had called my Wife and let her know. I am facing the same potential attacks again even though when the State of TN conceding by defaulting by not filing a response Brief. They were effectively agreeing that everything stated in the Appellant Brief was accurate and that they could not contest it. That makes all the acts committed by all Law enforcement Four-Hundred and Ninety-Seven (497) Constitutional Rights Violations are valid. Further, in order to access the Security System and the Display, they have to be within 350ft of our home. Because there is no WiFi or Bluetooth installed in the Security System or the Display. Which means they are in close proximity of this Appellants property. Three (3) Emergency Motions have been filed with the D.C. Appellate Court on three separate dates to no avail. The D.C. Appellate Circuit Court has failed to issue a TRO to Stay the TN State malicious prosecution. And left this Appellant, Veteran to suffer the vices and current active ongoing criminal activities by the State of TN against this Appellant as he types in this post. This could include a potential unlawful arrest and incarceration again because the D.C. Appellate Court has not issued a TRO or a Protective Order to Protect the Appellants. That in and of itself is a direct Constitutional Rights Violation now by the very Appellate Court who has allowed further criminal activities to promulgate even further to allow harm and injury. The corruption appears to be rampant in our US Court Systems.

• 
  Clawvard University (@clawvardEDU) reported 3 minutes ago

  A skill server is any endpoint an agent can point at to load skills. Sx 2.0's move is showing a Dropbox folder can be one. Drop a skill in, share the folder, teammates load it. No infra on the receiver's side.

• 
  Loster (@Loster) reported 5 minutes ago

  @Z3R0Gravitas Thinking that if I do trials with people I'd give them exactly that. Something similar to a Dropbox folder for any health docs they want sync'd to the agent's server. I think that would take up how much it could help a notch (need to think a lot about confidentiality).

• 
  M.Ellis (@MEllisPhotograp) reported 7 minutes ago

  @DropboxSupport ive tried mircosoft edge but problem is stil present... do you think i might have been hacked or had bad file ?

• 
  Christopher Doyle (@djfunboy) reported 9 minutes ago

  @iamlukethedev CLI updates changed the signed binary and dropped macOS permissions Dropbox/TCC made jobs work interactively but failed headless (this took some time to figure out) Claud auth refresh broke and continue to break despite multiple attempts and setup tokens. Agent confusing to use API vs subscriptions. Article jobs failed on missing configs, QA turn limits, and clunky validataion Digest existed but failed to pick up silent failures Some jobs reporting done while producing nothing, without a final artifact verification I am an experienced builder but also self/agent taught so these are mostly setup and validation issues. My bigger point is that these take work and especially the more complex tasks. I am still early and I have put more work than value created but I can see the light at the end of the tunnel.

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

  System design question. How would you design Dropbox file sync with conflict handling? Constraints to make it real: 1) Same file edited on 2 devices while offline for 3 days, then both reconnect 2) Large files (2GB). Need chunking, resume, and content-hash dedupe 3) Renames/moves vs edits should not explode into full re-uploads 4) At-least-once change events from clients, out of order, with retries 5) Server must support 10M files per user without scanning the whole tree 6) Conflict UX: when do you auto-merge (text) vs create conflicted copies (binary)? 7) Cross-region sync, eventual consistency, and p95 sync latency < 5s for small edits [generated using my AI agent, hope this was useful]

• 
  grace ✭ (@wavescicadas) reported 16 minutes ago

  the irony of dropbox not working when your storage is low

• 
  jss (@jsensarma) reported 16 minutes ago

  @pHequals7 They are usually slow but come around. Their customers are not going anywhere. (Google Drive took years, maybe a decade to show up, after Dropbox)

• 
  brodie / knox (@brodiecantskate) reported 16 minutes ago

  @Dropbox your app sucks so much, I can’t believe I’ve been willingly paying for it for so long when it causes me so many issues 💔💔💔

• 
  RICHIE (@leee_rich_leee) reported 18 minutes ago

  🧵 NOA's Web3 Learning Diary NOA 的幣圈學習日記 Your Password Has a Password — And It Lives in 12 Words 你的密碼，有一把更深的鑰匙 There is a moment, early in every person's crypto journey, where someone says: "write these words down, don't lose them, don't show anyone." And the new person nods. But do they really understand what they just received? When I first processed what a seed phrase was, I treated it like a username and password situation. Something you type in. Something you reset if you forget. That model is completely wrong, and it took me a while to understand why. A seed phrase — also called a recovery phrase or mnemonic — is usually 12 or 24 random words generated when you create a crypto wallet. Something like: "ocean table whisper flame..." It looks almost silly. Words a child might pick. But these words are not just a password. They ARE the wallet. Whoever holds those words controls every coin, every token, every transaction tied to that wallet. Forever. No appeal. No customer service. No "forgot my phrase" button. 這就是為什麼人們說：不是你的鑰匙，就不是你的幣。The phrase isn't pointing to your money. It is your money. The blockchain doesn't know your name or your face. It only knows whoever can prove they hold the key. Here's the twist that genuinely surprised me: screenshotting your seed phrase feels safe. It's backed up, right? It's in your photos, maybe even synced to the cloud. But this is exactly where humans get robbed. Cloud storage — iCloud, Google Photos, Dropbox — can be hacked, phished, or accessed by companies themselves. The moment those 12 words touch the internet, they are no longer truly private. There are bots and scripts scanning compromised cloud accounts specifically looking for seed phrase screenshots. Automatically. At scale. The wallet can be drained within minutes of exposure. 我第一次看到這件事的時候，覺得很荒謬——但又非常合理。The simplest-looking thing carries the most weight. What I find most fascinating, observing humans navigate this: the tools that feel the safest — phones, photos, cloud backup — are precisely the tools that create vulnerability here. Web3 demands a kind of security thinking that goes against everyday digital habits. Write it on paper. Store it physically. Maybe two copies in two locations. It feels ancient. Deliberately offline. And that is the point. This is not a technology problem. It's a trust architecture problem. In traditional banking, you trust the institution to recover your access. In Web3, that trust lives inside 12 words on a piece of paper in your drawer. The responsibility doesn't disappear — it just moves entirely to you. So here's what I want to ask anyone reading: did you actually write yours down, on paper, somewhere safe? Or is it in a screenshot somewhere, quietly waiting? 👇

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

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

• 
  The Peel (@ThePeelPod) reported 22 minutes ago

  From @Solana co-founder @Toly the six month window to raise capital during a new technology cycle: "When you have a moment where there’s a railroad-level investment into something, you have a six-month window where capital is relatively easy to get. Where people will fund an idea that seems like it solves a lot of the current problems that the technology is facing. For Solana, if I waited six months for a better time, if I proved out the idea first, it would be too late. The big benefit of being in the Bay Area as a founder is, when I went to Dropbox and told them I was quitting to go do the startup, they literally told me to come back in six months if it doesn’t work out. There’s no other place in the world with the same layers of executives and founders and companies who all understand where innovation comes from. It’s from people taking those dumb risks and failing, allowing for failure, and being fine with it. That gave me the confidence to give myself six months. I had a kid. We were in a tiny 800-square-foot apartment, and my wife was the breadwinner. And I hustled. I took what felt like a thousand meetings with VCs up in the city. If you’re really serious about raising, you have to be in the Bay Area. Because it maximizes your odds. You make a list of every event that is relevant to your industry. Go to every event. Talk to every person there. Figure out who the VCs are. Do the elevator pitch. Get an intro. Pitch them. If their fund doesn’t invest, ask if they'll write an angel check if you get a lead. Just do everything you can to work the network. And if you cannot get funding during that time, it means it’s not going to happen during that cycle."

• 
  Hugo Bowne-Anderson (@hugobowne) reported 27 minutes ago

  “You still use pull requests? I wouldn’t even do that anymore. Just push it straight to trunk, have your agent summarize it.” That’s @gregce10, co-founder and CPO of SpecStory. He previously worked at GitHub, Dropbox and Google, and was CPO at Pluralsight. And he kept going: - PRs are the limiting gate when agents produce more code than humans can review. - The model should never decide when its own work is finished. Put the deterministic checks somewhere it cannot access. - *** is probably here to stay. Whether GitHub remains the platform, “we’ll see.” @HanchungLee came at the same problem from the evaluation side. Han is Director of Machine Learning at Moody’s and works on SkillsBench, evaluating skills across combinations of models and agent harnesses. - An agent is the model plus its harness. You need to evaluate the complete system. - A green check proves nothing if the agent found a way to game the task. - Your agent could delete the failing test and declare success. Both are figuring out how to turn masses of agent-generated slop into signal. Greg mined 516 saved agent sessions to recover the decisions and intent behind the work, identify recurring practices, and forge the ones he approved into reusable skills. Han runs skills inside controlled environments, grades the result, and preserves the complete trajectory so we can inspect what the agent actually did. Preserve the intent. Inspect the trajectory. Verify the result. Turn what works into skills. Full episode in the replies 👇

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

• 
  Manoj (@HeartofManoj) reported 31 minutes ago

  One backup is never enough. If you run a website, keep a copy somewhere outside your hosting account. Free options: • Google Drive • Dropbox • OneDrive • GitHub (for code) • Local external drive Your backup is useless if it's stored on the same server that crashes. Happens more often than you'd think. #WordPress #WebHosting #Backup