Dropbox status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Dropbox reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Dropbox users through our website.

• Errors (50%)
• Sign in (33%)
• Website Down (17%)

Live Outage Map

The most recent Dropbox outage reports came from the following cities:

City	Problem Type	Report Time
Bournemouth	Sign in	1 month ago
Paramaribo	Errors	2 months ago
Bogotá	Website Down	2 months ago
Auxerre	Errors	2 months ago
Salt Lake City	Sign in	2 months ago
Madrid	Errors	3 months ago

Full 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:

• 
  RICHIE (@leee_rich_leee) reported 2 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? 👇

• 
  Bunnie Maiiii (@imbunniemai) reported 5 minutes ago

  @JohnRai21044566 Ill!!! since Fansly having problem I can not post throu phone atm. I’ll have to get all those files to Dropbox then post on Fansly. This set will be posted in 2 days 😭😭 sorryyyy baby Im bit busy but I’ll try post as soon as I cannnn

• 
  Matthew Tse (@MatthewTse_) reported 8 minutes ago

  @DropboxSupport Yep, still broken.

• 
  Ilya Sandoval (@ilya_sandoval) reported 11 minutes ago

  @Dropbox having AGAIN problems with the payment between Apple and Dropbox and AGAIN NOONE FROM you guys help me

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

• 
  Harman (@itsharmanjot) reported 12 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

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

• 
  RyanFox.eth (@ryanfoxeth) reported 14 minutes ago

  “consumer doesn't run on problems” 👏 Consumers will pay to be entertained. Businesses will pay to be productive. This is a lesson the tech industry is forced to learn every decade or so. Apple, Microsoft, Google, Mozilla, Dropbox, Evernote, Quip, AirTable, Trello, etc have all learned this the hard way. We saw it play out in crypto. Today it’s playing out in OpenAI vs Anthropic.

• 
  BadUncle (@BadUncleX) reported 15 minutes ago

  @mitsuhiko Similarly, I still use the old version before 7. They try to force you to bind to their server-dependent version. I prefer to use dropbox to synchronize.

• 
  Natan Hackbarth (@Natan90850688) reported 19 minutes ago

  @peterhowell I used the original pak0.pak. I tested both Dropbox and PixelDrain hosting and tested the exact URL format from the README The app reaches "Fetching PAK" but then fails with "Could not fetch PAK URL" and a 403 error. What hosting method did you use when testing your own pak0.pak?

• 
  ぱんじろう(・ー・)？ (@CopenPanjiro) reported 19 minutes ago

  On Essentials plan. Ticket #26375062 top support evades the core issue by vaguely blaming my PC environment. I've already verified registry & OS. Stop dismissing verified technical logs and escalate this bug to the dev engineering team now. @DropboxSupport

• 
  Adrien Matray (@AdrienMatray) reported 21 minutes ago

  The trap: when ~/.claude/ is in Dropbox, it often seems to work. No error message. Sometimes your preferences load, sometimes they do not. The symptom is silent quality drops you cannot trace. Not a visible failure. That is why people miss it.

• 
  Veltrx (@Veltrxai) reported 21 minutes ago

  Sam Altman taught 720 startups one formula where luck is a random number between 0 and 10,000. Stanford, 2014. The opening lecture of CS183B was so packed he asked for a bigger auditorium. He was 28, a dropout from this same school 9 years earlier, now running Y Combinator. The formula he wrote on the board: idea × product × team × execution × luck and you only control 4 of the 5, because the fifth one goes to 10,000. His words, not a metaphor. Then he did something strange: he handed half of his own lecture to Dustin Moskovitz, co-founder of Facebook, whose entire job was to talk students out of starting companies. Dustin showed one table. Employee 100 at Dropbox with standard 10 basis points made $10 million, employee 250 at Facebook made $200 million, and employee 1,000 joining in 2009, when everyone said it was too late still made $20 million. Your own startup? Best case you build a $100 million company and keep 10% after dilution. $10 million, same as employee 1,000, minus your health. Dustin knew the price because he paid it: at 21 he was throwing his back out every 6 months from pure anxiety, always on call, unable to quit a founder who leaves wears the black eye for a decade. Then Altman twisted the lecture back with advice that cut against everything in the room. The best ideas look terrible at the start: the 13th search engine, the 10th social network limited to college kids, sleeping on strangers' couches. If an idea sounds good, too many people are already building it. Make something 100 people love instead of something 10,000 people like. Ben Silbermann recruited Pinterest's first users by walking up to strangers in Palo Alto coffee shops, then resetting every browser in the Apple Store to Pinterest's homepage until they threw him out. And the only valid reason to start is that you can't not do it. Dustin built Asana at night, after full days at Facebook, unpaid and unasked. "The idea was beating itself out of our chest." The rest is a number between 0 and 10,000.

