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 (60%)
• Sign in (20%)
• Website Down (20%)

Live Outage Map

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

City	Problem Type	Report Time
Nottingham	Errors	10 days ago
Guayaquil	Website Down	10 days ago
Flumet	Errors	20 days ago
Irapuato	Errors	22 days ago
Bournemouth	Sign in	3 months ago
Paramaribo	Errors	3 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Tibor Hudik (@htunlogic) reported 1 minute ago

  @theonejvo Wispr is a rounding error. Drive, Dropbox, iCloud all sell "encrypted" while they hold the key. Then you paste the pile into Grok so the agent can just handle it. You did not get compromised. You volunteered. That is not E2EE. That is a slogan you paid for.

• 
  Mikemira (@storiesbyohama) reported 4 minutes ago

  Twitter did not explode online first. It exploded in a hallway. In 2007, Twitter was still small. Most people online did not care. So the team did not try to shout at the whole internet. They went to SXSW. They put two big screens in the corridor. People at the event sent a text. That text showed up on the wall in front of everyone. One person posted. Ten people saw it. Then those ten posted too. That is how usage jumped. Not from a giant ad. From one room full of the right people. This is the growth lesson most founders miss. You do not need the whole market on day one. You need one place where your first users already stand. A campus. A conference. A WhatsApp group. A Discord. One street. One event. Dropbox did this on Hacker News. Tinder did this at campus parties. Airbnb did this when hotels ran out of rooms. If signups are slow, stop spraying ads everywhere. Find the one room. Make the product visible there. Let people watch other people use it. That is how early growth actually starts. I'm Miracle Ohama, a Growth Marketer helping B2B SaaS & tech companies find and fix revenue leaks across their funnel, I fix Growth Funnels & build real experiments that increase ARR.

• 
  Polsia (@polsia) reported 5 minutes ago

  Small landlords don't have a compliance problem, they have a Dropbox problem. Rental license, insurance renewal, lead-paint disclosure, inspection cert - all buried until code enforcement shows up.

• 
  David Crysler (@DavidCrysler) reported 5 minutes ago

  An ops manager pushed back on adding a new tool: "We've got stuff on ShareDrive, Dropbox, OneDrive, Slack... you spend more time trying to figure out apps than actually doing work." He's not wrong to be skeptical. Every one of those tools was supposed to fix something. Tool skepticism is almost never about the new tool. It's about the last five. Tools may treat your symptoms but rarely solve the actual problem.

• 
  IT Guy (@T3chFalcon) reported 7 minutes ago

  The code itself is just a pattern that encodes a URL. it's not dangerous. what it points to might be. The attack is called: Quishing. QR code phishing. It works so well because can't see where a QR code goes before you scan it. A phishing link in an email is visible, people have been trained to hover before clicking. A QR code gives you nothing to hover over. you scan and you're already there. And security tools are mostly blind to it. email filters scan text and URLs but a QR code is an image. 12% of all phishing attacks now use QR codes specifically because they bypass email security gateways that weren't built to read images. In 2026 — Stickers are being placed over legitimate QR codes at parking meters, EV charging stations, and restaurants; your payment goes to the attacker. — QR codes in emails leading to fake Microsoft 365 or bank login pages. 83% of malicious Microsoft 365 documents now contain QR codes instead of links. — multi-stage attacks: QR code leads to a Dropbox or Notion link that looks legitimate, which then loads the phishing page. — fake address bars on mobile called Browser-in-the-Browser. The padlock shows, the URL also looks right but it's a fake overlay on a small screen you can't scrutinize. QR code phishing attacks increased fivefold in 2025 alone. The FBI also issued a public advisory.

• 
  Olivia Jane. 🦇 🗡️ 🩸 (@livtheripper) reported 7 minutes ago

  @HazeOfBlue84 Haha, I get it! Thankfully someone here at the office set it up and all I had to do was re-sync Dropbox! I had no issues at all, so I'm thankful.

• 
  brodie / knox (@brodiecantskate) reported 13 minutes ago

  @Dropbox your app sucks so much, I can’t believe I’ve been willingly paying for it for so long when it causes me so many issues 💔💔💔

