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.

• Sign in (57%)
• Errors (43%)

Live Outage Map

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

City	Problem Type	Report Time
Salt Lake City	Sign in	2 days ago
Madrid	Errors	17 days ago
Conneaut	Sign in	1 month ago
City of London	Errors	1 month ago
Alpharetta	Sign in	2 months ago
Shreveport	Sign in	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:

• 
  sophie's dad (@sofia_karina) reported 6 minutes ago

  @SharonElizaDC @FedExHelp who goes to a dropbox?? just wave down a truck ffs

• 
  Lagoon Labs (@LagoonLabsMv) reported 7 minutes ago

  Dropbox is doubling down on virtual-first while everyone else pushes return to office - their people chief says hybrid is the worst of all worlds.

• 
  Sea (@norfaerie) reported 8 minutes ago

  I just gave myself a five hour anxiety attack by trying to move all of my backups of pictures from Google to Dropbox and then running out of space on Dropbox and not being able to increase my storage because Google Play is broken on my laptop 🫠

• 
  Joachim Voth (@joachim_voth) reported 8 minutes ago

  @DropboxSupport u will just tell me its my problem, i should reinstall - which i did N times. selective sync is totally broken. i select 8 folders and u r on "syncing 450,000 files! 125 days to go!" how stupid does it get?

• 
  frank goertzen (@frankgoertzen) reported 10 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 😜

• 
  timbidefi (@timbidefi) reported 14 minutes ago

  You are being watched right now and you're paying for it, privacy isn't a feature, it's a decision you make. Google stores your emails, Apple logs your location, Dropbox reads your files. Every cloud service you pay for is a deal you didn't fully read, with a company whose interests are not yours. He read it, built this instead: Custom rack server in his home, fully self-hosted, zero third party access, every byte of data sitting on hardware he physically owns. Email, storage, VPN, everything, running on his infrastructure, under his rules. Nobody can sell it, subpoena it, or lose it in a breach he had no control over. It cost him a weekend to build and less than $300 to run per year. Your data is somewhere right now, the only question is whose terms it's living under.

• 
  Invest Lens (@AIadventure3) reported 15 minutes ago

  @gabrielchua On the outlook email plugin, when you draft replies the formatting is very bad. Is there a fix coming for this? Also, please add Dropbox and Asana plugins.

• 
  John Cartwright°͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌͌ 🐈 🐈 🐈 (@bejiitas_wrath) reported 17 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.

• 
  Jasper Polak (@polak_jasper) reported 18 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.

• 
  The Insight Brief (@SimpleTech247) reported 18 minutes ago

  You pay Google $10/month to store your files. On Google's servers. Where Google can read them. You pay Dropbox $12/month. On Dropbox's servers. Where Dropbox can read them. You pay Apple $10/month. On Apple's servers. Where Apple can read them. Dropbox was breached in 2024. User emails, hashed passwords, API keys, and OAuth tokens were exposed. There is a tool that syncs your files directly between your own devices. No cloud. No server. No middleman. Ever. It's called Syncthing. 81,900+ stars on GitHub. Your files go directly from one device to another. Peer-to-peer. They never touch a third-party server. Not even Syncthing's. Here's what it does: → Syncs files between any number of devices in real-time. → Peer-to-peer. No central server. Your files go directly between YOUR devices. → TLS encryption with perfect forward secrecy on every connection. → Every device authenticated with a strong cryptographic certificate. → Works over LAN and internet. No port forwarding needed. → Selective folder sharing. Sync different folders with different people. → File versioning. Deleted or changed something? Roll it back. → Runs on Windows, Mac, Linux, Android, FreeBSD, Solaris, and more. → Web dashboard to monitor everything from your browser. → No account. No sign-up. Install it. Share a device ID. Done. Here's the wildest part: There is no Syncthing server. There is no Syncthing cloud. There is no company storing your data. The protocol is open and documented. There is nothing between your devices except an encrypted tunnel. Google has shut down 293 products. Dropbox has been breached. iCloud photos have leaked. Every cloud service is one policy change away from scanning everything you store. Syncthing can never shut down your files. Because your files were never on their servers. Dropbox Plus: $12/month. $144/year. Google One 2TB: $10/month. $120/year. iCloud+ 2TB: $10/month. $120/year. Syncthing: $0. Unlimited devices. Unlimited storage. Your hardware. Your files. Forever. 349 contributors. 464 releases. 5,000+ forks. Battle-tested since 2013. Run by the Syncthing Foundation. A Swedish non-profit. MPL-2.0 licensed. Open protocol. Peer-to-peer. Free forever. 100% Open Source.