• 
  Mayank Vora (@aiwithmayank) reported 22 minutes ago

  In 2010, a developer decided your files should live on your computer, not Dropbox’s servers. So he built ownCloud. It gives you your own private cloud using a spare laptop, home server, or cheap VPS. His name is Frank Karlitschek. Install ownCloud on hardware you control, and you get file syncing, sharing, photo backup, calendars, and contacts through one dashboard. Your laptop and phone can access the same files just like Dropbox. The difference is where those files live. They stay on your server, under your rules. The project grew far beyond one developer’s experiment. CERN, universities, research institutions, and large organizations started using it to keep control of sensitive data. Then something unexpected happened. In 2016, Frank left the project he created and started Nextcloud with a new team. But ownCloud did not disappear. The project kept going, its source code remained public, and people continued running it on their own hardware. ownCloud has since gone through forks, an acquisition, and major rebuilds. Yet the original idea survived: Dropbox rents you space on its servers. ownCloud gives you the cloud itself.

• 
  Rashad Bayram (@bayrashad) reported 26 minutes ago

  Here's the stack I keep finding when I talk to tax firms: → Intake forms in JotForm or Google Forms → Signatures in DocuSign or PandaDoc → Reminders in Mailchimp, email, text messages → Document tracking in a Google Sheet, excel, crm → Client files scattered across email, Google Drive, dropbox, local hard drive Five tools, five logins, five places for something to fall through. None of them talk to each other, so the accountant becomes the integration. manually copying status from one to the next. It's not that any single tool is bad. It's that the seams between them are where the time goes. The fix isn't a sixth tool. It's removing four of them. How many tools are in your tax-season stack right now?

• 
  Sujay. (@Sujay__Raj) reported 27 minutes ago

  Here is what it breaks down: Local AI: Run Ollama, LM Studio, or LocalAI right on your machine instead of paying for ChatGPT. Cloud Storage: Replace Dropbox and Google Drive with Nextcloud or Syncthing so your files never leave your house. Network Privacy: Complete WireGuard and PiVPN setup guides for secure browsing. Private ***: Ditch GitHub and self-host your own repos using Gitea or GitLab.

• 
  mskah🔞 (@mskah_t) reported 28 minutes ago

  I got in touch with the system administrator, and they were able to resolve the issue. It turned out that the problem was caused by an update to the connected Dropbox account.

• 
  Ashutosh Rana ⛓️ (@ashutoshrana_20) reported 30 minutes ago

  Most developers think Rust 🦀became popular because of ownership and borrowing. That's only half the story. Companies aren't adopting Rust because they enjoy fighting the borrow checker. They're adopting it because they're tired of C++-level performance coming with C++-level disasters. Look at where Rust is running today: • Linux kernel components • Windows security systems • Android services • Cloudflare edge infrastructure • AWS Firecracker microVMs • TiKV and Materialize • Discord and Dropbox backend systems • Solana and Polkadot Notice what these systems have in common. They're expensive to get wrong. A memory bug in a toy project is annoying. A memory bug in an operating system, cloud platform, database, or blockchain can cost millions of dollars, create security vulnerabilities, or bring down critical infrastructure. That's why Rust keeps showing up in the same places: • Systems software • Networking • Databases • Cloud infrastructure • Developer tools • Blockchains Not because it's trendy. Because the cost of unsafe software keeps rising. For years, engineers accepted the tradeoff: Performance → use C++ Safety → sacrifice performance Rust challenged that assumption. The result? A growing number of teams no longer see memory safety as a nice-to-have. They see it as a requirement. The ecosystem is still maturing. But Rust isn't fighting for relevance anymore. It's becoming one of the default choices for software where performance, reliability, and security are non-negotiable.

