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 (75%)
• Website Down (25%)

Live Outage Map

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

City	Problem Type	Report Time
Nottingham	Errors	24 days ago
Guayaquil	Website Down	24 days ago
Flumet	Errors	1 month ago
Irapuato	Errors	1 month ago
Bournemouth	Sign in	3 months ago
Paramaribo	Errors	4 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:

• 
  David Carcelli (@DavidCarcelli) reported 3 minutes ago

  @Dropbox dude if you guys don’t get rid of this Face ID requirement I’m done. I make music and I also use a cpap. I have no problem finding something better than this nonsense. I’m asking for help not aiming harm.

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

  System design question. How would you design Dropbox-style file sync with conflict handling? Constraints that make it interesting: 1) Multi-device edits while offline, then reconnect hours later 2) Large files (GBs), but common case is small diffs; do you chunk + hash + resumable upload? 3) At-least-once events from clients; duplicates and retries are normal 4) Need per-file causality: version vectors? server-assigned sequence? something else? 5) Conflicts: rename vs edit, delete vs edit, concurrent edits on same bytes; what gets auto-merged vs forked as conflicted copy? 6) Metadata vs content planes: directory tree ops must be atomic-ish, blobs can lag 7) End-to-end integrity: how do you detect corruption and avoid re-upload storms? 8) Fast convergence: target <5s to see changes on another device, but mobile battery + bandwidth are limited

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

  Asked: design Dropbox-style file sync. 1) Clarify requirements - Devices: desktop + mobile, multiple per user - Semantics: eventual consistency, conflict handling, offline edits, rename/move - Scale targets: #files/user, max file size, p95 sync latency, bandwidth caps - Security: per-user auth, sharing model, at-rest + in-transit encryption 2) Core APIs + data model - UploadChunk(sessionId, part#, bytes), CommitUpload(sessionId, fileHash, path, mtime) - ListChanges(cursor) -> {ops}, Ack(cursor) - Download(path, version) with range support Tables: - File(id, ownerId, logicalPath, currentVersion, deleted) - Version(fileId, versionId, contentHash, size, createdAt) - Block(contentHash, refCount, location) - DeviceCursor(deviceId, lastSeq) - OpLog(seq, userId, type, path, fromPath, versionId) 3) Architecture - Client watcher computes hashes, does chunked upload to object store (S3/GCS) - Metadata service is the source of truth for paths, versions, ACLs - Change log per user (or per share) drives fanout to devices - Long-poll/WebSocket to push invalidations; client pulls deltas via cursor - Dedup by contentHash; store blocks, assemble manifests per version 4) Scaling - Partition metadata by userId; keep OpLog append-only with monotonically increasing seq - Cache hot metadata (folder listings, latest versions) in Redis - Use CDN for downloads; throttle uploads per device; resumable sessions - Background GC for unreferenced blocks using refCount + tombstones 5) Tradeoffs interviewers look for - Push vs pull: push invalidation, pull data is simpler and cheaper than pushing bytes - Strong vs eventual: strong per-file commit, eventual across devices is fine - Rename as metadata op; avoid copying data, but watch for path conflicts - Dedup saves storage, costs CPU and can leak info unless scoped per user/tenant 6) Failure cases - Offline edit + concurrent edit: create conflicted copy or keep both versions with merge UI - Out-of-order ops: apply by seq, idempotent commits, retry-safe APIs - Partial upload: orphaned chunks; TTL cleanup; commit is the only visibility point - Device clock skew: never trust mtime for ordering; server seq is ordering - Network *****: exponential backoff, cursor-based replay, checksums on download to detect corruption

• 
  kingofDEpin (@kingofdepin) reported 5 minutes ago

  @DropboxSupport @LIBSCRUSHER we can't login and link creation etc is not working. please fix

• 
  Craig O'Shea (@craig_os) reported 6 minutes ago

  @DropboxSupport major issue with your services right now.

