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 (44%)
• Errors (44%)
• Website Down (11%)

Live Outage Map

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

City	Problem Type	Report Time
Paramaribo	Errors	2 days ago
Bogotá	Website Down	2 days ago
Auxerre	Errors	2 days ago
Salt Lake City	Sign in	5 days ago
Madrid	Errors	21 days ago
Conneaut	Sign in	1 month 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:

• 
  Ezaz (@0xEzaz) reported 3 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

• 
  Sean (@jishaochen89766) reported 4 minutes ago

  And finally, I find the problem is In the " Remotely Save " option, there is a set name "Change The Remote Base Directory) I need to find the name of the file folder in Dropbox, and fill it in this parameter... So everything is Light....Sync ....

• 
  Kuramichan (@Kuramichan7) reported 6 minutes ago

  Is dropbox not working for anyone atm? I was JUST uploading some files and now it won't let me anymore, it keeps ending in "upload failed". It won't even let me delete folders either, it just gets stuck on a stupid endless spinning wheel or whatever. ******* hate this **** man

• 
  Just Suzie Q suzieqwx@bsky.social (@Suzieq2021) reported 7 minutes ago

  @ZARA people beware of returning an order to their Dropbox in store. I returned an item on 28th March and still haven’t received payment back I’ve had to follow up and although I have an email to say that it’s been returned and refund would issue 9-11 days still nothing

• 
  Sukh Sroay (@sukh_saroy) reported 9 minutes ago

  Dropbox stores your files on their servers. Google Drive scans your content. iCloud locks you into Apple's ecosystem. Syncthing does none of that. Your files sync directly between your devices -- peer-to-peer, end-to-end encrypted, no cloud, no company in the middle. It's called Syncthing -- a continuous file synchronization program that has been quietly running the background of the self-hosting, privacy-focused, and homelab community for over a decade. Here's how it actually works: → Install it on 2 or more devices -- Windows, macOS, Linux, BSD, Android, Raspberry Pi, anything that runs Go → Pair devices by scanning a QR code or exchanging a device ID → Pick folders to sync → That's it. Changes propagate automatically in real time Here's what makes it different from every cloud sync service: → Peer-to-peer -- your files never touch someone else's server. The only thing external servers do is help your devices find each other (discovery) and punch through NATs (relays) → End-to-end encrypted with TLS for every connection -- even the relay servers that help connect your devices can't read your data → No account, no subscription, no storage limits -- sync is limited only by the size of your own drives → Versioning built in -- trash, simple, staggered, or external versioning options to protect against accidental deletes or ransomware → Selective sync, ignore patterns, bandwidth limits, per-folder settings → Web GUI for managing everything, accessible from any browser on your network Here's the wildest part: Data loss protection is listed as the project's number one stated goal. Above security, above ease of use, above everything else. That's not a marketing claim. It's in the GOALS.md file at the root of the repository. 80.7K GitHub stars. 4.9K forks. 462 releases. 10+ years of continuous development. 100% open source. MPL-2.0 license. (link in the comments)

• 
  Frankly Frank (@NoFrankingWay) reported 10 minutes ago

  @ElSotong Little of each. I have: - 28 TB SSD RAID 5 - speed backup - 43 TB UNRAID with HDDs, 1024 Gb is SSD cache - everything BKUP - 12 TB HDD RAID 5 - file BKUP - iCloud - work file BKUP - DropBox Personal Photography BKUP - 250 TB server for Chia - a 2020 project gone defunct. So now I have hella storage

• 
  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.

• 
  Datos Drive (@DatosDrive) reported 13 minutes ago

  🔗 INTEGRATION ECOSYSTEM Already using other tools? No problem: • Import from Google Drive/Dropbox (one-click migration) • Connect to existing calendars • Sync with email clients • API for custom integrations • Webhook support for automation Bring your existing stack. We'll make it better.

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

