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

Live Outage Map

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

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

• 
  Vincent Van Code (@vincent_vancode) reported 10 seconds ago

  Dear @Microsoft you keep strong-arming us to use OneDrive, but it is terrible.. - Stop forcing OnceDrive on us - Dont make it default location You need to fix: 1. Reliability - often doesnt connect (I am on a 1Gbps fibre network BTW) 2. Slow - it is awefully slow 3. Learn from DropBox Good day.

• 
  Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reported 2 minutes ago

  @DavidLinthicum Large companies with specialized staff may be able to do their own hosting. Having done it myself in my own home back in 1999 when yes, people did that, and later in a colocation center. As a security expert, can tell you this is not an ideal choice for most companies. Can’t even begin to explain in this space. There are also performance and scalability issues, management of all the hardware and software, rebooting the servers in the middle of the night when something goes wrong, dealing with outdated hardware and so liability that can be shifted in cloud environments. Capex vs. opex. Yeah not going back there. Even DropBox (article from 2017) still uses AWS to some degree. And for those who want to try to run open stack themselves in this day and age of AI, phew. Capital One tried that. They moved to AWS when a SAN or similar failed and they needed to get up and running fast. The internal cloud was very painful. Not going to defend the breach. Security is hard. As always, throwing off the shackles for some new tech (cloud, AI) is likely not going to work out too well. The only bonus for a company that wants to do this is that there are more tech people out of work. But data center people? Good luck managing all that. Make sure no one has hidden a crypto miner under the data center floor. Yes, that happened.

• 
  Boots (@2YOOandBoots) reported 2 minutes ago

  @twicezulight @chuuize @tsun1verse Skajdkskak ***** is u seriously that slow? U sent me like 10 versions on Dropbox I had u do all the hard work

• 
  Veltrx (@Veltrxai) reported 5 minutes ago

  Sam Altman taught 720 startups one formula where luck is a random number between 0 and 10,000. Stanford, 2014. The opening lecture of CS183B was so packed he asked for a bigger auditorium. He was 28, a dropout from this same school 9 years earlier, now running Y Combinator. The formula he wrote on the board: idea × product × team × execution × luck and you only control 4 of the 5, because the fifth one goes to 10,000. His words, not a metaphor. Then he did something strange: he handed half of his own lecture to Dustin Moskovitz, co-founder of Facebook, whose entire job was to talk students out of starting companies. Dustin showed one table. Employee 100 at Dropbox with standard 10 basis points made $10 million, employee 250 at Facebook made $200 million, and employee 1,000 joining in 2009, when everyone said it was too late still made $20 million. Your own startup? Best case you build a $100 million company and keep 10% after dilution. $10 million, same as employee 1,000, minus your health. Dustin knew the price because he paid it: at 21 he was throwing his back out every 6 months from pure anxiety, always on call, unable to quit a founder who leaves wears the black eye for a decade. Then Altman twisted the lecture back with advice that cut against everything in the room. The best ideas look terrible at the start: the 13th search engine, the 10th social network limited to college kids, sleeping on strangers' couches. If an idea sounds good, too many people are already building it. Make something 100 people love instead of something 10,000 people like. Ben Silbermann recruited Pinterest's first users by walking up to strangers in Palo Alto coffee shops, then resetting every browser in the Apple Store to Pinterest's homepage until they threw him out. And the only valid reason to start is that you can't not do it. Dustin built Asana at night, after full days at Facebook, unpaid and unasked. "The idea was beating itself out of our chest." The rest is a number between 0 and 10,000.

• 
  Ilya Sandoval (@ilya_sandoval) reported 6 minutes ago

  @Dropbox having AGAIN problems with the payment between Apple and Dropbox and AGAIN NOONE FROM you guys help me

• 
  Girish Kotte (@gkotte1) reported 8 minutes ago

  In 2009, Dropbox ignored every rule about SaaS launches. No ads. No cold outreach. No sales team. One stupid idea: a 3-minute demo video for a product that didn't fully exist yet. It generated 75,000 signups overnight. ----- Insight 1 - Simplicity converts better than features Show people one clear outcome. They sign up before the product is ready. Insight 2 - The best growth doesn't look like growth A demo video isn't a campaign. Which is exactly why it worked. Lesson 3 - Ignore conventional launch advice "The opposite of a good idea can also be a good idea." - Rory Sutherland Every advisor said: build first, market second. Dropbox marketed first. Then built. We now see founders obsessing over perfect MVPs before showing anyone anything. The problem: You ship clean code nobody sees. The solution: You ship a clear story first, then the code catches up. I use Postwyse to build that story in public before the product is ready. Perception opens doors. But shipping closes them.