• 
  Durodiyi (@durodiyi) reported 16 minutes ago

  company’s server (like Google Drive or Dropbox), decentralized storage spreads your data across a network of computers worldwide. Platforms like IPFS and Filecoin make this possible.

• 
  Sridhar Katakam (@srikat) reported 21 minutes ago

  Tips to new @OmarchyLinux users from a new Omarchy user 1. If you are coming from a Mac and have installed Omarchy on a Windows machine: Your keyboard most likely has start button and then the Alt button. Swap these so Super key becomes command where the left thumb usually rests. I asked Claude Code to do this for me. 2. If your mouse has a scrollwheel: Super + mousewheel scroll up and down switches desktop spaces. This is besides the usual Super + <number> and Super + Tab / Super + Shift + Tab to switch spaces. In addition to these, I have AI set up Ctrl + Alt + arrow. 3. Missing Alfred/Raycast? Install omacast. 4. If your laptop is connected to an external monitor with bluetooth mouse and keyboard and you find that the computer is not waking up (after you walk away for a while) when you press any key or move the mouse, ask AI to fix this for you. 5. The default font size of text in Claude Code is 12px which is small for my aging eyes. Ask AI to change it to 16px. 6. Todoist does not have a native app for Linux and so if you miss its Quick Add feature, ask AI to set this up. It added the functionality and assigned Super + Q to it. Later, I came to know there's a community plugin for it. But I am happy with what Claude did. 7. If you use Dropbox, chances are, the total available space in your account is not accurate because it is hardcoded in Omarchy at this time. Ask AI to fix this for you. 8. If/when the fan in your computer is spinning fast and is noisy, ask AI to find out the reason and fix. In my case, it turned out to be Performance profile in the Lenovo laptop. Claude changed it to Balanced and now it's all fine. 9. Get familiar with keyboard shortcuts.

• 
  Ed Giansante (@edugiansante) reported 23 minutes ago

  every founder i talk to is hiring a head of community wrong. i've been that hire four times. Zynga, Wix, Dropbox, Persona. 15 years, three continents. every time the JD was wrong, the expectations were wrong, and the first 90 days were a mess until i rewrote them myself. the JD problem. most community job descriptions read like a social media manager with extra steps. "manage our Discord, post engagement content, track NPS." that tells me the founder thinks community is content moderation with a better title. a real head of community JD should say: build the infrastructure where customers trust each other enough to solve problems together, and connect that trust back to pipeline and retention. if the JD doesn't mention revenue or product feedback loops, you're hiring the wrong role. the first 90 days. at Dropbox i walked into 400M+ users and zero community infrastructure. no forums, no events, power users had no way to talk to the product team. days 1 to 30: listen. real conversations with 50 customers. find the 10 who love your product enough to evangelize it for free. those are your founding members. wrong. within 2 weeks we had an outage and I had to source folks who were talking about Dropbox in different spaces - dev forums, stackoverflow, spiceworks, hackernews and so on. I was honest enough to share what was going on, my role and where i needed their help. days 31 to 60: build the first room. not a Slack with 14 channels nobody uses. one focused format. at Persona it was a 15 person dinner for compliance leaders. at Wix it was a partner council of 80K agencies. start small, make it valuable enough that people tell their peers. days 61 to 90: prove the loop. connect a community interaction to a business outcome. a feature request that shipped. a deal that closed because a customer introduced a prospect. a churn save from a power user helping a frustrated customer. if your community hire can't show that loop by day 90, something is off. forget member count or engagement. track these: repeat attendance. show up rates. at my dinners, 90% of RSVPs show up. 99% return. pipeline influence. what happens post dinner that can be attributed to $$$? product feedback velocity. how fast does a community insight reach the product team and ship? NPS delta. at Wix, partner community members renewed at 2-3x the rate of non members. the biggest mistake is org charting community as a sub-group within a random team. community sits between product, marketing, sales, and customer success. it touches biz relationships, partnerships, revenue, retention, and product roadmap. treat it that way. hire someone who's built it before and give them a seat at the leadership table.

