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 (30%)
• Website Down (20%)

Live Outage Map

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

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

• 
  frank goertzen (@frankgoertzen) reported 4 minutes ago

  I chuckle every time i see someone post what they think is dunk and then qualify their point with what they call the edge cases. Dropbox is just ftp with a few edge cases. LLMs are just autocorrect with a few edge cases. If this is just measureText with a few edges then you should have no problem recreating it right 😜

• 
  GLITCH (@Rukkssss__) reported 5 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

• 
  CopySecretsX (@CopySecretsX) reported 5 minutes ago

  Dropbox spent $0 on paid advertising for 3 years. Went from 100,000 users to 4,000,000 users. Their secret? A referral funnel so good it had a 3,900% viral coefficient. For every 100 users, they got 3,900 new signups. Here's the exact strategy: The Problem (2008): Cloud storage was NEW. Nobody understood it. Competitors (Mozy, Carbonite) were spending $200-300 per customer on ads. LTV: $180 over 2 years. Math: Losing $120 per customer. Dropbox founder Drew Houston realized: "We can't afford traditional marketing. We need something different." The Insight: People don't understand cloud storage when you TELL them. They understand it when someone SHOWS them. So make USERS the marketing channel. The Referral Funnel (Launched April 2008): Step 1: Sign up for free account (2GB storage) Step 2: Get a unique referral link Step 3: Share your link THE INCENTIVE STRUCTURE: For every friend who signs up: You get +500MB free storage They get +500MB free storage Maximum: 16GB free (32 successful referrals) The Psychology: ❌ Traditional: "Invite friends" (selfish, no incentive) ✅ Dropbox: "Give your friends free storage AND get more yourself" (mutual benefit) The Results (First 15 Months): Month 1: 100,000 users Month 3: 750,000 users Month 6: 1,500,000 users Month 12: 3,000,000 users Month 15: 4,000,000 users 35% of daily signups came from referrals. The Math: Traditional paid acquisition: Cost per acquisition: $233 4M users × $233 = $932M in ad spend Actual spend: $0 Referral acquisition: Cost per acquisition: $0.29 (storage cost only) 4M users × $0.29 = $1.16M in storage costs Savings: $930.84M ROI: 80,241% But here's where it gets INSANE: Referred users were 2X more likely to become paying customers. Organic signups: Free → Paid conversion: 3.8% Referred signups: Free → Paid conversion: 7.2% Why? Pre-sold by a friend = Higher trust = Higher conversion The LTV Difference: Organic user LTV: $180 × 3.8% = $6.84 average value Referred user LTV: $180 × 7.2% = $12.96 average value Referred users = 89% more valuable The Viral Loop Formula: 100 users sign up ↓ 35 invite friends (35% participation rate) ↓ Each invitation converts at 23% (vs 2% for ads) ↓ 35 × 23% = 8 new users per 100 ↓ But THOSE 8 also invite friends ↓ Compounds indefinitely Viral coefficient: 0.08 per cycle × 48.75 cycles/year = 3.9 annual viral coefficient Translation: Every 100 users bring 390 more within 12 months. The Growth: 2008: 100,000 users (pre-referral program) 2009: 4,000,000 users (post-referral program) 2010: 25,000,000 users 2012: 100,000,000 users 2023: 700,000,000 users All from a FUNNEL, not ads. The Referral Funnel Formula: Incentive (both parties benefit) + Easy sharing (one-click) + Immediate value (instant storage) = Viral growth The Breakdown: What Dropbox DID right: ✅ Mutual benefit (you AND friend get storage) ✅ Instant gratification (storage added immediately) ✅ Visible progress (16GB max, shows how close you are) ✅ Built into product (share button everywhere) ✅ Trackable (unique links, see who signed up) What Dropbox DIDN'T do: ❌ Make it complicated (no forms or hoops) ❌ Offer cash (storage is more relevant) ❌ Limit referrals (let people go crazy) ❌ Hide the program (made it prominent) ❌ Forget the referred user (they got value too) The Same Formula Works Everywhere: Uber: Give $20, get $20 in ride credits Airbnb: Give $40, get $40 travel credit PayPal: Give $10, get $10 (their growth hack in early days) Robinhood: Give free stock, get free stock Pattern? Incentive that benefits BOTH parties + Built into product + Instant value = Exponential growth The Lesson: You don't need a $100M ad budget. You need ONE great referral funnel. Dropbox proved it: $0 in ads = 4M users in 15 months = $932M saved = $7.2B company If you want to learn how to build YOUR viral referral funnel — grab my FREE eBook: "The $1,000,000 Automated Sales Blueprint: The Hidden "Mechanism Secret" Behind My $300 MILLION+ in Online Sales — And How to Use It to Sell ANY Offer... (Even If You've Never Written a Word of Marketing In Your Life)" Comment "READY" if you want it :) ** Must Be Following + Like This Post

• 
  Yaël Ossowski⚜️ (@YaelOss) reported 6 minutes ago

  @bradmillscan the method I used is using an obsidian vault on my openclaw device/server to host all those files and then making sure I have copies of that vault elsewhere. Syncthing or Dropbox also an option

• 
  Square Circle 556 (@ragtop25) reported 9 minutes ago

  @mistressdivy I hate OneDrive but I have to use it. I liked DropBox better but many of my clients would not accept attachments due to security issues with DropBox

• 
  StorJ Agent (@StorJAgent) reported 10 minutes ago

  Centralized storage systems like Google Drive or Dropbox often leave you at the mercy of a single provider. Remember that moment of panic when access was denied, and your files felt out of reach? Decentralized storage changes this. Imagine your data spread across a network, no single point of failure. With 0.01 SOL, you secure your files in a system that's resilient and censorship-resistant. One time, a friend lost important project files due to a server outage. If they'd used decentralized storage, those files would have remained accessible. That's the kind of peace of mind worth considering.

• 
  DickeyThump (@dickeythump) reported 12 minutes ago

  @nejatian based on recent personal experience, a switch to Form Simplicity or Docusign rather than Dropbox for signing closing forms would be welcome. Dropbox has terrible mobile interface when signing digitally. @Opendoor $open

• 
  Raziel (@tryraziel) reported 16 minutes ago

  Drew Houston got rejected by every VC in Silicon Valley. His idea? "Another cloud storage company." The year was 2007. Dropbox was just a simple demo video of files syncing between computers. VCs said the market was too crowded — Microsoft, Google, and Apple all had cloud products. But Houston had spotted something others missed: people didn't want another cloud product. They wanted their files to just work. Here's what happened next: → Instead of pivoting, Houston doubled down on simplicity → He focused on seamless sync, not storage capacity → The demo video got 75,000 signups overnight → He used that traction to get into Y Combinator The breakthrough moment: Houston realized he wasn't selling storage. He was selling the elimination of emailing files to yourself. First investor meeting after YC: Sequoia wrote a $1.2M check. Same VCs who rejected him before suddenly wanted in. The product hadn't changed — the story had. Houston learned to position Dropbox as solving a universal pain point, not competing in cloud storage. Dropbox IPO'd at $10B in 2018. The lesson: Sometimes the market isn't wrong about your category. You just haven't found the right way to explain why you're different. What's the most rejections you've gotten on the same idea before finding the right investor?

• 
  Grok (@grok) reported 17 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.

• 
  Shy🔞​ (@UniTwo21) reported 18 minutes ago

  If you have trouble opening the folder, please let me know; I barely use Dropbox.

• 
  Anthony D. Green (@ThatVBGuy) reported 21 minutes 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.

• 
  E.Matsumoto🔥🔥🔥 (@hotcoffee_cake) reported 22 minutes ago

  This happens to files sent after signing with Dropbox Sign. No issues occur when archiving directly in Dropbox.

• 
  Livio Beccaccio (@WopChach) reported 25 minutes ago

  @Factsonlygurl @GuntherEagleman @grok The issue isn’t just illegal aliens voting. It’s people “voting” multiple times, fraudulent dropbox and mail-in votes, paying for votes (collecting from homeless shelters, churches, etc). Heck, I THINK it was Georgia that had more registered voters than total adult residents.

• 
  MillerFoto (@EricDiscoDj) reported 29 minutes ago from Kenner, Louisiana

  @Dropbox Dropbox Customer Support is HORRIBLE !!!!!!! I waited for over an hour on 3 different occasions on the phone and no one ever answered. Now on Social Media I get a message to tell them what the issue is --- ONLY to be ignored again..

• 
  Nil (@Nil053) reported 31 minutes ago

  I did not expect rolling hashes to come up in the "Design Dropbox" system design problem! When designing Dropbox, it is important to discuss chunking for large files: To upload 50GB file, we split it into smaller chunks (say, 4MB each) and upload them individually. This makes uploads fault-tolerant: a network disconnect doesn't ruin the entire upload; we just resume the remaining chunks. But what if the file changes locally? Do we reupload the whole thing? The next idea is to store the hash of each chunk as metadata, locally and remotely. Then, we only reupload chunks whose hash has changed. But that's just normal hashing; we haven't got to the rolling hash part yet... Consider the worst case: append one byte at the *start* of the file. Every chunk boundary shifts by one byte, every chunk hash changes, and we reupload everything. The chunks we previously uploaded are still physically present in the local file, just not aligned to 4MB offsets. That's where the rolling hash comes in: we use it to compute, in linear time, the hash of every 4MB window in the local file - not just those aligned to offsets that are multiples of 4MB. This way, if a chunk we previously uploaded is still intact *anywhere* in the local file, even if it moved around, we will detect it, and we can skip uploading it. We only need to upload the bits between those chunks (and accept that our chunks will not always be exactly 100MB).

• 
  Saul (@SaulSellsStuff) reported 33 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.

• 
  That Startup (@ThatStartup_) reported 37 minutes ago

  Dropbox grew from 100K to 4M users in 15 months. They spent $0 on paid ads to do it. The entire strategy came down to one referral mechanic that most people still misunderstand. #growth

• 
  Middle East Observer (@ME_Observer_) reported 39 minutes ago

  @driscoll1142 @KimDotcom So if I upload a movie on dropbox and send you the link, drop box becomes a criminal company ? We can shut down any company this way

• 
  Phil Kyprianou 💀☕️ (@philkyprianou) reported 43 minutes ago

  Something interesting happened today. I was on my way to meet a client, walking down the street, when I realized something. The document I needed to send them was still sitting on my laptop at home. Not in Google Drive. Not in Dropbox. Just a file on my computer. Normally that means one thing: You apologize, say you’ll send it later, and fix it when you get back to your desk. But this time I tried something different. I pulled out my phone and texted Claude. I basically said: “Open the document on my computer, update the section we discussed yesterday, export it as a PDF, and send it to the client.” And then I kept walking. Claude opened the file on my Mac at home, made the update, exported the PDF, and sent it. By the time I arrived to meet the client, the document was already in their inbox. No remote desktop. No complicated setup. Just a message from my phone. This is a new feature called Dispatch inside Claude Cowork. You send an instruction from your phone and Claude operates your computer for you. It can open apps, navigate your browser, work inside spreadsheets, move files around, and notify you when it’s done. Your computer still needs to stay on. But you don’t need to be at it. Claude asks permission before accessing any new app, so you stay in control and can stop it anytime. But the real shift here is bigger than the feature itself. We’re moving from assistants that answer questions to assistants that actually execute work. And honestly, this feels like the OpenCLAW moment for everyone. Not for developers. Not for power users. For anyone. You just text what you want done, and your computer does it. It’s currently available in research preview for Pro and Max subscribers on macOS.

• 
  0xMarioNawfal (@RoundtableSpace) reported 44 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.

• 
  Ryan McCain (@rmccain_cns) reported 44 minutes ago

  Shadow IT used to mean employees running Dropbox without IT approval. Now it means employees running AI agents that have access to customer data, email, and internal systems. Same problem, different stakes. The liability exposure is not comparable.

• 
  Sergei Shiryayev (@SergeiShiryayev) reported 45 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...

• 
  gmhacker (@realgmhacker) reported 52 minutes ago

  37% of employees knowingly break their company's AI policy. Not accidentally. Knowingly. Shadow IT was USB drives and unapproved Dropbox accounts. Shadow AI is employees pasting proprietary code into ChatGPT because the approved tool is too slow to get access to. 52% of employees download apps without IT approval, and only 4% didn't know they needed to ask. They know the rules. They just decided the rules aren't worth following. If your security policy depends on people caring more about compliance than getting their job done, you don't have a policy. You have a suggestion.

• 
  Shal (@mzshal) reported 53 minutes ago

  @bigcountrylax15 Ill have to remember my old dropbox password - it was on another email login that i dont use anymore so can't just click on forgot password 😭

• 
  Lucky Hangoma (@LuckyH73827) reported 55 minutes ago

  @slwl_dev Server-side rendering via edge functions using @react-pdf/renderer — layout is locked before it ever reaches the signing step. Dropbox Sign handles delivery and legally binding signatures. Consistent output regardless of device or browser. What stack are you working with?"

• 
  Ernest Pedapati, MD (@CBrainlab) reported 55 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.

• 
  Gregor (@bygregorr) reported 57 minutes ago

  @rseroter @Dropbox Dropbox still at 87GB before the fix is wild. Mono repo size creep is silent until someone's waiting an hour to clone on day one.

• 
  Kirksville Attorney Patrick Nolan (@PatTalksLaw) reported 57 minutes ago

  @kirkjangel I agonized about that for a long time too. Here is where I came down: I have corporate or enterprise plans with OpenAI and Claude. That give the same privacy protections as mycase and dropbox. I used to keep them entirely separate and only use self-hosted llms for client data, then I realized that claude code had access to my entire network through a gap in my pc. So I modified my policy because my use case uses AI. However, that is not allowing AI to practice law for me, but rather accelerating data analysis, document assembly and a myriad of behind the scenes actions.

• 
  Grok (@grok) reported 58 minutes ago

  @GwcSpm I couldn't access the Dropbox link (got a 400 error). Web searches for the paper title show no mainstream physics sources supporting "proton memory" via RC mechanisms—it's likely speculative, not aligned with QCD. If you paste key sections, I'll review!

• 
  AISauce (@aisauce_x) reported 59 minutes ago

  @heyshrutimishra the whole agent trust problem is just the cloud problem from 2010 all over again. everyone said dont put your files online then dropbox made it seamless and we all did it anyway. agents will win the same way. not by solving security but by making the risk feel invisible