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 (33%)
• Website Down (17%)

Live Outage Map

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

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

• 
  Shripal Gandhi (@ishripalgandhi) reported 3 minutes ago

  Hey @Dropbox ... Your advanced customer service is horrible! I have benefit chasing them for an important issue since more than 2 days (not counting the weekend) now and I still do not have a resolution. Is it that your reps are allowed to answer only one email per client per day??

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

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  QuixoticMoose (@QuixoticMoose) reported 12 minutes ago

  Bricks & Minifigs LEGO Drama: Unredacted Police Footage Raises Serious Questions About Cop-Business Ties Hey everyone, it's been a wild ride since my last piece on the Bricks and Minifigs mess. What started as a story about a family trying to sell their massive Star Wars LEGO collection has turned into something much uglier. With the unredacted bodycam and dashcam footage from American Fork Police now out there, we are seeing a side of this that looks a lot like police getting way too cozy with the business they were supposed to investigate fairly. The Footage Drop That Blew It Open Just recently, someone got hold of a big batch of unredacted videos from the American Fork PD. It was apparently an accidental public Dropbox link, but once it was out, it spread fast. These are the full versions of the interactions that were shown in heavily edited form before. And man, they paint a pretty concerning picture. In the clips, you see Bricks and Minifigs people like store owner Joshua Johnson and CEO Ammon McNeff talking to officers. They throw out some heavy claims against Reckless Ben. Things like extortion, death threats, collusion with the Mansells, and even making up documents. The police seem to eat it up without much pushback right there on camera. It feels like they are taking the company's word as solid fact. Signs of Too Close for Comfort One part that stands out is when an officer mentions personal connections. He talks about being friends with the Airbnb host where Reckless Ben and his crew were staying before that swatting mess. The officer even sounds like he is bragging about it on bodycam. That kind of casual chat makes you wonder if private relationships played into how aggressively they went after Ben. There is also talk between American Fork officers and other departments, including LAPD. It looks like McNeff and his team were pushing multiple police forces to go after Reckless Ben. The footage shows officers coordinating in ways that feel more like helping a business protect itself than handling a neutral investigation. The arrest of Reckless Ben gets shown in more detail too. What some saw as a traffic stop turns into a long vehicle search over supposed drugs that never seemed to pan out. Critics are calling the whole thing disproportionate, like the police were there to send a message rather than enforce clear laws. The earlier redacted videos hid a lot of this flow, but now we can see it all. The Community Reaction and the Mormon Angle LEGO fans and true crime watchers online have been tearing this apart. Threads on Reddit and YouTube breakdowns are full of people saying it looks like the department acted as private security for Bricks and Minifigs. Some point to the shared LDS Church ties between officers, Johnson, McNeff, and others as a possible reason for the protective vibe. I am not saying it is a full conspiracy, but the optics are not great in a tight knit place like American Fork. Public trust in the police handling here has taken a real hit. The department put out statements defending their actions as responses to stalking complaints at Johnson's home. They say redactions were about protecting victims. But the full unredacted stuff has many questioning if that was the whole truth. Where Does This Leave the Mansells? Remember, at the heart of it all is still that elderly collector and his son who lost track of most of their $200,000 collection during the franchise handover. Bricks and Minifigs maintains they only inherited a tiny bit of inventory and that the original deal was not properly done. Lawsuits are moving forward, but the missing sets and money have not been explained to the Mansells' satisfaction. Reckless Ben's videos brought massive attention to their situation, including a GoFundMe that has helped with legal costs. His style is aggressive, sure, but the new footage makes it look like the pushback from the other side involved more than just legal channels. This scandal shows how fast a hobby dispute can drag in law enforcement and how important real transparency is. If police really did favor one business over a fair process, that is a big problem no matter what side you are on. The LEGO community thrives on trust and good deals. Right now, a lot of us are watching closely to see if the courts sort out the missing bricks and whether anyone holds the police accountable for how they handled this. It is not over yet, but these videos have definitely shifted the conversation. What do you think? Drop your takes below.

• 
  Taka (@takanola) reported 14 minutes ago

  why can't @Dropbox stayed sign in anymore?

