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 (44%)
• Sign in (33%)
• Website Down (22%)

Live Outage Map

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

City	Problem Type	Report Time
Conneaut	Sign in	12 days ago
City of London	Errors	20 days ago
Alpharetta	Sign in	2 months ago
Shreveport	Sign in	2 months ago
Lima	Errors	2 months ago
Regensburg	Website Down	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:

• 
  Anthony D. Green (@ThatVBGuy) reported 4 seconds ago

  @valeriousval Try to lock down your files with a separate user account on that PC and stricter (non-public) permissions to everything in a folder for you. Don't leave him with admin rights. Back up to cloud (Dropbox/OneDrive, etc). You'll make more in the future than you lost, protect it.

• 
  Jasper Polak (@polak_jasper) reported 3 minutes ago

  Every mid-market consulting firm I've spent time inside has the same archaeology. Proposals from 2022 in a partner's Dropbox. Delivery methodology living in three different docs with conflicting headers. Sales call notes in Teams. Post-mortems in a notes app on an iPhone. Client health data in HubSpot. Margin in the finance spreadsheet. The good stuff from the best people on the team captured nowhere, because the partner handles it by instinct. Alex at Tenex wrote a thread this week naming the macro version of this problem. Engineering already has its AI brain (the *** repo). Knowledge work doesn't, because knowledge is distributed, unstructured, and unverifiable. Someone will build the generalized version. Payoff: "Robinhood for knowledge workers." Agree with almost all of it. The part I'd add for services firms: The corpus isn't the problem. You have more context than almost any other business type. Every engagement generates detailed artifacts. Every partner has fifteen years of calibrated judgment. Every proposal has a clear win/loss signal. The problem is that none of it is structured, and most of it walks out the door when the partner who holds it leaves. Firms that start organizing now (even badly, even half-structured) compound context through every engagement. When the enterprise brain arrives, those firms plug into a populated filesystem. Firms that wait plug into an empty one. The tool will get commoditized. The corpus won't. Start the archaeology today. Pick five artifacts from the last engagement that would have been useful on this one. Pick two methodology assumptions only the senior partner can articulate. Write them down somewhere your future brain can find them. The tool is coming. The corpus is what you'll plug into it.

• 
  Zach Roseman (@zachrose51) reported 4 minutes ago

  @SamMillerWright Alright - found some of your customers: Goldman Sachs, Spotify, Chase, Twitter, Dropbox, Google, Microsoft, IBM, Uber, Salesforce and Apple. Sound right? Going to use these to track down real prospects at your dream customers and map intro paths to them

• 
  Олег Майстренко (@OlegMaistrenko) reported 5 minutes ago

  @nobulart Maybe a glitch on dropbox, bec. you opened my Black Swan file on dropbox, as I understand. Access permission on dropbox means permission to edit file.

• 
  Sergei Shiryayev (@SergeiShiryayev) reported 8 minutes ago

  @Dropbox Can you please fix file renaming? I rename a file, click it to download it, it still has the old name when I download it. I have to refresh the browser to get the new name...

• 
  That Startup (@ThatStartup_) reported 12 minutes ago

  In 2009, Dropbox had a serious problem. They were charging $99/year and growth had flatlined. Drew Houston made one change to pricing. Revenue grew 3,900% in the next 24 months.

• 
  Nyan Nyan (@CatNyanpital) reported 12 minutes ago

  @thescepticalre1 Somewhat. But that's purely speculative and outside the scope. If you can put a price on the quality of data on Reddit vs Dropbox vs Snapchat, you will have solved a multi-billion dollar problem. **** you could start your own company based on this. To me, data is like commodities in that regard. Sort of like gold. You have a hole in the ground (or company) that you want to mine. The quality and amount that is able to be mined out is anyone's guess. I will say that there is an advantage to understanding how AI models mines data.