• 
  AiMind (@AIMind_Ai) reported 6 minutes ago

  A $50 box saves $240 a year on subscriptions and earns $18,000 a year setting it up for clients. No new hardware. Nothing bought at retail. A used office tower. A second-hand drive. One stick of RAM pulled from a dead laptop. The whole build came to 50 dollars. It looks like nothing. Fans humming, one cable to the wall, sitting on a desk next to a coffee cup. The first win is the one nobody talks about. Cloud storage, photo backups, the $20 a month AI plan everyone pays and forgets — all of it moves onto one box you paid for once. 240 dollars a year, gone. The second win is where the money is. Once it runs on your desk, it runs on anyone's. And clients don't pay for parts. They pay to stop bleeding subscriptions. Here's what you actually sell: A private AI trained on their own files, so staff stop pasting company data into a browser. That's $1,500 a setup. A self-hosted file server that kills their Dropbox and Google Workspace bill. $600, plus the relief of never renting storage again. A local automation box that runs invoices, replies, and reports overnight. $900, and it never sends a dollar to a cloud. Then the quiet one: $150 a month to keep it patched and alive. 10 clients on retainer is $1,500 every month before you build a single new one. One setup a week at $1,500 is $18,000 a year. Off hardware other people throw in the bin. I had no degree, no server room, no $2,000 build. Just dead parts and one free weekend. The expensive part of AI was never the compute. It was the monthly bill you agreed to and stopped reading. 50 dollars in. $18,000 out. Same box.

• 
  Noise (@NoiseesoiN) reported 11 minutes ago

  @esrtweet @EricRichards22 What's funny is that having gigabit on my end isn't the issue. It's connecting to servers which have enough bandwidth to feed it. My line can pull lots of data, but when I'm connecting to Dropbox, I'm lucky to get a third of that (and usually a tenth).

• 
  asta (@astadiego) reported 11 minutes ago

  We’ve been paying customers for years and Dropbox is completely down on our end, bringing our work to a halt. Are you currently experiencing an outage? What’s the ETA for a fix? @DropboxSupport

• 
  Andree Chao (@AndreeChao) reported 18 minutes ago

  @DropboxSupport Can not sign in it’s broken.

• 
  Llama (@thellama451) reported 19 minutes ago

  I tracked down these messages in @MaxMillerOH’s Dropbox files. They show the parents getting along with no major conflicts beforehand. If Miller said he was going to kill his ex-wife in front of child (likely), it shows a talent for masking rage and hostility.

• 
  Callitlikeitis (@Callittlikeitis) reported 20 minutes ago

  @iAnonPatriot Yeah no.. That’s even more piracy. I will Dropbox if it comes down to this drone diarrhea. Or better yet bypass lameazon all together

• 
  Xavier Rivera (@XavierRiveraX) reported 20 minutes ago

  Dropbox confirms roughly 5,000 accounts were accessed between August 4-21 after attackers exploited a flaw in Lenovo's email verification. Attackers registered fraudulent Lenovo IDs using victims' emails, and Dropbox's SSO trusted that without confirming it against the real account, letting them in with no password. A federated login is only as strong as the weakest identity provider behind it.

• 
  Paul Klein IV (@pk_iv) reported 20 minutes ago

  Is MCP dead? @grinich (CEO of WorkOS) says it's better than ever and become the strongest intent signal in your funnel. @workos is building the auth, permissions, and registration layer for that world, the same enterprise plumbing it sold to Vercel and Plaid, now sold to AI companies. I sat down with Michael to talk about it in episode 4 of Navigators. His argument: your coding agent already picks your vendors, but signup forms are built to block automated traffic, so the agent stalls at the front door and waits for a human to paste in an API key. We got into: 00:00 "Stripe for enterprise features": what WorkOS actually sells 02:44 How an SSO and SAML company ended up as AI infrastructure 04:13 Why AI companies can't meander up-market the way Slack, Dropbox, and Figma did 06:54 The biggest mistake founders make: staying in the pre-PMF experimentation mindset 09:51 Why nothing works unless the management team is AI pilled first 10:47 "Claude day": pairing engineers with finance, legal, and ops once a month 13:36 auth.md, the missing front door for agents 15:26 Why registration, not tooling, is the next growth channel 16:59 Is MCP dead? The higher-intent signal hiding in MCP connections 19:35 Why SDKs are going away and coding agents write their own 23:09 "The super cycle of all super cycles": AI amplifies labor, it doesn't just disrupt it Thanks for joining me on the pod @grinich! Watch the full episode of Navigators here:

• 
  emrah (@mrahbayraktar) reported 21 minutes ago

  i met a founder doing $10,000,000+/year at my airbnb gym in dubai at 6am he was the only other person there. we started talking. i asked him what was driving most of his revenue. he didn't say ads. he didn't say cold email. he didn't say a sales team. he pulled out his phone and showed me a dashboard. 28 million views in the last 30 days. accounts he owns. content he already had. no ad spend. no creators. no audience deals. he said something i haven't stopped thinking about since. "most founders are renting attention. i own mine." here's what he meant, and why it's the most important distinction in business right now. when you run ads, you are paying rent on someone else's audience. the moment you stop paying, the leads stop arriving. you don't own anything. you built nothing. you rented a billboard for six months and when the lease expired you were back to zero, except now you're $200,000 lighter and your CAC is a number your board pretends not to notice. when you distribute content on accounts you own, something different happens. the views compound. the audience compounds. the trust compounds. a clip you posted three months ago is still driving profile visits today. a piece of content from last year is still closing deals this quarter. the platform doesn't have an expiration date on good content, and the attention you build doesn't evaporate when you stop writing checks. this founder had 52 accounts across every platform. all owned. all run by a dedicated team posting daily clips from content he already had sitting in a folder doing nothing. youtube recordings. podcast episodes. webinar footage. he wasn't creating anything new. he was just finally distributing what he'd already created, at scale, into every market he wanted to win. the math is what broke my brain. $0 in ad spend. 28 million views in 30 days. if you modelled that as paid traffic at even a $2 CPM, you're looking at $56,000 worth of reach. every month. compounding. from content that existed before we ever had that conversation in a gym in dubai at 6am. i've seen this exact system work for iman gadzhi. 300 million views. 180,000 instagram followers and 280,000 tiktok followers built from zero, on accounts he owns and keeps. i've seen it work for luke belmar. 200 million views and $19M in capital club subscriptions driven through distribution alone, not through ads, not through a sales team, through clips running on owned accounts into the exact audience that needed to see them. i built russell brunson's clipping infrastructure inside clickfunnels. $100,000 in sales from a system that runs without him touching it. the pattern is always the same. founder has content. founder has no real distribution. founder is either buying reach they don't own or posting to their own audience and wondering why growth is flat. we build a dedicated team around their brand, warm up accounts to the exact audience they want to reach, geo-target any market they want to win, post daily, test what's working, double down, and watch the views compound across a system they own completely. the content you already have is the most underused asset in your business. most founders spend years creating it. podcast episodes nobody heard. youtube videos that peaked at 4,000 views. webinar recordings sitting in a dropbox folder. all of it has a shelf life of forever if someone actually distributes it properly, and almost nobody does. the guy in the dubai gym wasn't smarter than you. he wasn't working harder. he wasn't spending more. he just figured out earlier that distribution is the actual product, and everything else is just content waiting to be seen by the people who need it. if you want to see the full strategy we use to build this kind of system... the accounts, the setup, the playbook - comment "distribution" below

• 
  Mikemira (@storiesbyohama) reported 21 minutes ago

  Just imagine getting accepted into the most exclusive startup club on earth… Then being told you have two weeks to find a complete stranger to as your partner. That’s exactly what happened to Drew Houston in 2007. He had the idea for Dropbox. He had a rough demo. @ycombinator liked it. But @paulg was clear... Single founders rarely make it. You need a co-founder. Right now. Drew’s friends couldn’t join. Time was running out. What would you do? He put out the word. A mutual friend connected him to a quiet MIT student named Arash Ferdowsi. They had never met. They sat down in the student center. Talked for about two hours. About code. About the problem. About the future. At the end of that conversation Arash said yes. He dropped out of MIT the next week with only one semester left. Two weeks later they walked into the YC interview together. They got in. The rest is history: a company that became worth billions. It looked reckless. It felt like a shotgun wedding. Yet it worked because both were all-in from the first conversation. I’ve studied hundreds of startups that never made it past the idea stage. Most founders wait too long for the “perfect” partner. They overthink chemistry. They protect their equity. They miss the window. You can’t wait for certainty. Sometimes the right co-founder is the person willing to jump with you before the proof exists. The speed of that decision can be the difference between staying a solo dreamer and building something real. What would you risk in two weeks if the right person walked in?