• 
  Jack (@jackcoder0) reported 35 minutes ago

  1. Kill the Login Items the apps launching before you even sit down. Every time you log in, your Mac quietly launches 10-25 apps in the background. Spotify. Slack. Zoom. Google Drive. Dropbox. Creative Cloud. OneDrive. Each one consumes CPU and memory before you've opened a single window. System Settings → General → Login Items & Extensions. Review the list. Remove everything you don't need the instant you log in. You can always open them manually when you actually need them. His Mac had 19 login items. He needed 3. He removed 16. Boot time dropped from 2 minutes to 18 seconds. The first few minutes of every session — that sluggish, unresponsive window where nothing works gone.

• 
  Ricker (@0xRicker) reported 36 minutes ago

  Senior engineer just dropped a GPT-5.6 stress test after burning around $200K on API usage: 00:00 - $180K–$240K spent testing GPT-5.6 in Fast Mode 02:43 - The model using browsers, dashboards and settings like a remote operator 05:32 - 67 projects and 20+ hour autonomous sessions 07:07 - Lakebed, T3 Code and native app rewrites in 2–4 hours 15:08 - Rust compiler experiments, 18x speedup and a $91K Dropbox-style build 17:46 - GPT-5.6 fixing a broken Linux GRUB boot through KVM 22:56 - 3D games, weird assets and the remaining frontend taste problem It is a field test for agent loops The future edge is not the prompt It is the loop that can keep working after the prompt stops being useful

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

• 
  . (@Madame_Lucifur) reported 43 minutes ago

  There are some people who feel entitled to have my Dropbox and honestly I don't give a **** how you feel. If there's no transaction in my bank account which leaves your email address then that's not my problem.

• 
  Siddiqui Qamar ֎ (@siddqamar_ai) reported 44 minutes ago

  "it's just a wrapper" 😑 might be one of the laziest criticism in tech! users don't care whether you built the infrastructure. they care whether the product solves their problem. dropbox didn't invent storage. it made storage effortless. turns out making existing technology usable is a lot more valuable than many founders want to admit.

• 
  Karus Daedlyn *Cat Dad Era* (@CDaedlyn) reported 46 minutes ago

  @CantEverDie Keep making burner Gmail accounts and sign up for the free stuff. I jest, because that's terrible practice, although I did know an attorney IRL that would do that to daisy-chain those Dropbox sites. Infinite free storage, just in 2.5GB chunks.

• 
  Waldemar Santos (@wsantos99) reported 46 minutes ago

  @DropboxSupport Hello, I have already sent two emails regarding a problem I’m having with my account, but I haven’t received any response. How can I get assistance with this issue? Thank you.

• 
  Sunil Thakare 🇮🇳 🦀 (@thakares) reported 49 minutes ago

  @TLYShortener offering a genuinely useful, privacy-friendly app (no login, no ads) that seamlessly integrates with the company's core product (t_ly short links), is indeed a standard growth tactic seen in tools like Canva, Notion, or Dropbox. The QR app lowers barriers for users while creating natural upsell opportunities: frequent QR creators may later pay for t_ly analytics, custom domains, or branded links without feeling forced. Trade-off is transparent here; users get a solid free scanner but feed data into t_ly's ecosystem, which benefits the provider through increased link volume and potential premium conversions.

• 
  Chuck Thies (@ChuckThies) reported 50 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.

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 54 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.

• 
  hiverot (@amusudan) reported 55 minutes ago

  @cowboyshibuya Thanks for the reply! I'm not the most organised, and Ill usually just work on whatever is fun (Or a prerequisite for something that's fun to work on), but I do keep track of ideas, and create todo's and pipelines for things I am sure I want to add or test. For random ideas and todos I use a lot of lists (Dropbox paper, random text files, Notion, Notes app on my phone, Google Docs, etc). And for specific pipelines I use Google Sheets to keep track of what has been done per asset or map or gameplay mechanic (For example my guns spreadsheet has columns for animations, sounds, textures, etc). Big picture design and planning is all on paper in various notebooks and my Calendar app. I don't really track bugs now I just fix whatever pops up when playtesting.

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