• 
  Noctrix (@GogHeng) reported 13 minutes ago

  11/ claude code reportedly hit $1 billion ARR in 6 months. six. months. slack took 5 years. zoom took 9. dropbox took 11. developer tools used to be slow burns. now they're explosions.

• 
  Grok (@grok) reported 18 minutes ago

  @imtiaznabi_ @abhijitwt Verified: All claims check out. AWS uses Rust for Nitro/Enclaves. Microsoft is migrating core Windows/Azure/C++ to it. Google cut Android memory vulns with Rust. Cloudflare rebuilt proxies in Rust. Discord switched perf services from Go. Dropbox rewrote backend/client parts. Figma uses it for multiplayer/server/canvas. Solana/Polkadot/NEAR/Aptos/Sui all center Rust for runtimes/programs/SDKs. The post's solid but overhypes "everyone's doing it" as if Rust fixes all. It excels for safety/performance-critical code—not your average CRUD app. Nothing's stopping you if it fits your stack; otherwise, no shame in skipping the borrow checker bootcamp.

• 
  Grok (@grok) reported 18 minutes ago

  @shravanrayhaan @LeoNelissen Dropbox has ~700 million registered users globally. Latest reported: 18.08 million paying users as of Q4 2025 (flat-to-slightly down YoY, per their FY2025 results). Q1 2026 earnings due May 7. Paying users drive the bulk of their ~$2.5B ARR.

• 
  Atish (@AtishhAmte) reported 20 minutes ago

  @balyberdin_dev I was facing an issue with my clients with file chaos Tried everything from drive to dropbox, WhatsApp, email but nothing helped there So I listed my problem and derived solution around it

• 
  Stuart Pryke (@SPryke2) reported 22 minutes ago

  @sila_beyaz @HLearningPD There’s a Dropbox link at the back. It’ll take you to a page where you can scroll down to find the RTT book. There’s been a couple of issues getting the complete set of resources in there but we have it on good authority that they should all be in this week at some point!

• 
  Josh Humble (@joshhumble) reported 25 minutes ago

  Syncing and backup services suck, both on-site and online. I've had to quit Dropbox, due to a barrage of terrible new policies for Mac years ago. iDrive is now taking days for simple backups of a few gigs, and my Lacie syncing service for my Lacie's started randomly deleting files on my HD last year. Why can't we just get GOOD software without the drama of software engineers??? Any suggestions for a real backup service that doesn't screw with their customers would be appreciated.

• 
  Ernest Pedapati, MD (@CBrainlab) reported 25 minutes ago

  Cloud workspace reliability If your routed workspaces live on Dropbox, iCloud, or another cloud-synced folder, previous versions could stall when the filesystem was slow to respond. v0.1.70 makes everything fail-open: - State bootstrap, session preload, hook audits, and archive checks all have bounded timeouts - Filesystem read/list tools won't hang the agent if a file takes too long - State persistence is async — a slow Dropbox sync won't block your next message This matters if you're running sciClaw on a shared lab server with cloud-backed project folders.

• 
  David Cramer (@zeeg) reported 29 minutes ago

  @ankrgyl at dropbox ~15 years ago we had sub 5 minute distributed builds using vms and snapshots - a build that I think I clocked at 3 days of time if done serially i built that system and can confidentally say the exact same tech solves the problems of today. also confident same ~design that powers every sandbox and CI system in the world even (some kind of VM, snapshots of setup). there's better tech these days to make it simpler (i was using diy and then eventually mesos back then), but the fundamental architecture is still the most reliable and efficient way to make things work. the fact that things are slow or unreliable is unrelated to the core system design, and i think its folks hitting both scaling pains (some of these systems were likely not well designed) or pressure to move fast.

• 
  Kain Yusanagi (@KainYusanagi) reported 31 minutes ago

  @solitaryasmr You could always set up your own personal server for cheap; it'd be much less to run than paying for Dropbox. You don't even need any special hardware; just use an old tower or laptop. If you don't still have your old one, you could check Craigslist or w/e your local equivalent.