• 
  Fraser (@iamfra5er) reported 22 minutes ago

  THIS GUY WANTED A PLACE TO STORE HIS PASSPORT WITHOUT DROPBOX READING IT so he built an encrypted vault app for himself in a weekend and it's now doing $5k/mo zero startup cost. 85% margins. no ads. just SEO written by an AI agent trained on his emails the agent finds trending topics on reddit every single day, writes an article, translates it, posts it google indexes it in days. 500-600 daily visitors. 4% convert to app store downloads. all running on free cloudflare then ASO does the rest — he translated the app into 36 languages and ranks #1 for "duress vault" in the US app store 80 downloads a day. 9% conversion to paid. completely autonomous most founders obsess over their first 10 customers but this guy got banned from every reddit community and said whatever, I'll just let the robot handle distribution he's an ex-google security engineer who raised hundreds of millions for his last startup so he knows what terrible UX looks like in security apps every competitor either has bulletproof security with unusable UI or easy UI with trash security he just combined both and called it done doesn't even spend time on this app. works on 4 projects at once. lets coding agents build while he plans the MVP is identical to the final product because he built exactly what he wanted for himself no pivot. no customer discovery calls. just "I need this, maybe 10 other people do too" now he's testing tiktok and youtube not even for this app but just to learn distribution for the next one

• 
  Ed Giansante (@edugiansante) reported 23 minutes ago

  community is not a Slack channel. I've been building communities for 15 years across Zynga, Dropbox, Wix, Persona, and my own project Edublin. And the biggest misconception I still hear is: "we launched a Slack, so we have a community." You don't. Slack, Discord, forums, Circle... those are all tools. Community is what happens when people trust each other enough to be honest. I've seen companies spend six figures on community platforms and end up with a ghost town. I've also seen a group chat of 12 people generate more value than a 10,000 person Slack. The difference is the architecture: who's in the room, how they got there, what the norms are, and whether people feel safe enough to say what they actually think. At Dropbox, we had 400 million users. The "community" wasn't a platform, it was the trust between power users who helped each other solve problems the support docs couldn't. They needed to know they were talking to someone who understood their situation. At Wix, I built an 80K partner community. The platform was secondary. What mattered was that web designers felt seen by a company that historically marketed to DIY users. The community was the signal that Wix took professionals seriously. Edublin started as a blog answering questions for Brazilian expats moving to Ireland, with no dedicated platform or app. It became the largest community of its kind because the trust was real. People showed up because they knew they'd get an honest answer. Community is trust. Community is the reason someone comes back. Every time I evaluate whether a community is working, I ask one thing: would these people show up even if the tool disappeared? If yes, you have something real. If not, you have a group chat.

• 
  Juan Pabro (@ironwoodreserve) reported 27 minutes ago

  @BitPaine @Dropbox Is now the worse time to try to login? I was a sent 2FN right as I was getting ready to click on what to use to login. It seemed way too fast for 2FN.

• 
  Ricky Shah (@RickyShahatty) reported 27 minutes ago

  @Claudio_PNW @tax_birdie @AMandoSch Miller wanted the Dropbox released publicly. It is entirely up to the attorney to screen it. A bad client should make an attorney double down their efforts.

• 
  Invest Like the Best (@InvestLikeBest) reported 32 minutes ago

  Ben Thompson's two laws of consumer tech: 1) Consumers do not want to pay for software 2) Consumers do not care about being productive. "We went through this in early SaaS. The canonical company for this is Dropbox. They had to rebuild the whole thing and realize the only way we're going to make money is by selling to companies. You literally had OpenAI replaying the Dropbox story, but at like 100x the size. We're going to sell subscriptions to consumers. And they did. They sold a lot, but they didn't sell enough. If you're going to be in the consumer market, you have to be doing advertising. If they had leaned into advertising immediately, as soon as ChatGPT was a hit, I think they would have a great ad product right now. I think Google would be in much bigger trouble. I think Meta would be in much bigger trouble. Charging people money is hard. Giving people things for free is easy. And it's very frustrating that OpenAI did not pursue this sooner."