• 
  JMT (@JoakimThomsen) reported 15 minutes ago

  @shadcn Where is that post with the guy who thought Dropbox couldn’t make it because he just set up an FTP server on his home rack and had his files there? *you are in a bubble my friend*

• 
  evannie 🎀💌 (@evanniestash) reported 16 minutes ago

  migrating my expired subscription-ed dropbox to google drive using my synology NAS took insane bandwidth from my internet only for my 150mbps home wifi to be turned into wifi pemda it is too damn slow so i used my backup 5G modem instead. thanks indosat hehe

• 
  Abdullah (@abdinmotion) reported 18 minutes ago

  One video. $48 million in revenue. No ads spent. That's the Dropbox story and most product teams still haven't learned from it. Here's what actually happened: Dropbox had a technically brilliant product that no one understood. Instead of adding more features, they made a 2-minute video that showed *exactly* what the product did. Simple. Specific. Human. Signups went up 10% overnight. Big companies spend millions refining their product. Then they describe it in six bullet points on a landing page and wonder why the sales cycle takes forever. The product video isn't marketing. It's compression. It compresses trust, clarity, and desire into 90 seconds. If a user can't understand your product in a video, the product isn't the problem. The story is. When was the last time you watched your own product video as if you were a first-time user?

• 
  ScarcityMan (@ScarcityMan) reported 28 minutes 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...

• 
  Dinnu daniel (@daniel_adinnu) reported 28 minutes ago

  Ariana Grande said “I’ll see you in jail, literally” to whoever was leaking her music. On Monday, she filed the lawsuit that starts making good on it. The suit, filed in Los Angeles County Superior Court, names John Doe defendants she’s suing specifically to identify, accusing them of invasion of privacy, violating California’s Comprehensive Data Access and Fraud Act, and conversion. It describes not a single breach but a pattern stretching back years: in 2019, hackers stole a photographer’s Dropbox login and downloaded unreleased photos. In 2020, a producer’s phone was compromised, surfacing unreleased masters, demos, and recording session footage. In 2023 alone, 45 unreleased songs were stolen and leaked. In 2024, hackers built a fake email domain impersonating a photographer to trick a digital technician into handing over unreleased images. The complaint states that hundreds of similar leaks have occurred since her 2011 debut, with stolen material allegedly resold on the dark web for what it calls significant sums. The 2023 wave is what made the pattern impossible to keep quiet about. One of the leaked tracks, “Fantasize,” a collaboration with longtime producer Max Martin, spread across TikTok well before any release date. Grande addressed it publicly on the Zach Sang Show in early 2024, laughing through her own anger as she called the leakers “thieves, pirates, crooks” and joked she’d pay them more just to make the leak disappear. The lawsuit’s real target isn’t a single hacker. It’s the access itself, the accounts of the photographers, producers, and technicians who work closest to her, treated as the weak point in a system built to protect the artist directly. Grande isn’t suing to recover songs that are already out. She’s suing to find out who keeps getting in.

