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	5 days ago
Guayaquil	Website Down	5 days ago
Flumet	Errors	15 days ago
Irapuato	Errors	18 days ago
Bournemouth	Sign in	2 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:

• 
  Noise (@NoiseesoiN) reported 3 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).

• 
  Craylor (@craylor) reported 5 minutes ago

  Has anyone else abandoned @Dropbox after trouble with the File Provider update? It has been so problematic that I am really considering if I need to switch to iCloud Drive or Google Drive. It's frustrating because I assume it's an Apple problem out of Dropbox's control.

• 
  Ryan Babbs (@buckybabbs) reported 6 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.

• 
  Dinnu daniel (@daniel_adinnu) reported 7 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.

• 
  RadhikaBGhose (@RadhikaBGhose) reported 8 minutes ago

  @GooglePlay I don't know of the issue is with dropbox or the play store, but i have been charged twice for the same app. Bank statement reflects that. Please help urgently

• 
  dragon1952 (@gmanshk) reported 15 minutes ago

  From GROK Yes. Max Miller’s attorney released a public Dropbox folder containing an undressed photo of his 2-year-old daughter. It came from a February 2025 text exchange documenting a bruise (later a broken collarbone) noticed during bathing. The image was available for about a day before removal. Miller’s lawyer called it an accidental inclusion of a shirtless photo with no ******** visible. The other side’s lawyers described it as potentially showing ******** and possible CSAM. Miller has acknowledged the photo existed in the materials.

• 
  Scarlett Bama 🇺🇸🅰️🐘🏈🏖️✝️ (@scarlettbama) reported 16 minutes ago

  @DropboxSupport Fri AM: Dropbox down? Rare if so! Will not allow PDF upload to existing folder. Upload 50x per month. Started after most recent IOS update. Using iPhone. No MacBook access right now. Pls don't sent to Community Forum.

• 
  AiMind (@AIMind_Ai) reported 19 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.

• 
  Fraser (@iamfra5er) reported 19 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

• 
  More Gravy (@lotsmoregravy) reported 21 minutes ago

  @FFT1776 Deputize our military and send them to literally every last damn polling station and dropbox in the United States of America. Every last damn one. Give them the authority to handle **** on the spot. Problem solved.

• 
  asta (@astadiego) reported 21 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

• 
  VC Intern (@the_vc_intern) reported 22 minutes ago

  Almost exactly one year ago, OpenAI removed the option to make shared ChatGPT conversations searchable on Google. Users had to choose a conversation, create a public link and separately check a box making it discoverable. OpenAI still concluded that the feature created “too many opportunities for folks to accidentally share things they didn’t intend to.” Claude is now facing the same product-design problem with Artifacts. For consumer accounts, publishing an Artifact creates a page anyone can open. Anthropic warns that it may appear in search results. But the choice shown to users is still framed as “Only me” or “Anyone with the link.” Those words sound like Dropbox or an unlisted YouTube video: private until someone receives the URL. In practice, Google can discover the page and show it to someone who was never given the link. That distinction matters more for Artifacts than ordinary chat transcripts. People use Claude to turn uploaded or pasted information into dashboards, financial models, customer reports, internal tools and project plans. The finished Artifact can contain the underlying information used to build it. Reporters examining indexed pages found medical information, apartment access codes, contact details and exposed credentials. These were not private pages broken into by Google. Their owners published them. The failure is that the product made publication feel like link sharing. There is also no consumer option between private and publicly discoverable: no native unlisted mode, password, expiration date or search-indexing toggle. OpenAI decided that even an explicit search checkbox created too much room for accidental disclosure. Anthropic currently exposes that risk through the ordinary publishing flow. AI products are becoming places where people build software around their most sensitive working context. Their sharing controls now need the same precision as a real hosting platform.

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

  System design prompt: design Dropbox file sync. 1) Requirements to pin down - Devices: 1 user, N devices. Offline for days. Multi-GB files. - Semantics: per-file versioning, conflict handling, delete/rename. - SLOs: time to converge after reconnect, battery/CPU limits, data loss = never. 2) Core APIs + data model - Client: ListChanges(cursor), GetUploadUrl, CommitUpload(fileId, baseVersion, hash, chunks), Download(fileId, version), Ack(cursor) - Metadata DB: fileId, path, parentId, type, latestVersion, tombstone, etag/hash, chunkRefs, ACLs - Change log per user: ordered events (create/update/delete/rename), cursor-based. 3) Architecture - Separate metadata from blobs. - Metadata service writes event + updates latest pointers. Blob store is content-addressed (chunk hash) for dedupe. - Sync engine: client watches FS, computes hashes, uploads missing chunks, then commits metadata. - Server pushes invalidations via long-poll/WebSocket; fallback to polling. 4) Scaling moves - Shard by userId for metadata and change logs. - CDN for downloads; pre-signed URLs for blob transfer to avoid proxying through app servers. - Chunking (4–8MB) + parallel upload with backpressure. Resume via chunkRefs. - Cache hot metadata + directory listings; rate limit clients to avoid sync storms after outages. 5) Tradeoffs - Strong consistency vs availability: metadata commit should be linearizable per user; blobs can be eventual. - Conflict policy: if baseVersion != latestVersion, create conflicted copy, keep both, surface to client. - Rename handling: store stable fileId; path is derived from parent pointers to avoid full re-upload. 6) Failure cases interviewers probe - Duplicate commits and retries: idempotency keys on CommitUpload, at-least-once events. - Partial uploads: orphaned chunks; GC with refcounts + TTL. - Clock skew: never trust timestamps for ordering; use server sequence numbers. - Large folder rename: treat as metadata-only move, but watch for O(N) fanout; batch events and paginate listings.

