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 (38%)
• Website Down (13%)

Live Outage Map

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

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

• 
  ScarcityMan (@ScarcityMan) reported 1 minute ago

  @balkanhodl @hodlonaut Even worse than that. It's dropbox except every archival node runner is providing storage space for free, so like, dropbox where you host your data and pay for your own server...

• 
  YC Insights. (@Aiagent_s) reported 3 minutes ago

  He spent two years looking for a bigger problem. Found it on a Chinatown bus in January 2007 when he reached into his bag and realized he'd forgotten his USB drive. Again. He opened his laptop and started coding what would become Dropbox.

• 
  Adrien Matray (@AdrienMatray) reported 3 minutes ago

  The fix is simple: do not use one generic code/ folder for all long-lived branches. Use separate Dropbox folders whose names encode the intended branch: code_main/ code_experimentation_main/ code_experimentation_main_name1Sandbox/ code_experimentation_main_name2Sandbox/

• 
  lonesome cowgirl lex (@besosprincessa) reported 7 minutes ago

  Who is down to add to their Dropbox link? 👀👀👀 shoot me a message with your budget and want you wanna see!!

• 
  Isha (@VISportsTalk) reported 7 minutes ago

  @DropboxSupport Still not working

• 
  Blake Heron (@BlakeHer_on) reported 8 minutes ago

  @StartupArchive_ the dropbox and uber examples are the tell. scratch your own itch, ship the fix, discover a million people had the same itch.

• 
  Americanrambler (@Ameericanrambl1) reported 8 minutes ago

  The ******** at the corrupt American Fork Police Department forgot to set the dropbox to private, so they accidentally made all the unredacted videos public. Before they realized their errors, somebody downlaoded them. Here it is. American Fork PD Unredacted Body & Dashcam 6 3 26 220 PM : Free Download, Borrow, and Streaming : Internet Archive #recklessben #americanfork #bricksandminifigs

• 
  Lagoon Labs (@LagoonLabsMv) reported 15 minutes ago

  Dropbox founder Drew Houston is stepping down as CEO, moving to executive chairman. Stock dropped 2.3% on the news. His next move? He's eyeing the AI space - 'credit card alerts for my Cursor token spend.'

• 
  ray🥤 (@rayontrack) reported 19 minutes ago

  bookmarked, downloaded, screen recorded, emailed, stored in hard drive, uploaded to cloud, archived, backed up, shared via bluetooth, forwarded, copied to usb, saved offline, synced across devices, added to favourites, printed, password protected, compressed into zip, renamed, organised into folders, duplicated, exported, imported, attached to message, sent to recycle bin, restored from backup, converted to pdf, edited, highlighted, annotated, watermarked, uploaded to google drive, uploaded to dropbox, shared through airdrop, linked to notes, tagged, encrypted, burned to cd/dvd, cached, mirrored to another device, uploaded to server, queued for transfer, dragged into archive, pinned, added to reading list, stored on ssd, embedded in document, linked in spreadsheet, previewed, sent to printer queue, recovered from trash, and indexed for search.

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

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

• 
  fercaton (@fercaton) reported 23 minutes ago

  Writing things down isn't weak—it's like training wheels for your ideas. Your brain's not built to be an infinite Dropbox; it's for connecting dots, not hoarding them.

• 
  america is an embarrassment🖕🏻🧊 (@abadlittlevibe) reported 25 minutes ago

  @DaddyAndJaxson @kdriley05 Whelp you've got the Dropbox login...do what you need to do ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