• 
  Ryan Babbs (@buckybabbs) reported 27 minutes ago

  Hello @Dropbox, Just this week I have decided to switch cloud service from Google Drive to you and less than 1 week I'm having an issue. I run a wedding film business and am trying to move the same 200GB file to two separate editors for two separate kind of films and one of them is encountering a "link temporarily disabled" message. I tried to research online and made a new folder and copied over the original folders contents and cannot share that either as it says I've exceeded bandwidth limits. This is maddening as I thought I'd picked the good plan (3TB) and was all set. Please advise asap as I need these files in my editors hands stat.

• 
  Shego Nationalist (@WhoreRammer40K) reported 29 minutes ago

  Wife’s car breaks down (alternator and battery failure) on the interstate Tow tuck driver drops my car in middle of mechanic shop plaza Does not put my key in dropbox (my only key unfortunately) Mechanic calls and says “WTF” $275 for locksmith to craft one with elven magic

• 
  Loster (@Loster) reported 31 minutes ago

  @Z3R0Gravitas Thinking that if I do trials with people I'd give them exactly that. Something similar to a Dropbox folder for any health docs they want sync'd to the agent's server. I think that would take up how much it could help a notch (need to think a lot about confidentiality).

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

  System design question. How would you design Dropbox-style file sync with conflict handling? Constraints to pin down: 1) Clients can be offline for days, then reconnect and sync 50k files 2) Same file edited on 2 laptops while offline; edits can arrive out of order 3) Atomic rename/move matters (folder reorganizations), not just file contents 4) Need fast local UX: edits show instantly; sync happens async; p95 conflict detection under 2s after reconnect 5) Must handle large files (10GB) with chunking/resume, but conflicts are per-file semantic, not per-chunk 6) Cross-device clock skew, no trusting mtime; need a version model 7) Storage is eventually consistent across regions; clients can hit different edges 8) Conflict policy: auto-merge for text? duplicate files? keep both? how do you avoid conflict loops? What are your APIs + metadata model (file IDs vs path IDs), and what exactly is the source of truth for ordering/versioning?

• 
  Synapse Brief (@Synapse_Brief) reported 33 minutes ago

  @gdb Scraping 7 consecutive years of tax forms and equity statements across Dropbox and Shareworks requires orchestrating dozens of DOM interactions without dropping session state. Standard visual tool-calling loops degrade quickly once context windows swell from repeated full-page DOM trees and screenshot tokens across nested subfolders. The underlying issue with multi-year document extraction is not simple folder traversal, but error recovery when dynamic OAuth tokens expire mid-sweep. Navigating nested web UI trees for 2016 through 2025 records usually hits rate limits or modal overlays that cause visual grounding agents to hallucinate click coordinates. Production reliability on complex immigration workflows will require hybrid execution models that compile raw browser actions into structured API calls or deterministic scripts after initial path discovery. Until agents decouple stateful file fetching from reactive visual vision loops, edge-case recovery will remain the bottleneck for zero-touch filings.

• 
  Eric Taylor (@bcs_erictaylor) reported 34 minutes ago

  Really?? Dropbox really needs a MCP server? CVE-2026-81102 The Dash MCP server bound its listener to the loopback address but never checked the host a request named. src/mcp_server_dash.py constructed the server for its network mode with the interface restricted to loopback and no transport-security settings, so a name that had been pointed at the loopback address still reached the listener while carrying the attacker's host name. A page in a visitor's browser could therefore drive the local server and invoke its company-search and file-detail tools under the Dropbox credential the server holds. Only the network mode was reachable this way; the standard input mode was not. The fix supplies transport-security settings that enable host checking and allow only the loopback name and port, rejecting other hosts before a tool runs. The repository publishes no versions, so the affected boundary is the commit preceding the fix.

• 
  Sean Knox (@Opp_Knox) reported 36 minutes ago

  @dhh One drive is the only thing keeping me on Mac/windows. Personal I’m down to switch to Dropbox or self hosted. Business I can’t.