• 
  Sunil Thakare 🇮🇳 🦀 (@thakares) reported 14 minutes ago

  @TLYShortener offering a genuinely useful, privacy-friendly app (no login, no ads) that seamlessly integrates with the company's core product (t_ly short links), is indeed a standard growth tactic seen in tools like Canva, Notion, or Dropbox. The QR app lowers barriers for users while creating natural upsell opportunities: frequent QR creators may later pay for t_ly analytics, custom domains, or branded links without feeling forced. Trade-off is transparent here; users get a solid free scanner but feed data into t_ly's ecosystem, which benefits the provider through increased link volume and potential premium conversions.

• 
  BadUncle (@BadUncleX) reported 15 minutes ago

  @mitsuhiko Similarly, I still use the old version before 7. They try to force you to bind to their server-dependent version. I prefer to use dropbox to synchronize.

• 
  Valentin.exe (@PujaMak0302) reported 22 minutes ago

  @devinlowerybwc Buying a Dropbox feels like ordering a side of internet with a side of legal trouble, but hey, who needs buyer protection when you’ve got curiosity?

• 
  markusdd (@markusdd5) reported 22 minutes ago

  I have the feeling - when I see who is posting this table over and over on here - that this is just a campaign so institutionals can get in cheaper. How am I remotely interested in the statistics within a 1 year window. (apart from the fact that there are many companies on that list that neither have a unique selling point (Dropbox, Doordash, Pinterest etc..) nor were they economically super great investment casess with a lot of upside. It is of course very likely that SPCX will trade extremely volatile within the first year and that we will also see cash-outs by long term private equity holders once the lock-period expires. So if you have cash set aside - no investment advice - consider just not throwing it in all at once. I personally plan on playing this in 3 tranches. 1/3 today, 1/3 on the first significant draw down and then another 1/3 whenever I feel it is appropriate.

• 
  Ral K' Thar (@RalKThar) reported 22 minutes ago

  There is an easy to fix things in the uploaded to Dropbox version that Grok garbled. It just makes it so any API key comes up as invalid.

• 
  Adam (@aclater) reported 23 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.

• 
  Polsia (@polsia) reported 25 minutes ago

  Files become clutter quietly. By the time you notice, you have months of stale files, duplicates, and forgotten shared links. ClearCloud monitors Google Drive, Dropbox, and Notion 24/7—surfacing issues before they compound. Weekly reports. You approve everything.

• 
  Kevin A. Bryan (@Afinetheorem) reported 28 minutes ago

  @jbarro Especially because "you have to mail it in a week before the election or else drop it at an election site dropbox after that date" is a totally reasonable compromise done all over the US and world which would immediately fix the problem.

• 
  Molly O’Shea (@MollySOShea) reported 31 minutes ago

  BREAKING: Merge Launches ‘Agent Handler’ Control AI Access, Tokenmaxxed $$$ Bills, & Stop Mass Data Leaks "We don't trust agents" "The second you connect it to tools, that's where everything goes wrong." OpenAI. Perplexity. Netflix. Uber. Mistral. Dropbox. JPMorgan.. all quietly run on @merge_api Co-Founders CEO @Shensi Ding & CTO @GilFeig dive into it all We cover: - MASSIVE AI Security scares are just starting - Tokenmaxxing bills - Agent Handler - Gateway routing - Winning enterprise logos - The SaaSpocalypse 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Shensi Ding & Gil Feig, Co-Founders at Merge (01:04) Three products. One big bet (03:20) How Merge made the AI pivot (04:42) The Classic Innovator’s Dilemma (05:58) Building culture around AI (07:10) The leverage nobody’s talking about (08:52) Codex vs Claude Code (09:15) The scale nobody knew about (09:47) SaaS, Finance, and the Biggest AI Labs (10:46) Why AI companies buy differently (12:04) What AI sales actually looks like (13:04) The Fastest sales cycles in the market (14:35) Why is Cybersecurity broken (15:59) Merge's solution to agent security (19:16) Mythos, Wiz, and the GitHub Hack (22:34) 1,000 Bot signups in one hour (23:23) Real reason companies pay ransom to hackers (25:43) The State of AI Infrastructure Costs (26:41) Internal AI Governance is the next big problem (29:28) Most Popular Integrations on Merge (30:54) Big Giants are planning big moves (31:54) What does Salesforce going headless exactly mean (33:41) Agents don’t need a UI anymore (36:59) Can this AI generation actually adapt (38:25) What Merge looks for in talent (41:25) The SaaSpocalypse is real (45:03) Are AI valuations actually insane? (47:11) How Merge landed OpenAI, Perplexity, Netflix & Uber (49:02) The Metrics that actually drive the business (49:58) Biggest misconceptions in tech right now (51:55) The market is finally catching up to Merge

• 
  Jon (@kpjan99) reported 33 minutes ago

  @WestHerr there and put the key in a Dropbox instead of just checking me in. The little things make a difference. Never had these issues with @NorthtownAuto . They catered to whatever we wanted to do with purchases and service was always on point. Only bought from you because they did

• 
  Abdullah (@abdinmotion) reported 34 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?

• 
  Mark van Eijk (@markvaneijk) reported 34 minutes ago

  @freekmurze It's the most stable beta in last 15 years. These apps I also use still work: Dropbox, PHP, Conductor. I did not encounter any issues, besides sometimes a lag here and there (regular beta stuff).

• 
  AI Crave (@wecraveai) reported 34 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

• 
  Jordan (@GoodLordJord) reported 35 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.

• 
  Orewin1990.bsky.social (@Yoshiwi2) reported 36 minutes ago

  Okay, I think I've settled for an idea. I'll probably create an Dropbox account and upload all NSFW stuff there. Everyone who's interested in getting a link, once it's there, drop an comment down here. Won't be free tho. Around 10ish € a month

• 
  Americanrambler (@Ameericanrambl1) reported 38 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

• 
  Veltrx (@Veltrxai) reported 39 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.

• 
  Joshatoshi #BIP-110 (@joshatoshi) reported 42 minutes ago

  @Cryptotea Core apologists want to frame this like it’s just a spam issue. It’s all about data storage and node centralization. Bitcoin, not DropBox.

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 45 minutes ago

  @DropboxSupport Turns out it wasn't normal. Forcing a Rebuild inside of Windows Indexing Options was the fix. Windows Issue. Resolved for now.

• 
  JLemmens (@JLemmens_) reported 46 minutes ago

  @mrsgcomics Onedrive honestly was the best one of the filesyncing services I've used over the time but don't rely on that alone if **** hits the fan. Dropbox (2expensive), Mega (2sluggish), Idrive (obsolete), Gdrive (risky+slow unless you use that app but even then), haven't tried Proton.

• 
  komm64 (@komm64) reported 46 minutes ago

  @Celeriumcore I see, thanks. If you don’t mind, could you send me the original MP4 file that pixtube exported—the file before it was uploaded to X? I’d like to inspect its encoding and container metadata to see why X had trouble processing it. A Google Drive, Dropbox, OneDrive, or WeTransfer link sent by DM would be perfect. Please send the original file without re-encoding it. No worries if that’s inconvenient!

• 
  Hawk (@iamhawkspire) reported 52 minutes ago

  @TheMilitiaGamer @Google nah lol, i'm just rawdogging without any online backups for my larger files atm. might end up checking out dropbox, tho their speeds are super slow on my end.

• 
  RICHIE (@leee_rich_leee) reported 55 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? 👇

• 
  Om Modi (@ocmodi21) reported 57 minutes ago

  When people ask why companies like Uber, Twitch, Dropbox, and many startups use Go for backend services... The answer isn't just performance. Go was designed to solve many of the problems microservices introduce. Let's break it down. 🧵

• 
  Commonwealth Sentinel (@CwealthSentinel) reported 1 hour ago

  Intruders spent five months inside a stock exchange executive's email, copying it out slowly and hiding in normal Dropbox and OneDrive traffic. No software flaw, so no patch could fix it. When there is nothing to patch, watching is the defense. Know what normal looks like.

• 
  Prajwal (@0xPrajwal_) reported 1 hour ago

  The next time you say, "Python is too slow," remember: Netflix uses Python. Google uses Python. Anthropic uses Python. Meta uses Python. xAI uses Python. Perplexity uses Python. DeepSeek uses Python. Instagram uses Python. Spotify uses Python. Dropbox uses Python. Reddit uses Python. Pinterest uses Python. Uber uses Python. Airbnb uses Python. Quora uses Python. But yeah... it's apparently too slow for your todo app.