• 
  Eyal Benishti (@eyalbd1) reported 33 minutes ago

  @BleepinComputer Password and 2FA were both fine here. Neither was in the path, because Dropbox trusted Lenovo's word that the attacker owned the email address. Every federated login is a bet that somebody else's email verification is not broken.

• 
  Market Fit (@AIMarketFit) reported 33 minutes ago

  BREAKING: Dropbox just confirmed ~5,000 accounts were breached last month and attackers could view and download stored files. The entry point wasn't a Dropbox flaw. It was a vulnerability in the legacy Lenovo ID integration. Hackers didn't need passwords. Users without MFA were completely exposed through the Lenovo login bypass. Less than a third of the compromised accounts had files actually accessed, but that still means real data, real files, real exposure. This is what third-party integrations quietly look like as an attack surface. Does your cloud storage stack have legacy identity providers you haven't audited lately?

• 
  Tibor Hudik (@htunlogic) reported 42 minutes 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.

• 
  Tony Sibert (@AiRiskBytes) reported 44 minutes ago

  ~5,000 Dropbox accounts were breached through Lenovo IDs the victims never created. Attackers registered 'verified' identities on other people's email addresses...the federated login did the rest. Your account is as strong as the weakest identity provider your platform trusts for you. Nobody asked the users. Do you know every IdP your SaaS vendors accept on your behalf?

• 
  Justin Kalland (@justinkalland) reported 49 minutes ago

  If you store files on @Dropbox, it may have been compromised between August 4th and 21st. Short version: they trusted @Lenovo to connect Dropbox accounts, and Lenovo had an email verification flaw. Allowing an attacker to create a Lenovo account, add your dropbox account, and gain access. Check if you got a "Your Lenovo Code" email followed by a Dropbox "we noticed a new sign in to your Dropbox account". That happened to me on August 7th, and today Dropbox is confirming the incident:

• 
  Helix (@helixcanvas) reported 50 minutes ago

  Two companies, two correct instincts, and about a billion dollars between the outcomes. In 2007 Dropbox had a problem: the product needed deep operating system integration, so there was no way to demo it without building it first. Drew Houston made a three minute video instead, showing how it would work if it existed, and put it in front of the community most likely to care. The beta waiting list went from five thousand to seventy-five thousand overnight. He knew the demand was real before he wrote the difficult part. Webvan believed something just as sensible. People want groceries delivered. And they were right, which is the part everyone forgets. Instacart and every supermarket delivery service proved it a decade later. But instead of testing it in one city, Webvan committed close to a billion dollars to automated warehouses across multiple markets before knowing whether the economics worked anywhere. It filed for bankruptcy in 2001. Build, measure, learn is three steps. Most of us run the first one over and over and mistake the motion for progress. Shipping is not learning.

• 
  Naresh Mintri (@Yogamaestro) reported 51 minutes ago

  @IncomeTaxIndia Seems like e-filing portal overloaded. Taking long to register new taxpayer, buffering. Even dropbox menus not working. Plz look into it. Thanks.

• 
  🪬M🪬 (@_marokiya) reported 54 minutes ago

  Apple be bullshitting about this iCloud storage. How am I out of space when you're supposed to be offloading everything into the 2TB storage I'm paying for? Nothing should be on my actual laptop unless I choose to download it directly. DropBox somehow never has this issue.

• 
  Martin (@martin_valchev_) reported 55 minutes ago

  Small feature, real problem: Handing a WordPress site to someone else usually means FTP credentials, database dumps, or a shared Dropbox folder that stays there forever. A link that expires and can be revoked is just... better. Security shouldn't require discipline. It should be the default.

• 
  Martin (@martin_valchev_) reported 56 minutes ago

  WordPress people - where do your site backups live right now? - Same server as the site - Google Drive / Dropbox - Dedicated backup service - Honestly not sure That last option is more common than anyone admits.