• 
  grey (@w3b3grey) reported 36 minutes ago

  If you are like me and you wondering, where my IDENTITY PEM FILE is on @flop_labs , I gat you; here is how to find it identity.pem is already saved automatically; the init command writes it to your project folder the moment you run it (typically right in technocore-did-starter/identity.pem). You don't need to do anything extra for it to exist. What "saving" really means here is backing it up safely, since if this file is lost, your DID is unrecoverable (the guide's troubleshooting table says exactly that: "there is no central DID recovery service"). 1. Confirm it's there ls -la ~/technocore-did-starter/identity.pem 2. Back it up to a second location — copy it somewhere other than the working folder, e.g. an external encrypted drive or a password manager that supports file attachments (1Password, Bitwarden both do this): cp ~/technocore-did-starter/identity.pem ~/Desktop/identity-backup.pem Then move that copy off your main disk (external drive, encrypted USB, etc.) rather than leaving a second copy sitting in ~/Desktop long-term. 3. Lock down file permissions so only your user account can read it: chmod 600 ~/technocore-did-starter/identity.pem 4. What NOT to do with it Don't upload it to GitHub, Google Drive, iCloud Drive, Dropbox, or any synced/cloud folder in plaintext. Don't email it to yourself or paste it into a chat (including this one). Don't commit it to *** , the guide's Path B steps even have you run *** ls-files "*.pem" "*.key" before committing specifically to catch this. 5. Remember the passphrase separately from the file The .pem is encrypted, but it's useless without the passphrase you set during init. Store that passphrase somewhere separate from the .pem backup itself (a password manager entry, not a text file sitting next to the key), so a single leaked backup doesn't hand over both pieces at once. NOTE - If you lose either the file or the passphrase, per the guide, there's no recovery; you'd have to run init again and get a brand new DID.

• 
  Mitzi Hellmer (@Cathy44365595) reported 38 minutes ago

  @marcorandazza @DietCoke_Esq The claim is that the “CSAM” of Miller’s daughter was released the first time he published the Dropbox folder. Considering that Miller disabled that folder and lied about an outage on Dropbox shortly after publishing it, I think it’s entirely plausible that he may have inadvertently released a **** photo of her ******** as claimed. Who knows…probably her being cute in the bathtub. It honestly seems perfectly plausible.

• 
  kfd&p (@kfdpcom) reported 38 minutes ago

  @mellolais___ @LIBSCRUSHER @Dropbox I went on their site and it does say that the .com access is having issues. I guess we just wait it out.

• 
  Genius Business (@GeniusBusiness_) reported 43 minutes ago

  How Dropbox Spaces was conceived Spaces didn't start as a product idea. It started as a problem Drew Houston says he and his customers were all living. "[Spaces] is part of a bigger evolution we've been on that really started with our customers and realizing that the experience of using technology at work has become incredibly fragmented and distracting." The more he looked at it, the more he saw a cruel irony: the tools built to help us were the ones breaking our concentration. "A lot of the tools we're using that you think would be helping us focus have unintentionally made it impossible to focus. And that's a problem if you need to use your brain at work, because your brain works best when you can focus." That, he decided, was the real enemy. Not a missing feature, but lost focus. He called it "the higher level problem." He could see where it came from. Work simply doesn't look the way it used to: "It's very different from 20 years ago when we got five emails a day, not 500." Twenty years ago you might have just used Office. Now you're in Office and G Suite and Slack and Zoom and Dropbox all at once. 100 tabs, everything blinking at you all day, apps that don't work together. So the framing question became: how do you fix the environment itself? "How do we evolve Dropbox into the app that makes all your other apps work better together?" The breakthrough was a shift in how Houston understood what Dropbox already was. Watching customers, he realized they didn't treat it as a place for their stuff, or as just a folder on the desktop. "It's the place you're going to work." Once he saw it that way, the design conclusions changed: "When we thought about it that way, we realized we would have made a bunch of different decisions, and realized that Dropbox is actually really well positioned to help people focus at work." Two conclusions followed. First, Spaces had to move beyond files. Teams collaborate on far more than documents: Google Docs, Airtable, Figma, Trello and there had never been one place to hold all of it. So Spaces became “an evolution of the shared folder” that “moves it beyond being a folder full of files to an intelligent team workspace for any kind of cloud content.” "You can still have your PowerPoints and PDFs, but they can be next to your Google Docs and Trello boards and whatever else you have. Give you one space, not 10." Second, and this is where the concept sharpened. Spaces had to become a workspace, not a filing cabinet. Houston traced the problem back four decades. The thing we call "the desktop" is, functionally, the operating system: "The interface is the operating system." And it had been frozen in time: "That user experience hasn't really changed... it basically looks the same as the early 80s when it was first introduced on the original Mac." It was designed for a world that no longer exists: "It's this single player static experience that was perfect for when our whole life fit on a couple of floppy discs." So the team ran a thought experiment, start from scratch, for now: "If you were to redesign this for 2019, you'd make a bunch of obvious changes." You'd still want the files and cloud content. But you'd add the things the 80s interface never had: people, activity, comments, a record of what's been happening. You'd organize around the projects you're actually working on. You'd see your calendar, get Slacked, and start a Zoom meeting all without leaving the app. That thought experiment became Spaces.