• 
  Raziel (@tryraziel) reported 14 minutes ago

  Drew Houston was a 24-year-old MIT student who kept forgetting his USB drive. His solution? A file-syncing service called Dropbox. But here's what most people don't know about his fundraising journey: His first pitch deck was terrible. 15 slides of technical jargon about "synchronized file systems" and "delta encoding algorithms." VCs glazed over. The breakthrough came when he made a 3-minute demo video instead. No technical explanations. Just Houston using Dropbox like a normal person — dragging files, syncing across devices, sharing with friends. That video got him into Y Combinator in 2007. → Seed round: $1.2M led by Sequoia (2007) → Series A: $7.2M led by Accel (2008) → Series B: $25M led by Sequoia (2011) By 2018, Dropbox IPO'd at a $10B valuation. The lesson: Houston didn't pivot his product — he pivoted his pitch. He stopped explaining how it worked and started showing why people needed it. Sometimes the problem isn't your idea. It's how you're selling it. What's the simplest way you could demonstrate your product's value in under 3 minutes?

• 
  Raziel (@tryraziel) reported 16 minutes ago

  Drew Houston pitched Dropbox to 76 VCs in 2007. 75 said no. The rejections were brutal: → "Storage is a commodity" → "Microsoft will crush you" → "Why not just email files?" → "The market is too small" Houston was a 24-year-old MIT dropout with no enterprise sales experience. VCs couldn't see past the obvious: cloud storage already existed. But Houston understood something they missed. The problem wasn't storage — it was sync. He'd built the first version because he kept forgetting his USB drive. Every knowledge worker had the same pain: files scattered across devices, email attachments, version control chaos. The breakthrough came when Sequoia's Mike Moritz asked one question: "How big could this really get?" Houston's answer: "Every person, every file, every device." Dropbox launched in 2008 with a simple demo video. 75,000 signups overnight. Series A at $25M valuation. By 2018: IPO at $9B valuation. Today worth $8B+ with $2.5B annual revenue. The lesson: When 75 VCs say your market is too small, maybe you're seeing something they can't. What "obvious" idea do you think VCs are missing right now?

• 
  𝖆𝖍𝖒𝖎𝖗 (@calhalt98) reported 20 minutes ago

  @liabynight Lmk if you ever make a Dropbox, I’d be down to get it

• 
  Inzo Technologies (@InzoTechHQ) reported 21 minutes ago

  Where's your most sensitive data right now? A server? A laptop? Someone's personal Dropbox? An email from 2023? If you don't know where critical data lives, you can't protect it.

• 
  Mark Cuban (@mcuban) reported 23 minutes ago

  @pvpandroids Just like box and Dropbox and Google gave away free storage and uber sold rides at a loss. It’s a competitive issue to start. At some point they will.

• 
  neo_relic (@neo_relic123) reported 25 minutes ago

  @Ashleydoncare @rachallison1 ... IF A MAN LEAVES HIS CHILD AT A FIRE STATION OR HOSPITAL OR DROPBOX OR WHATEVER THEY WILL HUNT HIM DOWN!!! NOT THE SAME FOR WOMEN!!!! WAKE ******** UP!!!! 🤬🤬🤬🤬🤬🤬🤬

• 
  daniela molloy (@diandrasdiandra) reported 25 minutes ago

  coachella taking down the stream right when i'm at the start of it... okay *******. can someone send me like a link? a dropbox, a mega file, a drive, something?

• 
  Grok (@grok) reported 28 minutes ago

  @bad_alhaji @RoundtableSpace Yes, mostly true. Syncthing is real open-source P2P file sync (82k+ GitHub stars): files stay only on your devices, end-to-end encrypted, no central server or account. Free forever, unlimited storage/devices. Dropbox’s 2024 breach hit its Sign service (emails, hashed passwords, API keys exposed—not core file storage). Google One charges ~$10/mo for 2TB and can access/scan files per its policy. Syncthing is great for personal multi-device sync if you’re okay running it yourself.

• 
  “Ijebu Tax” (@OlalekanOR) reported 34 minutes ago

  @TaoFeek182 Tbh, I could not download it, the Dropbox was not working. I'd share with you once I get hold of it.

• 
  Mutt (@MuttMetaX) reported 36 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.

• 
  Lars Alister 💖🔜Anthrocon & Littles Jamboree 2026 (@Lars_Alister) reported 39 minutes ago

  Wait a ******* moment she sold the movies she was asked to take down on Dropbox? Without consent or knowledge of the other person? If a man had did that we would be having conversations about him being dangerous or a predator. About how he is a consent violator. So where is the accountability!!!

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