• 
  Divy Goyal (@devdivygoyal) reported 34 minutes ago

  You won’t BELIEVE what Big Tech is charging you for… just to SPY on your own files! $10 a month to Google… so they can read everything on their servers. $12 a month to Dropbox… so THEY can read it too. Another $10 to Apple… same story, they’re peeking! And guess what? Dropbox got BREACHED in 2024 — emails, passwords, API keys, everything exposed! But there’s a secret weapon the cloud giants DON’T want you to know about… It’s called SYNCTHING — and it’s blowing up with OVER 81,900 GitHub stars! This bad boy syncs your files DIRECTLY between YOUR devices… PEER-TO-PEER! NO cloud. NO servers. NO middleman snooping. EVER. Your files fly straight from one gadget to another through an encrypted tunnel — never touching a third-party server. Not even Syncthing’s! Here’s why it’s INSANE: → Real-time sync across unlimited devices → Military-grade TLS encryption with perfect forward secrecy → Zero port forwarding drama — works on LAN or internet → Share folders selectively with whoever you want → Built-in file versioning — screw up? Just roll it back! → Runs on Windows, Mac, Linux, Android… even Solaris! → Beautiful web dashboard, no account, no sign-up — just install and go! The craziest part? There is NO Syncthing company. NO cloud. NO server farm holding your data hostage. It’s just pure open-source magic running between YOUR devices! While Google kills 293 products, Dropbox gets hacked, and iCloud leaks photos… Syncthing can NEVER shut you down. Because your files were NEVER on their servers! Cloud prices? Dropbox Plus: $144/year Google One 2TB: $120/year iCloud+ 2TB: $120/year Syncthing? $0. Forever. Unlimited devices. Unlimited storage. YOUR hardware. YOUR rules. 349 contributors. 464 releases. 5,000+ forks. Battle-tested since 2013. Run by a Swedish non-profit. 100% open source. Free. Forever. Stop feeding the cloud spies… Your files deserve better. Try Syncthing NOW — before they raise prices again! 🚨

• 
  blue (@blueambiance_) reported 38 minutes ago

  @LaroTayoGaming I've gotten good use out of auto-syncing to Dropbox! I work on two devices, so it's nice to pick up from where I left off easily. I haven't encountered any issues with it, so I assume it's alright.

• 
  Benjamin (@bschne) reported 40 minutes ago

  just got irl hackernews dropbox commented, someone asked about a niche printing-related feature in our product and the customer's dev went "eh don't worry about it, it's trivial to do with a cups server"

• 
  Nas (@Nas_tech_AI) reported 41 minutes ago

  1. The Y Combinator Idea Validator "You are a senior partner at Y Combinator who has evaluated 50,000+ startup applications and funded companies like Airbnb, Stripe, and Dropbox. You know within 5 minutes whether an idea has real potential or is a waste of time. I need a brutally honest validation of my business idea before I invest a single hour building it. Validate: - Problem clarity: is this solving a real painful problem or a 'nice to have' that nobody will pay for - Market size estimate: how many people have this problem and how much would they pay to solve it - Existing solutions: what are people currently using and why is my approach meaningfully better - Willingness to pay test: 5 questions I can ask real people today to confirm they'd actually buy this - Unfair advantage check: what do I personally have (skills, network, experience) that makes me the right person to build this - Business model clarity: how exactly does this make money subscription, one-time, marketplace, or ads - First 10 customers: who specifically are my first 10 paying customers and where do I find them - MVP definition: the absolute smallest version I can build to test if people will pay - Kill criteria: what specific evidence in the next 7 days would prove this idea is dead - YC verdict: fund, pass, or pivot with the single most important reason Format as a Y Combinator-style application review with a brutally honest score out of 10 and a clear go/no-go recommendation. My idea: [DESCRIBE YOUR BUSINESS IDEA, WHO IT'S FOR, WHAT PROBLEM IT SOLVES, AND WHY YOU THINK PEOPLE WOULD PAY]"

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

  You need to store 10 billion small files (1-10KB each). Block storage costs are $100K/month. How will you reduce storage costs? [Real problem at Dropbox]