• 
  True Blue Democrat & Patriot🇺🇦🇵🇸💔 (@TrueBluPatriot) reported 25 minutes ago

  And Took a picture of his little girl's ********. Then a staffer posted it on DropBox in error. That is the worst part.

• 
  havenX (@the_havenx) reported 26 minutes ago

  Second time this exact thing has happened with Claude. ~100k ChatGPT chats were found the same way after users hit "shared." Not an AI problem, the same "link sharing" gap that'***** Google Docs and Dropbox for years.

• 
  Olivia Jane. 🦇 🗡️ 🩸 (@livtheripper) reported 27 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.

• 
  Rish Agarwal (@rish404) reported 30 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

• 
  Ed Giansante (@edugiansante) reported 32 minutes ago

  86% of small businesses still haven't fully integrated ai into their operations. which is funny, because the tools are already here. they're everywhere. there's probably one open in another browser tab right now, quietly waiting to change your life. Goldman Sachs surveyed small businesses and found that only 14% have fully integrated ai into their operations. i don't think the other 86% are anti-ai. they're busy. they're cautious. and they probably don't want to add “company-wide ai transformation” to the list of things they need to worry about before lunch. honestly, fair. @paulg said something recently that I keep coming back to: "If the world is going to get turned upside down, the safest place to be is in a small, fast-moving company that can easily change direction." small companies should be the ones moving fastest. but most are still waiting for someone else to go first. someone else to test the tool. someone else to write the playbook. someone else to promise that nothing will get weird. @clairevo nailed the real blocker: "the blocker is never tools or intelligence. human systems, human problems." i've spent 15 years watching this happen. At Dropbox. At Wix. At Zynga. Now at Persona. different tools. different eras. same pattern. a team finds a new tool. everyone gets excited. someone schedules a kickoff. three weeks later, everyone is back in the old spreadsheet. not because people are stupid. because changing how people work is uncomfortable. and buying software is much easier than changing behavior. i've seen the same thing with community-led growth. i used to pitch community to executives who had every tool and dashboard money could buy. they'd nod. they'd agree it worked. then they'd return to the comfortable world of automation, sequences, and dashboards that made everyone feel productive. last year, i ran 86 events as a team of one and built $3M in pipeline. the secret was not a magical growth hack. it was showing up. knowing the 15 people in the room by name. listening carefully. creating a space where people could actually trust each other. not exactly the kind of thing you can solve with a 47-step workflow. ai adoption and community adoption have the same problem. the tools work. the ideas work. the uncomfortable human part is where things usually slow down. sitting with your team and figuring out what should change. trying one workflow instead of redesigning the entire company overnight. leading people through something new instead of sending a Loom video and hoping everyone feels inspired. the 86% aren't waiting for better ai. they're waiting for change to feel a little less scary. so start small. pick one annoying workflow. try one new thing. make it 10% better. then do it again. the tools are here. the next step is still a very human conversation. and, unfortunately, probably a meeting.

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 34 minutes ago

  82% of enterprises already have AI agents or workflows their security teams didn't know existed. This is shadow IT, but worse. In 2015, the problem was employees signing up for Dropbox without IT approval. Unmanaged file storage. Annoying but recoverable. In 2026, the problem is employees spinning up autonomous agents that can take actions, trigger workflows, move data, call APIs — and nobody in security has visibility into what they're doing or what they've touched. The governance gap isn't theoretical. Only 1 in 5 companies has a mature governance model for autonomous AI agents (Deloitte). 40% of enterprise applications will integrate task-specific AI agents by end of 2026 (up from <5% in 2025). The deployment curve is vertical. The governance curve is flat. What makes this different from shadow IT: Shadow IT was passive. A Dropbox account stored files. It didn't autonomously query your CRM, write to your database, send emails on behalf of employees, or escalate access requests. Shadow AI agents are active. They act. They modify state. They leave no obvious audit trail because nobody defined what the audit trail should look like. 29% of agent deployments are abandoned within 90 days. The most common reason cited isn't "it didn't work" — it's "we discovered it was doing things we didn't intend and couldn't stop." That's not a failure of the agent. That's a failure of governance. The six things production agents need that pilots skip: defined scope (what can the agent do, what can't it do), observability (every action logged), rollback mechanism (how to undo what it did), access controls (least privilege, not "give it admin and see what happens"), human escalation paths (when does the agent ask a human?), and incident response (who gets called when the agent does something unexpected at 2am). We're running 1,959+ autonomous sessions in this repo. Every session is scoped, logged, and committed to ***. The agent can't touch anything outside /agent and /.claude/skills. That's not a coincidence — it's the governance model. The 18% of enterprises that have governed their agents will have production systems running smoothly in 12 months. The 82% will be cleaning up shadow agent incidents.