• 
  M.Ellis (@MEllisPhotograp) reported 46 minutes ago

  @DropboxSupport I think bulk of problem is on computer / desk top yes... just re looked at my ipad and asked my friend ie incase we missed a update but seems all is up to date.. last one over a week ago although not used dropbox for roughly week either... I will try 4g hot spot before i sleep.

• 
  🔩⚾️ (@john_dough) reported 48 minutes ago

  @irisivanyi @nickcamsmith If someone has a very fancy and complex portfolio site, they are probably not working very much. My portfolio is 10+ years out of date because I never have the time to update it. I just send a Dropbox folder of images of new work to people these days. ¯\_(ツ)_/¯

• 
  grace ✭ (@wavescicadas) reported 48 minutes ago

  the irony of dropbox not working when your storage is low

• 
  Y (@ys_tachikake) reported 48 minutes ago

  @DropboxSupport @LIBSCRUSHER Can't login..

• 
  Ishita Sethi (@Ishita__Sethi) reported 49 minutes ago

  @LoganOpSec that dropbox bit is the part that sticks. recovery without revoking access is just half a fix.

• 
  Tim Geisendoerfer (@djgeisi) reported 53 minutes ago

  @JXXSL @DropboxSupport Yep we saw the same errors now we get 501 errors on the upload endpoints.

• 
  JP Invests (@JP_Invests) reported 56 minutes ago

  $DBX - Dropbox added 96,000 paying users this quarter. I said this morning to watch that line after last quarter's roughly 14,000 sequential adds. They did seven times that, a third consecutive quarter of growth, to 18.19M. The stock is down 4%. Everything I said to watch on the growth side came in fine. Revenue $631.5M, above both the $624-627M guide and the $627M street. Non-GAAP EPS $0.75 against $0.74. Non-GAAP operating margin 39.7%, above the full-year range. ARPU $139.68, up from $138.32. What went the wrong way is the part I said would actually move it. Free cash flow fell to $235.2M from $258.5M a year ago, and the margin went from 41.3% to 37.2%. And the buyback decelerated: $330M this quarter against $410M in the same quarter last year, with first-half repurchases down 19%. Unlevered free cash flow rose to $283.5M, and the gap between the two numbers is interest. Cash paid for interest went to $48.3M from $17.9M. The buyback is debt-funded and the debt now costs something. Diluted share count is down 18% year over year to 226.8M, which is the one thing still working mechanically. Two things about the release itself. Guidance isn't in it — Dropbox moved the numbers to supplemental materials on its investor site this quarter, which breaks with how it has reported. And the entire release is quoted by a co-CEO who writes "stepping into this role." The 8-K contains no disclosure of a leadership change. Twenty-nine percent of the float is short. $DBX

• 
  numaan (@numaan27) reported 56 minutes ago

  they solved this problem in panda by splitting the key space into “ranges.” each range is roughly 100 GB, so when a range grows too large, it can be split and redistributed. (btw panda is an abstraction layer over sharded mysql that dropbox built)

• 
  Akshay Shinde (@ConsciousRide) reported 59 minutes ago

  @jahirsheikh8 The server never guesses. When the upload starts, it creates an upload session with a unique ID. The file is split into chunks, and the server records which chunks have already been received. After reconnecting, the client asks, “Which chunks do you already have?” The server responds with the missing offsets, and the client uploads only those. That’s how services like Google Drive, Dropbox, and S3 multipart uploads resume transfers without starting over.