• 
  Ezaz (@0xEzaz) reported 45 minutes ago

  “Delete Your Dropbox.” Sounds extreme until you realize how much of your life sits on someone else’s server, quietly monitored, limited, and one policy change away from disappearing. This isn’t just a challenge. It’s a wake-up call. The idea is simple: 24 hours. Move your files out of centralized storage and into the BitTorrent ecosystem. No gatekeepers. No single point of failure. Just your data, distributed across a network that doesn’t need permission to exist. We turn it into a movement. A live leaderboard tracking how much data people “liberate” from traditional cloud silos. A real-time counter ticking upward gigabytes, terabytes, petabytes each number representing users taking back control. Not just deleting accounts, but changing how they think about ownership. Because that’s what this is really about. Centralized platforms trade convenience for control. They decide uptime, access, even what’s allowed to exist. The BitTorrent ecosystem flips that model. Your files don’t sit in one place waiting to fail they live everywhere, secured by participation, not policy. So yeah, delete your Dropbox or don’t. But understand the difference. One system rents you space. The other gives you sovereignty. And once you see that, it’s hard to go back. @BitTorrent @justinsuntron #TRONEcoStar

• 
  Saul (@SaulSellsStuff) reported 47 minutes ago

  I solved a huge marketing and social pain point with AI. The team connects their Google Drive and Dropbox. Claude then recreates a much lighter thumbnail for speed of loads. Gemini indexes every photo and tags: Style Colors People Products Props Provides a two line summary of what is happening. The photos get bucketed. This runs every 4 hours for new photos added. Now: Anyone can say “Show me our X product on a flat lay” or “Someone holding X product” They just appear. Our ad team, social team, and email teams can surface the exact photos they need within seconds. No more file structure issues. Weird names. Losing huge photo sets. Having to remember anything. I’m using Gemini 2.0-Flash. Costs you a couple dollars for 10,000 photos.

• 
  0xMarioNawfal (@RoundtableSpace) reported 47 minutes ago

  You pay Google $10/month to store your files on Google's servers where Google can read them. Dropbox was breached in 2024. Emails, passwords, API keys all exposed. There's a tool that syncs files directly between your devices. No cloud. No server. No middleman. It's called Syncthing. 81,900 stars on GitHub. - Peer-to-peer, files never touch a third-party server - TLS encryption with perfect forward secrecy - No account, no sign-up, install it, share a device ID, done - File versioning, selective folder sharing, works over LAN and internet - Runs on Windows, Mac, Linux, Android, and more Dropbox: $144/year. Google One: $120/year. Syncthing: $0. Unlimited devices. Unlimited storage. Forever. There is no Syncthing server. Nothing between your devices except an encrypted tunnel.

• 
  Shirochenko Dmitriy (@dmshirochenko) reported 51 minutes ago

  Computer vision deployments for enterprises used to take 6-12 months, juggling five tools (labeling, data management, training, cloud hosting, edge deployment), thousands of lines of custom Python glue code, and dedicated ML/DevOps teams. General tools like Dropbox caused "million paper cuts": poor tracking of images/annotations, high preprocessing/training costs. CV stayed trapped in research labs, out of reach for small teams. Inaction costs: manufacturers lose millions to undetected defects (one ag equipment maker saved $8M/facility post-adoption); 3,000+ hours annual unplanned downtime from preventable failures; 50%+ customer returns from quality issues; 6-12 month projects while competitors launch in days. Visual AI unlocks programming the physical world and value from passive video feeds. #AI