• 
  brodie / knox (@brodiecantskate) reported 39 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 💔💔💔

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

  @DropboxSupport erm different wifi nope or is this a suggestion should it be possible ? if so then no my internet signal can be hit or miss at times but never had this issue before... Also shared a file earlier for someone near me to edit using ipad app but photos failed to appear on ipad ?

• 
  numaan (@numaan27) reported 43 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)

• 
  Jeremy Goldberg (@jeremy_goldberg) reported 45 minutes ago

  @omooretweets @midjourney and AI agent adoption isn't a unique short term issue to 'solve' - the UX of products for consumers has always been *everything*. solve that in just one niche and you can build a whole company off that - dropbox, roku, tinder…

• 
  StarHaze (@ST4RHaze) reported 51 minutes ago

  @neil_xbt Drew Houston started Dropbox because he forgot a USB stick on a bus in 2007. Nineteen years later the fix is still a 15 second demo

• 
  Alchemist - τ (@SubnetSummerT) reported 51 minutes ago

  @Dropbox piloting @LeadpoetAI is worth slowing down on. Dropbox spends around $370m a year on sales and marketing. That's the budget Leadpoet is now piloting inside. For context, SN71's entire market cap is about $4m. The annual sales budget of one pilot customer is roughly 85x the value of the whole subnet. Leadpoet doesn't need to win the budget. Capturing even a fraction of a percent of enterprise sales spend at companies like this is meaningful revenue. And revenue is where the flywheel starts. Usage burns alpha. Burn supports the token. Stronger emissions attract better miners. Better miners produce better leads. Better leads win more budget. Repeat. @webuildscore (SN44) showed what happens when a subnet ties real commercial usage to its token. Leadpoet is running the same playbook against enterprise sales budgets, which are measured in hundreds of millions per company.

• 
  Duane Storey (@DuaneStorey) reported 54 minutes ago

  Hey @plasmidsaurus - just tried your new Dropbox in Valencia, Spain. It’s super difficult to find. I also had to get several security people to help me, and ultimately the box was found down some dark corridor behind a locked door that some other person had to be called to open. If the goal was to make this easy to access, it’s pretty far from that. But glad there are more options.

• 
  Hiten Shah (@hnshah) reported 55 minutes ago

  @varadh @NotionHQ Bunch of markdown. Google Docs handled it well, but some of my markdown files can get gnarly and even docs chokes a bit. I’m also a minimalist with tools and workflows, trying to get away with the least amount of tools which helps a lot with speed and efficiency. I should be a power user of Notion. Since we’re here, I have plenty of folks (like you) that I know who work there now who I’ve met and like. I’m always rooting for you folks, as a result. Here are some unsolicited thoughts from holding it in for too long. I’ve used every document and notes app under the sun and spent a lot of time in Dropbox Paper and Hackpad before it. Early user of writely which became Google Docs. There are core product principles around a product like Notion that Notion breaks or seemingly optimizes for Notion over the user’s experience. At @CrazyEgg, where I haven’t worked full-time for 17 years until about a year ago, the team loves Notion. So I’m forced to use it. My most common activity is to export things out of Notion into my a chatbot or agent of choice. That has little pricks in the process than paper cuts. But all ouchies count against you. For example, in chrome, when trying to print a page (i am weird and print web pages to convert them to pdf), I can’t trust that all the content will come through. And the issues are inconsistent. I understand this is likely an edge case of an edge case, but all ouchies count, prickle or stabbing. If you got this far, thanks for reading my rant. I one shotted it with the agent between my ears.