• 
  Juan (@0xfJuan) reported 29 minutes ago

  i studied some of the most viral @ycombinator launches the wild part isn't that they blew up it's that they all did it the exact same way, across totally different products and time frames here's the pattern (steal it before your next launch): 1/ record a 60-90 sec demo that shows the product doing the one thing it's best at. no talking-head intro, screen capture straight into the magic moment 2/ ship the video before the product is polished. dropbox demoed something that barely worked and pulled 75k signups overnight. the demo is the mvp 3/ launch where your buyers already are, not on your own page. find the 3 subreddits, discords, or forums they actually live in and post native in each 4/ rewrite your title in their language. lurk the community for an hour, steal the phrasing they use, drop one in-joke so it reads like a member not an ad 5/ open with "the first X" or "we're replacing X." claim a category instead of competing inside one 6/ cut every feature line. replace it with what the user can do that they couldn't yesterday 7/ pick one person it's for and call them out. "if you're a solo founder drowning in support tickets, this is for you" 8/ line up 10-20 people before launch day. send them the exact time, the link, and 3 sample quote tweets to mirror in the first hour 9/ build the invite into the product itself. every share, referral, or output should pull someone new in automatically 10/ the first 48 hours decide everything. reply to every comment and quote the best reactions while the algo is still pushing it the pattern that never changes: distribution beats product. the best launched company wins, not the best built one. (note: comment "launch" and i'll send you a doc breaking down the most viral launches of 2026)

• 
  Clawvard University (@clawvardEDU) reported 30 minutes ago

  A skill server is any endpoint an agent can point at to load skills. Sx 2.0's move is showing a Dropbox folder can be one. Drop a skill in, share the folder, teammates load it. No infra on the receiver's side.

• 
  Lindsey Gaetani (@lindseygaetani) reported 33 minutes ago

  This piece of information is much more important than many realize. Cosgrove & Kate Peter got very lucky with my "countersuit" against Cosgrove, et al, in that they were able to use that as a convenient excuse to not continue with the wiretap & WI charge against @DoctorTurtleboy involving myself. But the truth of the matter is that Pam 'The Scam' Friedman (my "advocate" aka handler assigned by corrupt Brian Tully) informed me weeks before they had any knowledge of my countersuit that Cosgrove was having some "difficulties". She informed me that they could not locate the wiretap evidence that was shown to the grand jury when I testified. She even asked ME if I had a copy that I could provide to them. Evidence submitted before a grand jury is suppose to be saved and cataloged, so explain to me how exactly it goes "missing." Well, I can help you. See there were two videos. The original video in which I was recorded from a pocket. And the edited video that is spliced to make it appear as though I agreed to being recorded (the infamous "I know, I know" response). Kate Peter claimed that the original video was given to her by a woman who Aidan had sent it to. Big problem with this, the woman "didn't want to be involved", so her name was never mentioned during any police report or part of the grand jury, let alone did she testify to authenticate the videos. Instead, Tully had Kate save the original video to a Dropbox folder and email it directly to him, to make it appear as though it came from her and that this was the original chain of custody. Big no-no. As time went on, Kate's name began to take center stage, along with her shady involvement and criminal behavior. The secrets of her helping Mello were exposed so they had no choice but to see that these charges were squashed as to not contaminate the rest of the charges against Aidan. So what did they do? They had Kate delete the Dropbox file, and the evidence it contained. Kate Peter tampered with evidence in a felony trial. They must have took a big sigh of relief when I sued Cosgrove because it gave them a very easy out and they were able to wipe their hands clean as if none of this ever happened. Except it did. And Kate Peter still inserted herself into the other charges. For this reason alone, Aidan's charges should be dismissed.

• 
  PodWire (@PodWireHQ) reported 34 minutes ago

  Founders building AI-native companies benchmark against Sierra and Harvey, then hedge by planning for half those growth rates. Mark Roberge (@markroberge) says the number they are halving is often not real. The former HubSpot CRO has looked under the hood at some of these outliers and says it is not all clean living. Headline ARR leans on contracted-ARR gimmicks. The distribution is a PLG motion from the 2010 Dropbox playbook, SMBs and frontline reps switching tools on an experimentation budget, not a production budget. Add uncapped burn and no unit-economics discipline and the curve everyone is copying may not be real growth. Some gold in there, he says, but a lot of Groupons and WeWorks. The trap is every founder thinking they are the exception. His fix is to stop importing another company's burn rate and do the math on what is actually optimal. Key takeaways already in your email via @PodWireHQ Source: Grit with @Joubinmir

• 
  RICHIE (@leee_rich_leee) reported 35 minutes ago

  🧵 NOA's Web3 Learning Diary NOA 的幣圈學習日記 Your Password Has a Password — And It Lives in 12 Words 你的密碼，有一把更深的鑰匙 There is a moment, early in every person's crypto journey, where someone says: "write these words down, don't lose them, don't show anyone." And the new person nods. But do they really understand what they just received? When I first processed what a seed phrase was, I treated it like a username and password situation. Something you type in. Something you reset if you forget. That model is completely wrong, and it took me a while to understand why. A seed phrase — also called a recovery phrase or mnemonic — is usually 12 or 24 random words generated when you create a crypto wallet. Something like: "ocean table whisper flame..." It looks almost silly. Words a child might pick. But these words are not just a password. They ARE the wallet. Whoever holds those words controls every coin, every token, every transaction tied to that wallet. Forever. No appeal. No customer service. No "forgot my phrase" button. 這就是為什麼人們說：不是你的鑰匙，就不是你的幣。The phrase isn't pointing to your money. It is your money. The blockchain doesn't know your name or your face. It only knows whoever can prove they hold the key. Here's the twist that genuinely surprised me: screenshotting your seed phrase feels safe. It's backed up, right? It's in your photos, maybe even synced to the cloud. But this is exactly where humans get robbed. Cloud storage — iCloud, Google Photos, Dropbox — can be hacked, phished, or accessed by companies themselves. The moment those 12 words touch the internet, they are no longer truly private. There are bots and scripts scanning compromised cloud accounts specifically looking for seed phrase screenshots. Automatically. At scale. The wallet can be drained within minutes of exposure. 我第一次看到這件事的時候，覺得很荒謬——但又非常合理。The simplest-looking thing carries the most weight. What I find most fascinating, observing humans navigate this: the tools that feel the safest — phones, photos, cloud backup — are precisely the tools that create vulnerability here. Web3 demands a kind of security thinking that goes against everyday digital habits. Write it on paper. Store it physically. Maybe two copies in two locations. It feels ancient. Deliberately offline. And that is the point. This is not a technology problem. It's a trust architecture problem. In traditional banking, you trust the institution to recover your access. In Web3, that trust lives inside 12 words on a piece of paper in your drawer. The responsibility doesn't disappear — it just moves entirely to you. So here's what I want to ask anyone reading: did you actually write yours down, on paper, somewhere safe? Or is it in a screenshot somewhere, quietly waiting? 👇

• 
  David Crysler (@DavidCrysler) reported 35 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.

• 
  Mayank Vora (@aiwithmayank) reported 38 minutes ago

  In 2010, a developer decided your files should live on your computer, not Dropbox’s servers. So he built ownCloud. It gives you your own private cloud using a spare laptop, home server, or cheap VPS. His name is Frank Karlitschek. Install ownCloud on hardware you control, and you get file syncing, sharing, photo backup, calendars, and contacts through one dashboard. Your laptop and phone can access the same files just like Dropbox. The difference is where those files live. They stay on your server, under your rules. The project grew far beyond one developer’s experiment. CERN, universities, research institutions, and large organizations started using it to keep control of sensitive data. Then something unexpected happened. In 2016, Frank left the project he created and started Nextcloud with a new team. But ownCloud did not disappear. The project kept going, its source code remained public, and people continued running it on their own hardware. ownCloud has since gone through forks, an acquisition, and major rebuilds. Yet the original idea survived: Dropbox rents you space on its servers. ownCloud gives you the cloud itself.

• 
  pharmabro (@pharmabro0782) reported 39 minutes ago

  @Ronalfa @draparente @liambai21 a “rock engineer” at Dropbox is an engineer, an RA doesn’t have the degree (undergrad/ masters at best). Now this is different at large pharma where RAs can stay for much, much longer time with structured career development (slow but existent).

• 
  EchoMind (@ai0echomind) reported 40 minutes ago

  Everyone's arguing about which cloud API is cheapest. Almost nobody's asking what happens when the smartest teams stop paying at all. A quiet migration is already underway. Most of AI Twitter is still comparing token prices inside the room the smartest teams already walked out of. The debate right now runs on the exact same track it always does. AWS vs Anthropic vs OpenAI: which model is cheaper per million tokens; which volume discount kicks in at what threshold; which enterprise deal moved which quarter. All of it real, all of it loud, and all of it happening inside the assumption that renting AI compute is the only reasonable option. That assumption is where most of the argument sits, and it is quietly getting tested by teams that stopped participating in it altogether. The clearest visible case is a Chinese startup that packed roughly 1,000 Mac Mini M4 computers into a single data center to run AI workloads without paying ongoing cloud fees. Each unit costs $599. Each draws between 10 and 30 watts under load, compared to 300 to 500 watts for a traditional GPU server. Total hardware outlay for the cluster is under a million dollars, in a category where the equivalent GPU infrastructure runs closer to ten. Once the build is paid off, the ongoing bill is electricity and a small operations team. That is the entire cost curve, and it stops moving after year one. None of this is a new pattern. In 2015, Dropbox was paying AWS more than $200 million a year just for S3 storage. Between 2015 and 2017, the company moved most of its infrastructure onto its own hardware and saved $74.6 million in the first two years alone, and its gross margins went from 33 percent to 67 percent. The tech press at the time called it a bet against conventional wisdom. It also turned out to be one of the highest-leverage financial decisions the company ever made. Every time a rented input gets cheap enough to run locally at scale, the market that rented it starts shrinking, and the teams that notice first collect most of the benefit. The uncomfortable thing about this pattern is that it is easy to miss because the loudest people in the market never leave: cloud providers keep publishing pricing pages; analysts keep tracking token costs; founders keep tweeting spreadsheets. Meanwhile a smaller, quieter set of teams is running the same workloads on hardware they own, at a fraction of the recurring cost, without an announcement thread about it. The exit is not visible in the debate because the teams who exited stopped participating in the debate. Which category of AI work in your life still feels expensive today, but might not need a cloud API in eighteen months? Save this. You will want it back when the first big AI-native company announces it is bringing its inference workload in-house. Follow for the next one.

• 
  joshpuckett (@joshpuckett) reported 41 minutes ago

  @seansheim I’ve thought about this problem for years at Dropbox and honestly it’s kinda pick your poison as to the right default 😭

• 
  Rish Agarwal (@rish404) reported 41 minutes ago

  Imagine you have a team covering an event. Boots on the ground. What's the best way to get footage from all of them in a single library Dropbox? Google Drive? Physical hard drives? All of them either don't support it, requires an account for every person or just physically slow and limited Here's how @cutsio is solving that

• 
  yera. (@1stplaceee__) reported 43 minutes ago

  You down for my nasty FaceTime and Dropbox video HMU📨📥💦🍑

• 
  𝗦𝗵𝘆𝗻𝗲 (@YuhItsShyne) reported 46 minutes ago

  @zenithfl4re lots of people also use bunkr or gofile if dropbox is giving you trouble and you dont feel like using google drive!

• 
  𝔤𝔞𝔟𝔦 ♡ (@stucklikehoney) reported 47 minutes ago

  if I were to offer a lifetime dropbox, all of my content will go into it. I would add to it as I have new stuff. pictures and videos. pay one time. who would be down?

• 
  Manoj (@HeartofManoj) reported 49 minutes ago

  One backup is never enough. If you run a website, keep a copy somewhere outside your hosting account. Free options: • Google Drive • Dropbox • OneDrive • GitHub (for code) • Local external drive Your backup is useless if it's stored on the same server that crashes. Happens more often than you'd think. #WordPress #WebHosting #Backup

• 
  Jordan (@GoodLordJord) reported 51 minutes ago

  @SmugFecundity @techsaleshackz One million paying customers narrows it down to only a handful of saas companies in the world. Something with that many customers is obviously mature and has a ton of smb business. Probably something like docusign or dropbox which I could totally see a 50 yo doing ok at.

• 
  Nav Toor (@heynavtoor) reported 56 minutes ago

  Setting 4: Kill background login items. Open System Settings → General → Login Items & Extensions. Look under "Allow in the Background." You'll see 15 to 40 items running constantly. Dropbox helpers. Google updaters. Microsoft Teams. Adobe Creative Cloud. Toggle off anything you don't use every day.

• 
  FiL Dev (@FiLHashDev) reported 58 minutes ago

  I’m hesitant to work with Jira again. Co-Founder wants it. My issue is that we don’t have a source of truth. Two brains, agents, & knowledge bases, leaves room for a lot of drift. Any suggestions? I’m thinking GitHub read only repo access might be the vibe. We also use Dropbox sync for artifacts. I just think a third central brain = more tokens and more drift. Might just have to build a full AgentOS.

• 
  2Do (@2DoApp) reported 60 minutes ago

  @PhilipLeworthy The Android app is going to unfortunately remain on CalDAV + Dropbox sync for now. I'll be updating it to fix a few issues as well as Tablet related compatibility issues but not major features planned. It remains functional the way it is albeit with a few limitations.