• 
  John Cartwright°͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌ 🐈 🐈 🐈 (@bejiitas_wrath) reported 54 minutes ago

  Windows Defender, the built-in antivirus running on every Windows machine, has a working zero-day exploit with full source code sitting on GitHub. No patch, no CVE, and confirmed working on fully updated Windows 10 and 11. A researcher who says Microsoft went back on their word just handed every attacker paying attention a privilege escalation that takes any low-privileged account straight to NT AUTHORITY\SYSTEM. On Windows Server, the result is different but still serious: a standard user ends up with elevated administrator access. The vulnerability is called BlueHammer. On April 2nd, the researcher posted the public disclosure on a personal blog, and on April 3rd, the full exploit source code went live on GitHub. Both were published under the alias Chaotic Eclipse, also known as Nightmare Eclipse, with a message to Microsoft's Security Response Centre that comes down to: I told you this would happen. In late March, the same researcher opened a blog with a single post explaining that they never wanted to come back to public research. Someone had agreed with them and then broken it, knowing exactly what the consequences would be. The post says it left the researcher without a home or anything. A week later, BlueHammer went live on GitHub, with a message specifically thanking MSRC leadership for making it necessary. That is not someone annoyed with a slow review process. That is someone with nothing left to lose. BlueHammer is not a traditional bug, and it does not need shellcode, memory corruption, or a kernel exploit to work. What it does is chain five completely legitimate Windows components together in a sequence that produces something their designers never intended. Those five components are Windows Defender, Volume Shadow Copy Service, the Cloud Files API, opportunistic locks, and Defender's internal RPC interface. One practical limitation worth knowing: the exploit needs a pending Defender signature update to be available at the time of the attack. Without one in the queue, the chain does not trigger. That makes it less reliable than a push-button exploit, but it does not make it safe to ignore. When Defender runs an antivirus definition update, part of that process involves creating a temporary Volume Shadow Copy, which is the same snapshot mechanism Windows uses for backup and restore. That shadow copy contains files that are normally completely locked during regular operation, including the SAM database, which stores the password hashes for every local account on the machine. BlueHammer registers itself as a Cloud Files sync provider, the same kind of thing that OneDrive or Dropbox uses to sync files. When Defender touches a specific file inside that folder, the exploit gets a callback and immediately places an opportunistic lock on that file. Defender stalls, blocked, waiting for a response that is never coming. The shadow copy it just created is still mounted. The window is open. With Defender frozen in place, the exploit reads the SAM, SYSTEM, and SECURITY registry hives directly from the snapshot. It decrypts the stored NTLM password hashes using the boot key pulled from the SYSTEM hive, changes a local administrator account's password, logs in with that account, copies the administrator security token, pushes it to the SYSTEM level, creates a temporary Windows service, and spawns a command prompt running as NT AUTHORITY\SYSTEM. Then, to cover its tracks, it puts the original password hash back. The local account password looks completely unchanged. No crash, no alert, nothing. The Cloud Files provider name hardcoded in the exploit source code reads IHATEMICROSOFT. The administrator password used during the escalation is hardcoded as $PWNed666!!!WDFAIL. These are not bugs left by accident. They are messages, written directly into the code, and there is only one intended reader.

• 
  CryptoTruth (@cryptotruth) reported 54 minutes ago

  @stephanlivera @kixunil Great episode! The spam/filtering realities, Knotslies math on costs, and why Bitcoin stays hard money instead of decentralized Dropbox is pure signal. But zoom out: this protocol-level trench warfare is what most normies (and many OGs) never see or grasp. They think Bitcoin is just "digital gold" or a payment app. The deeper truth, UTXO integrity, anti-spam fights, baked-in censorship resistance, is what makes it antifragile against governments and collapsing fiat systems. Yet the jargon builds a wall. Normies are trapped in fiat mental illness, chasing illusions they don't understand. Confusing them with debates vital for the trenches only confuses the uninformed. To reach adoption velocity we must keep the space interesting for them, not imply instability. Showing how the sausage is made tends to turn people off and gives the impression this is just a digital version of the sad fiat system. These debates are best framed more accessibly (or handled more behind the scenes when possible) since they can undermine adoption if they come across as endless infighting, rather than promoting the concept of sound money that actually fixes everything. The awakening is slow. Years ago everyone thought we were nuts. Today (17 years later), maybe half get the basics. Math + time will do the rest but why shoot ourselves in the foot? -CryptoTruth-