• 
  Jainam Parmar (@aiwithjainam) reported 42 minutes ago

  Fix 3: Turn on two-factor authentication on every important account Even if someone finds a password in your notes, 2FA stops them at the door. They need the password AND a code from your phone to get in. Set it up on: → Email (Gmail, Outlook, Yahoo) → Banking apps → Social media (Instagram, X, Facebook) → Cloud storage (iCloud, Google Drive, Dropbox) → Crypto exchanges Use an authenticator app (Google Authenticator, Authy) not SMS. Text codes can be intercepted through SIM swapping.

• 
  Mike Sawyer (@raftersranch17) reported 42 minutes ago

  @jenvanlaar @Hounsizzle It's valuable currency. The outer envelope is where you sign the affidavit. How would you catch a culprit ? That is the problem we face. Did you hear of anyone stuffing a Dropbox get prosecuted, despite the numerous videos catching them in the action?

• 
  blue (@blueambiance_) reported 45 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.

• 
  Stuart Pryke (@SPryke2) reported 49 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!

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

  A good system design interview question for a Senior/Staff Backend Engineer is: Design Dropbox. At first, Dropbox looks like a simple file upload and download system. User uploads a file, we store it, and later they can access it from another device. But the real complexity is not uploading one file. The real complexity is sync, conflict resolution, versioning, permissions, large file handling, offline changes, metadata consistency, deduplication, and making the system feel instant across laptops, phones, and web. I would start by breaking the system into two major parts: file content and file metadata. File content means the actual bytes of the file. Metadata means file name, folder path, owner, size, checksum, version, permissions, timestamps, and deleted/restored state. These two should not be stored together. File bytes should go to blob/object storage, while metadata should go to a database that supports fast lookups and strong correctness. For upload, the client should not send a large file as one big request. A 2GB video should not restart from zero because the Wi-Fi dropped at 95%. So we should split files into chunks, calculate checksum for each chunk, and upload chunks independently. Once all chunks are uploaded, the server creates a file version that points to those chunks. This gives us resumable uploads, retry safety, and better network usage. A very important optimization is deduplication. If 10,000 users upload the same popular PDF, we do not want to store 10,000 copies of the same bytes. We can hash file chunks and store only unique chunks. Metadata will point to the chunk list. This saves huge storage cost, but we must be careful with privacy and security. Dedup should happen in a controlled way, not leak whether another user already has a specific file. The metadata service becomes the source of truth. Every change like upload, rename, move, delete, restore, or share should create a new metadata version. This is important because Dropbox is not just storage, it is a timeline of changes. If the user deletes a file by mistake, we should be able to restore it. If two devices make changes offline, we should know exactly what changed and when. Sync is the heart of the system. Each client should maintain a local sync token. Whenever something changes, the server writes it into a change log. The client can ask, “give me all changes after token X.” This is much better than scanning every folder again and again. For near real-time sync, clients can use long polling, WebSockets, or push notifications to know when new changes are available. Conflict handling is where naive systems fail. Imagine a user edits the same file on laptop while offline, and also edits it from mobile. When both devices come online, which version wins? For normal files, the safest approach is to keep both versions and create a conflict copy. For collaborative documents, we need deeper merging logic, but for a Dropbox-like file system, versioning plus conflict copies is usually good enough. Permissions should be checked before every sensitive operation. Sharing a folder is not just adding one row in a table. If a folder has thousands of files, permission inheritance becomes tricky. We should model ownership, viewer/editor access, shared links, link expiry, team policies, and audit logs. Permission changes should be strongly consistent because users must trust that removing access actually removes access. Downloads should first go through metadata and permission checks. After that, the system can return a short-lived signed URL from blob storage or CDN. Public/shared files can be cached more aggressively. Private files need careful access control. Performance is important, but leaking private files for speed is not acceptable.

• 
  The New Release Guy (@moviesplusgames) reported 53 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

• 
  0xJansss (@jannnsssssss) reported 53 minutes ago

  Think about every file you've ever uploaded to Drive, Dropbox, or iCloud. Google can delete it. Anytime. No warning. Amazon's servers go down? Half the internet goes with it. You don't own your data. just rent it. We've been okay with this for 20 years. Walrus says: that's over.

• 
  Ezaz (@0xEzaz) reported 55 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

• 
  Rober (@robsoto1511) reported 57 minutes ago

  @MEGAprivacy would be nice if joplin could sync with mega or proton their options are onedrive dropbox and the joplin server