• 
  Aakash Gupta (@aakashgupta) reported 23 minutes ago

  In April 2024, Dropbox disclosed that one compromised service account had given an attacker access to every active Dropbox Sign user's email, phone number, hashed password, API keys, OAuth tokens, and MFA data. Plus the names of everyone who had ever signed a document through the platform without even making an account. Syncthing has been around since 2013 and that breach is structurally impossible against it. 82,000 GitHub stars. MPL-2.0 license. Maintained by a Swedish non-profit foundation. Written in Go. The architecture is the whole product. Every device gets a cryptographic certificate. Traffic is TLS-encrypted end to end. Files move directly between machines you own through the Block Exchange Protocol. No central server gets compromised because no central server exists. Turn off the optional discovery and relay services and Syncthing has zero connection to anyone else's infrastructure. The reason cloud sync keeps producing breaches like the one above is structural. Centralized storage requires a single high-value target. The property that lets you log into Dropbox from a hotel computer is the same property that exposed every user when one service account fell. The convenience and the vulnerability are the same feature. Syncthing trades that property away. The cost is real. Both devices need to be online for sync to happen. There's no web UI you can hit from a borrowed laptop. No shareable link to text a friend. For most people that's a dealbreaker, which is why most people have never heard of Syncthing despite 13 years of open development. For files you actually care about, understand what the $120/year subscription is paying for. Storage at scale is close to free. The price covers an account, a server, a database, and a team that has to keep all three secure forever. The same surface area that made the 2024 breach possible. Dropbox can read your files. So can Google. So can Apple. Their architecture requires it. Syncthing literally cannot. Its architecture forbids it.

• 
  Nil (@Nil053) reported 23 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).

• 
  Neural Insights (@neural_insights) reported 24 minutes ago

  Netflix, Google, Anthropic, Meta, xAI, Perplexity, DeepSeek, Instagram, Spotify, Dropbox, Reddit, Pinterest, Uber, Airbnb, Quora all use Python. But sure—Python is “too slow” for your project.

• 
  Joseph Jude (@jjude) reported 24 minutes ago

  @tarungangwani @signulll Why would you say dropbox lost PMF? Is it because other tools have captured the market or the problem itself is not significant any more

• 
  Rashford Eyo of Jeje Group (@rashfordeyo) reported 24 minutes ago

  2. Solve a problem that hurts. Dropbox got its first 5,000 users from a simple demo video. They didn’t have a following, just a pain point worth talking about.

• 
  Mutt (@MuttMetaX) reported 27 minutes ago

  Let me break this down. An AI just launched that replaces every marketing job. Not some. All of them. SEO. Social media. Content. Ads. Branding. Pitch decks. Community management. Reddit posts. Email campaigns. Everything. A marketing team costs $200K–$500K a year. Agencies charge $10K–$20K a month. Freelancers $5K per project. This AI does all of it—for almost nothing. Backed by General Catalyst, Jeffrey Katzenberg, and execs from Dropbox, Stripe, Google. $7.5M in funding. Thousands already using it. It has an API. Other AI agents feed it work automatically. Copy is written, assets designed, posts scheduled, campaigns optimized. No humans required. A full marketing department, end to end. Automated. A week ago AI replaced coders. Then writers. Customer service. Now marketing. All at once. With one launch. Every week another AI drops. Another career becomes a subscription. And it’s not slowing. It’s accelerating.

• 
  The New Release Guy (@moviesplusgames) reported 32 minutes ago

  @Dropbox And fix your passkey verification flow. The code you send doesn't even work no matter how many times you type it in or copy and paste it. The government needs to start telling these apps to get better. They suck like most things in this **** country, ever since Dems ****** it

• 
  Adel Bucetta (@adelbucetta) reported 32 minutes ago

  @heynavtoor most people just upload to google drive or dropbox, but nobody's talking about how terrible their video quality is afterwards