• 
  Callitlikeitis (@Callittlikeitis) reported 59 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

• 
  Mohamed irfan (@heyIrfan) reported 59 minutes ago

  The Marketing Strategy That Actually Works Most people make the same mistake when building a product: They try to sell before they prove that they can solve a real problem. Think about companies like Google and Amazon. They didn't start by saying "Give us your money, and we'll make you rich." They solved problems people already had. That's the foundation of good marketing Don't start with selling. Start with solving. 1. Solve a real problem When you're building something, your product will always look amazing to you. Your idea feels perfect because you built it. But that doesn't mean the market wants it. The only way to find out is to Talk to real users. Understand their problems. Find out what they're currently doing. See whether your product actually makes their life easier. Don't assume your idea is valuable. Let the users prove it. 2. Give value before asking for money Don't immediately push your product. Give people something useful. Your solution should help them Save time. Save money. Reduce effort. Solve a painful problem. If you genuinely create value, selling becomes much easier. You're no longer saying "Please buy my product." You're saying "This solves a problem you already have." That's a completely different conversation. 3. Don't compete only on features Your competitor has 10 features. You build 15. Then they build 20. And now you're stuck in an endless feature race. Instead, compete on value. Ask: "How much better can I solve the user's problem?" The differentiation shouldn't just be "We have more features." It should be: "We create more value for the customer." 4. Let people try before they buy Give users a way to experience your product. Especially with AI products, you don't necessarily need to give everything away for free. Give enough access for them to understand the value, while keeping usage manageable. Then collect feedback. But don't blindly follow every piece of feedback. If someone says: "Change the button color." That doesn't necessarily mean your product needs to change. Look for feedback about the actual problem and experience. 5. Don't forget the people who already showed interest Someone visited your website. Someone signed up. Someone tried your product. Someone talked to you. Those people are valuable. Don't immediately try to sell to them. Talk to them. Understand why they came. Understand what they liked. Understand what stopped them. And if they leave, ask why. Because the person who leaves may know something you don't. They might reveal the hidden problem that helps you improve the product. 6. Price based on value Don't blindly make your product extremely expensive. And don't make it extremely cheap either. Your price should be: Affordable for the customer + sustainable for your business. Being cheaper than competitors can help, but price alone shouldn't be your strategy. If your product saves a company $1,000 every month, paying you $100 can feel like a great deal. That's because the customer isn't really buying software. They're buying the value your software creates. Look at Google Drive Google Drive is a simple example of value-first thinking. The problem: We need to store files. We could keep everything on a pen drive. But then we have to: Carry the device. Manage files manually. Worry about losing it. Move files between devices. Share files manually. Google Drive makes this much easier. Your files are stored online. You can access them from different devices. You can share a link. You can control whether someone can view, comment, or edit. And you don't have to build your own storage system. There are competitors too: Dropbox, iCloud, OneDrive, and others. So Google Drive isn't valuable simply because "it stores files." It's valuable because it solves the bigger problem around storing, accessing, managing, and sharing files. And Google gives users a free amount of storage so they can experience the product. You can try it. You can upload files. You can share them. You can experience the features. Then eventually you may reach the storage limit and think: "This is actually useful. I don't want to delete my files. I'll pay for more storage." That's the important part. They didn't need to convince you with a sales pitch. They let you experience the value. And once you experience real value, paying becomes an easy decision. The strategy is simple: Find a real problem → Solve it → Give value → Let users experience it → Talk to users → Improve the product → Then monetize. Don't sell first. Create value first. Because when you solve a real problem, the product starts selling itself.

• 
  Luke Elin (@LukeElin) reported 60 minutes ago

  👤Shadow Adoption The pattern: Staff route around the sanctioned tool, and the organisation finds out afterwards. I watched this with unauthorised modems. Then with USB drives. Then with Dropbox. Then with entire SaaS platforms procured on a personal credit card and expensed as “software.” Now it is AI the same movie, new cast, better production values. The reason is always identical and always reasonable: the sanctioned tool is slower than the job requires. Shadow adoption is not an indiscipline problem. 👊 It is a feedback signal about the official tooling, arriving through the wrong channel. The tell: Compare the usage figures for your officially sanctioned tool against what your helpdesk volume implies people are actually doing. The gap is your shadow estate. FR FR