• 
  Joo Tat (@heyyyjoo) reported 25 minutes ago

  @kozerafilip @joinsauna @newitemco Here’s my main first impression of Sauna: I don’t see a clear winning use case yet. At least from my perspective, Sauna currently feels like a broad AI layer on top of the apps you already use. It can suggest what to do, help find information, and has a multiplayer/collaboration angle around understanding what other people are doing. But I don’t yet see the specific use case where Sauna is clearly much better than existing alternatives. For an early product, I think it would be useful to have a sharper wedge: a specific group of people, in a specific situation, with a painful problem where existing solutions are poor, and where Sauna is obviously the better answer. Maybe that wedge already exists, but as an outsider looking at the website and demo, it is not immediately clear to me. This feels especially important because Sauna asks users to overcome a meaningful amount of friction and anxiety. To unlock the value, users may need to connect sensitive apps like email, Slack, and Notion. If the multiplayer value is important, they may also need to convince teammates to connect their own sensitive apps. That creates a big trust and coordination hurdle, so the value proposition needs to be extremely clear before people will make that jump. One analogy I think about is Notion. Notion is now a very broad horizontal product: people use it as a CRM, Jira alternative, team wiki, notes app, etc. But early on, I believe it had a much simpler starting point: document and knowledge organization. The product and communication was focused on a better way to store, structure, and share notes and docs compared to alternatives like Google Drive, Dropbox, or scattered documents. People could use it for their own notes and documents first. Then, when they eventually shared a page with colleagues, those colleagues could immediately see the value because the page was easy to navigate, clear, flexible, and beautiful. I wonder what the wedge could be for Sauna. I noticed that the Solutions page seems to heavily feature Sauna in Slack, as an assistant that has access to shared context. Is that something that has been resonating better with users? One possible wedge could be someone who is overwhelmed by Slack because they have too many messages and threads to respond to. They could drop their personal assistant into a channel to help reply on their behalf, using context shared with Sauna, and escalate when it is unable to answer confidently. That might also create an easier mental model around access: the personal assistant in Sauna has access to more private context, while the team-facing assistant in Slack has more limited, scoped access. From there, if colleagues see the assistant working and want their own, that could be a natural path into the multiplayer or “*** main branch” idea. Individual assistants could start to merge shared context and provide better help, suggestions, and coordination over time. I’m not sure if this is the right wedge. The answer may already be visible in the product’s usage patterns: who is sticky, what they are using Sauna for, and where they are getting repeated value. But I think the key question is: what is the specific initial use case where Sauna is not just useful, but dramatically better than the alternatives? Once that is clear, I think the product / website / demo should make that use case extremely obvious to the users who need it. (Btw I'm speaking with Ryan tmr regarding the PM role. Which was what led me to explore Sauna as part of my own research. Thought I might as well share my first impressions here)

• 
  bayleigh | HEARD BABYLON 💙 (@eternalwarnings) reported 30 minutes ago

  sorry it's boofed quality my Dropbox account was not working so I had to ss for the time being

• 
  🎀MONA MANIC🧸 (@mona_maniccc) reported 35 minutes ago

  My new Dropbox link is out 1 terabyte dm if you are down 💞

• 
  Bosn (@00bosn00) reported 37 minutes ago

  2026 and we’re out here building god-tier AI that can debate physics and write symphonies, but Grok still can’t watch a Dropbox, OneDrive, or Discord video link.“Sorry, I can’t watch videos from Dropbox, OneDrive, or most direct file links.”We’re doing all this magic with AI and the video player is stuck in 2015. Fix it, xAI.

• 
  Adam (@aclater) reported 38 minutes ago

  Hey @FedEx @fedexhelp - you've got the wrong address on a dropbox in alexandria, and I keep getting your angry customers and packages. Happy to work together to fix it? I can DM details.

• 
  Jody (@Jody28391214234) reported 38 minutes ago

  @sarahadams @BenghaziAttacks @BentonDave28405 Same with me Sarah - running into trouble trying just to get the report from DropBox. Help.

• 
  Sara (@monamouroui) reported 39 minutes ago

  @SlmnMANUTD @WindowsLatest I didn't care about updating to the latest build. I cared about how Windows 11's AI deleted my Dropbox files from not only my desktop, but Dropbox itself! I managed to find them in DropBox's web Deleted Files folder and recover them. On top of this Windows decided to move all of my files that were on my hard drive to One Drive without my permission. And in the process of doing so created multiple subfolders D: OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/etc I brought it over the BestBuy to repair the OS because there were other problems, so I cannot tell you how many layers I had to click through to get to my actual documents. I was able to recover the apps that we affected by the update (ScanSnap, Adobe Illustrator, Acrobat, etc) doing a System Restore. But that didn't help with my files.

• 
  Pageform (@ThePageform) reported 40 minutes ago

  Dropbox is where deals go to die. Investors open your “data room.” It’s a shared folder named “My Data Room” with 34 subfolders and zero logic. They close it in 8 seconds. You never know they were there. No analytics. No structure. No story. That’s the problem we built @ThePageform to fix.

• 
  Abhishek Singh (@0xlelouch_) reported 41 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.

• 
  Raziel (@tryraziel) reported 41 minutes ago

  Drew Houston got rejected by 76 VCs before Dropbox became worth $12B. But the rejections weren't random — they revealed exactly what he needed to fix. 2007: Drew builds a file-syncing prototype. VCs say "there are already 20 companies doing this" and "users won't pay for storage." He realizes he's pitching the wrong thing. Storage isn't the product — seamless sync is. 2008: He creates a 4-minute demo video showing Dropbox "magically" syncing files across devices. No technical jargon. Just the experience. The video gets 75,000 signups overnight from a waiting list that didn't exist yet. Same product. Same founder. Completely different story. Key insight: Drew stopped explaining how Dropbox worked and started showing why people needed it. → Before: "We use block-level file synchronization across distributed systems" → After: "Your files, everywhere you need them" When he finally raised $1.2M from Sequoia, it wasn't because he built better technology. It was because he learned to sell the outcome, not the process. The rejections taught him something no accelerator could: how to position a technical product for mass adoption. What's the difference between how you explain your product internally versus how customers actually experience it?

• 
  Sahil Handa (@sahilhandapanda) reported 42 minutes ago

  I'm convinced this kind of environment-setting is even more important online. The digital equivalent of swapping a cassette in a studio is stopping to go hunt down a file in Dropbox or Drive.

• 
  ScarcityMan (@ScarcityMan) reported 43 minutes ago

  You might not believe it, but it is in fact happening, because it increases the cost, time, and difficulty of running a node. "Large" is a matter of opinion, but is clearly a quantity which would add up over time and have an impact. Why don't you want nodes to be as easy to run for people as possible, so that the maximum number of people can participate in the network, making it more valuable and more resilient? Why is that not something you want, to the extent that you will spend time arguing against it? What exactly is your stake in nodes being more difficult to run than they need to be? Why don't you care about spam? Why don't you care that it obviously, as it does everywhere it exists, degrades the quality of the thing being used? Why do think bitcoin will just be fine and go on forever while watching it transform into a poor imitation of dropbox? Why would anyone interested in bitcoin as money continue to use it when it becomes more and more infested with non-monetary data? Why don't you care about the possibility of truly bad stuff ending up on chain until the end of time? Do you think Satoshi made a mistake? Should he have created "Bitdata" instead? Do we not need to fix the world's money? You good with USD or whatever else is inflating away to nothing? So many questions that will never be answered...

• 
  Jeff Preshing (@preshing) reported 48 minutes ago

  What's the point of using smarter models if "smarter" means 10% better at finding obscure bugs and having a sassy attitude? Most of the true productivity gains that coding agents have to offer, which are finite, can be obtained using open-weight models for literally 1/100 of the price. The catch is that you actually need understand the code you are working on. At the same time, I still think there's a viable business serving proprietary models. People are willing pay for Dropbox even though FTP is free, and it's nice to throw a tough problem at a stronger model occasionally (if intellectual property limitations allow it). Plus, there's a whole frontier productizing this stuff. Unfortunately, Anthropic is currently in the business of spreading tall tales about future improvements, then shaking down enterprise customers. Most of it is based on 2010s LessWrong posts full of category errors, some of which I remember reading back in those days. And their recent hostility toward users in the name of safety is a result of the same ideological recklessness.

• 
  SCRIBEMOON (@SCRIBEMOON) reported 51 minutes ago

  Ok great. What do we do. What can we do. I was told We were the problem, the people who vote on Election Day, we made things go slowly. VOTE EARLY THEY SAID. I voted on May 13 via dropbox. STILL NOT COUNTED. I doorknocked for Spencer. Only threatened once- by a Cedars Sinai young white female doctor. The CORRUPTION is too overwhelming. We need FEDERAL INTERVENTION!

• 
  Jesse Meyers (@jmbase) reported 52 minutes ago

  @VISportsTalk @Dropbox I was able to get the web interface to load by switching to a VPN. Before that it was showing a 500 error. Desktop app on Mac is still not connecting. Dropbox status page doesn’t show any issues.

• 
  Natan Hackbarth (@Natan90850688) reported 53 minutes ago

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

• 
  Boris Gostroverhov (@gostroverhov) reported 54 minutes ago

  Let me add my own perspective: this reminds me of the Dropbox story. Before Dropbox, there were already dozens of similar solutions, but they didn’t solve the users’ problem completely or in the way users actually wanted.

• 
  obtuse goose (@abelianraisin) reported 57 minutes ago

  @suchenzang Entire value prop is doing a lot of heavy lifting here everything gcp/aws/azure does can effectively be done in a budget manner by its customers. Dropbox storage similarly (granted it's market cap is way down but still it is a viable business) I have no dog in this fight fwiw