• 
  Red (@rubelr44) reported 33 minutes ago

  you're paying google $10/month to sit in their server room. dropbox gets $12/month. apple gets $10. the kicker? they can all see your stuff. and when dropbox got breached in 2024? emails, passwords, and tokens were just... out there. there’s this tool called syncthing and it’s honestly kind of a cheat code. no cloud. no company servers. no middleman watching you. it just syncs your files directly between your own devices. peer-to-peer. it's got like 81k stars on github so it’s legit. here is why it wins: direct sync: files go from your phone to your pc. they never touch a 3rd party. privacy: encrypted with tls and crypto certificates. zero friction: no accounts. no sign-ups. just install it and share a device id. everywhere: works on windows, mac, linux, android... even solaris if you're into that. safety net: it has file versioning. if you accidentally delete something, you can just roll it back. the wildest part is that syncthing isn't even a company. it's a swedish non-profit. there is no "cloud" to shut down. google has killed 293 products, but they can't kill this because your files aren't on their hardware. the math is pretty dumb when you look at it: dropbox/google/icloud = $120-$144 a year. syncthing = $0. unlimited storage. unlimited devices. it's been around since 2013 and it's 100% open source. if you're tired of paying a subscription for "permission" to access your own data, just switch. your hardware. your files. forever.

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

  Super chad legendary interviwer at dropbox: 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]

• 
  𝕲𝖎𝖌 𝕯𝖎𝖌𝖌𝖊𝖗 (@Gig_Digger) reported 39 minutes ago

  @unusual_whales The problem is several years back when it started was peak Bidenflation era. It reset all prices higher, but thats also Biden should have never been put in office with dropbox stuffing.

• 
  Atish (@AtishhAmte) reported 40 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

• 
  The Bingus Man (@NotNordgaren) reported 42 minutes ago

  @Dropbox you guys wanna shut down the links I sent you that are hosting malware or are you gonna sit on it another week?

• 
  Multihopper (@Multihopper) reported 49 minutes ago

  @brycent Apple already has this in every phone and mac. Can't imagine that @Dropbox etc aren't going to hit this soon. It's a trivial problem to solve. Technically it's already solved even by YouTube.

• 
  The New Release Guy (@moviesplusgames) reported 53 minutes ago

  @Dropbox Maybe it is a skill issue, like ppl keep saying....bc they're WAY behind a company like X.

• 
  Luke (@lukecodez) reported 54 minutes ago

  PlayerZero just dropped their Engineering World Model and it's kinda insane $20M from matei zaharia (databricks), guillermo (vercel), dylan (figma), drew (dropbox) + Foundation Capital the problem: debugging is chaos because nobody has the full picture. support sees tickets, sre sees infra, devs see code. everything's fragmented. playerzero connects it all slack threads, PR reviews, CI/CD, observability, support tickets, incidents — into one context graph so when **** breaks you don't scramble. you just know. plus it learns from every incident. gets smarter about which code breaks, which configs are fragile, which changes affect what zuora, georgia-pacific, nylas → 90% faster bug resolution, catching 95% of issues before **** they guarantee 20% more engineering bandwidth in a week or they donate $10k to open source if you're sick of spending half your time hunting bugs instead of shipping, check this out

• 
  Grok (@grok) reported 54 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 55 minutes ago

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

• 
  Last Satoshi 🇨🇦 (@iamlastsatoshi) reported 55 minutes ago

  @chamath If the knowledge base or skills are in md file based. You can share this file using service like google drive, one drive, dropbox or any sync service. This way same file but shared between different agents. I have answered based on what you have jot down in your post without knowing the context.

• 
  Raziel (@tryraziel) reported 59 minutes ago

  Drew Houston was a college kid who kept forgetting his USB drive. Today Dropbox is worth $8B. Here's the brilliant strategy behind one of the most successful pivots in startup history. In 2007, Houston built a personal tool to sync files between computers. Simple problem, simple solution. But investors weren't buying it. Every VC said the same thing: "There are already 20 file storage companies. What makes you different?" Houston's breakthrough wasn't technical — it was psychological. Instead of building better storage, he realized people didn't want to think about storage at all. The magic wasn't in the cloud. It was in making the cloud invisible. The pivot: → Original idea: Online backup service (like everyone else) → New idea: Your files, everywhere, automatically → Key insight: Sync, don't store Houston spent months perfecting the demo video. No fancy features. Just a file appearing on multiple computers simultaneously. It looked like magic because it solved the real problem: friction. That video got 75,000 signups overnight. The lesson: Sometimes the billion-dollar idea isn't what you build — it's how you frame what already exists. Houston didn't invent cloud storage. He invented the feeling that your files just worked everywhere. What "obvious" problem in your daily life could be the next Dropbox?