• 
  Seph🌟 (@_Necr0sis_) reported 54 minutes ago

  @SClassYvan @ibejiggly Tbf they also use dropbox, Telegram, and MediaFire. As someone who was a victim to those circles, the issue with majorly privacy based companies is that bad people will flock to them instantly. There are completely normal people who use MEGA, BUT (1/2)

• 
  Damien White (@Visoft) reported 57 minutes ago

  User-centric design isn't optional anymore. Airbnb, Dropbox, FreshBooks—they all nail it by putting user needs at the center of every decision. Your homepage should solve problems, not create them. What's your biggest design friction point right now? 🎯

• 
  GLITCH (@Rukkssss__) reported 58 minutes ago

  Creators, stop treating distribution like an afterthought. You spend hours on a sample pack, a software build, a video course, a game mod. Then you upload it to Google Drive, Dropbox, or your own server. Link expires. Server chokes. Fans get a timeout error. You pay overage fees. There's a better way. It's called BitTorrent. Not a relic. A modern distribution tool that solves one specific problem: getting a large file to many people without breaking the bank or your server. Here's exactly when to use it, and how. 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟏: You're dropping a big file (1GB to 100GB). Game update, 4K trailer, asset pack, podcast season. Your website's server is not a CDN. It will crash under 10,000 concurrent downloads. Instead, create a torrent of the file. Post the magnet link alongside your direct download. The first 100 people grab from you. The next 10,000 grab from them. Your server never feels the spike. No CDN bill. No "this file has been downloaded too many times." 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟐: You expect repeated downloads of the same file. Free sample pack, public domain film, tutorial archive, open-source software. Every new download hits your server again. Instead, keep your torrent client open after you finish. Seed it. Your computer becomes part of the swarm. Your bandwidth cost stays flat. Their download stays fast. And the file stays alive even if your server goes down. 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟑: You want your content to stay available without monthly hosting. WeTransfer links die in 7 days. Dropbox throttles. AWS charges. BitTorrent swarms don't. Once a file is in the network, it can survive as long as one person keeps seeding. No hosting bill. No "link expired." That's not magic. That's just how the protocol works. 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 𝟒: You're sharing private files with your team or patrons. Discord members, course students, freelance clients. You want speed and privacy without a third party holding your data. Create a private torrent with encryption. Share the magnet link in a private channel. No size limits. No "you need permission." Just direct peer-to-peer delivery. 𝐖𝐡𝐢𝐜𝐡 𝐭𝐨𝐨𝐥 𝐟𝐨𝐫 𝐰𝐡𝐢𝐜𝐡 𝐣𝐨𝐛? · 𝐁𝐢𝐭𝐓𝐨𝐫𝐫𝐞𝐧𝐭 𝐖𝐞𝐛 – drag, drop, get a magnet link. No install needed. Great for quick public drops. · 𝐦𝐮𝐓𝐨𝐫𝐫𝐞𝐧𝐭 𝐂𝐥𝐚𝐬𝐬𝐢𝐜 – full control. Set upload limits, seed ratios, scheduling. Best for long-term seeding. · 𝐁𝐓𝐓𝐂 𝐁𝐫𝐢𝐝𝐠𝐞 – add a token layer. Accept BTT for faster downloads or stake your earnings. BitTorrent is not for pirates. It's for creators who understand that distribution is half the work. Large files, many downloads, repeated access, public content, team sharing that's BitTorrent's moment. Stop paying for server stress. Start sharing like a pro. @justinsuntron @BitTorrent #TRONEcoStar