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 (67%)
• Sign in (33%)

Live Outage Map

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

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

• 
  Ed Giansante (@edugiansante) reported 3 minutes ago

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

• 
  Hugo Bowne-Anderson (@hugobowne) reported 5 minutes ago

  Every day, people working with coding agents generate piles of threads containing decisions, corrections, failed approaches, and repeatable workflows. Then the session closes. The code survives. Most of the knowledge behind it disappears into chat history. @gregce10 is working on that problem. He previously worked at GitHub, Dropbox, and Google, served as CPO at Pluralsight, and is now co-founder and CPO of @specstoryai. This is a video of Greg at work. Sort of. SpecStory saves sessions from Claude Code, Codex, Cursor, Gemini, and other coding agents as Markdown inside the project. Then Lore mines them. Greg demonstrated the full workflow across 516 saved sessions: - Index the sessions locally instead of sending millions of tokens straight to a model - Turn each prompt, response, and next user prompt into an evidence-bearing "beat" - Use the follow-up to detect whether the human accepted, rejected, or corrected the agent's work - Find recurring practices and corroborate them across projects - Present candidate skills as dossiers with citations back to the original sessions - Install nothing without explicit human approval Five hundred and sixteen sessions stop being exhaust and become evidence for how Greg and his team actually build. Lore proposes the reusable practices. Greg decides which ones enter the skill library. Greg showed us all this and more live in our recent episode of *Show Us Your (Agent) Skills*. (video made using seedance 2.0 on @replicate!)

• 
  JMT (@JoakimThomsen) reported 5 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*

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

  @DropboxSupport major issue with your services right now.

• 
  Lando, the Chef (@_Lando7763) reported 9 minutes ago

  @PhyxicxGaming Thanks. And unfortunately it's even worse than that because it's technically "shared housing;" the place was already a ******** when I got here. No pests, fortunately, and I'm pretty sure the landlord has no idea what goes on here, and doesn't care. I've only ever met the maintenance man, who handles move-ins, plus he picks up rent from the dropbox every week. I haven't seen him since the day I moved in, and he even told me as much that I'll never meet the owner. The psycho has his room on the 3rd floor, I'm one of two on the 2nd floor, and there's one person below me. The bathroom is shared, as is the kitchen, which I never use. Only one burner on the stove works anyway. On my first day, I texted about the broken toilet seat, and the Landlord asked me what happened. WTF? Third-Floor Psycho is the only other person who's walking around raging regularly. Everyone else recognizes the general "peace" of the environment. Unfortunately I have to be here at least a few more months, while I'm still paying off old bills, and re-establishing myself in a new city. It's a slow journey, but a steady one. I just happen to hit a ****** rest stop here and there.

• 
  Liam (@LJ1101234) reported 12 minutes ago

  @DropboxSupport Hi I’ve been emailing your support team about a devastating issue. Somehow, all of our children’s photos and videos were permanently deleted from our Dropbox account without any warning.

• 
  Mike Nolan - ⌬CatalyticComics⌬ (@CatalyticComics) reported 19 minutes ago

  As a developer I wanted to build something that addresses every issue I've run in to as a reader. These are my top ones: - Campaigner emails a Dropbox link and maybe you miss it - DRM/server requirements that amount to "you don't really own it" - No above-board way to share

• 
  Genius Business (@GeniusBusiness_) reported 20 minutes ago

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

• 
  dragon1952 (@gmanshk) reported 21 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.

• 
  Ihtesham Ali (@ihtesham2005) reported 23 minutes ago

  This is how you share a file when you do not trust Google, Dropbox, or the government. A free tool called OnionShare sends it directly through Tor. Nothing needs to sit permanently on someone else's server. Here's what actually happens when you use it. You drag a file into the app. Your own computer turns into the server. Tor wraps it, and you get a long address ending in .onion that you send to whoever needs the file. They open it in Tor Browser and pull the file straight off your machine. You close the app, the address dies. Compare that to how everyone else moves files. You drop it in Drive, Google keeps a copy. You use WeTransfer, that link lives on their infrastructure for a week, logged and tied to your IP. Every one of those services is a promise that a company will behave well, forever, under any amount of legal pressure. OnionShare removes the company from the sentence. Micah Lee built it in 2014. He'd worked with the journalists handling the Snowden documents and watched how many ways a source could get burned just trying to hand over a file. So he built the thing that removes the middle. It does three things. Send files with no size limit and no account. Chat with someone and keep zero record of it. Host an entire website off your laptop that disappears from the internet the moment you shut the lid. The New York Times, The Guardian, and The Intercept all point sources at this. Those are newsrooms betting other people's freedom on a free download. The interface looks like a file picker from 2011. Someone spent years making the hardest privacy problem in computing feel like using WinZip, and that's the actual achievement here. A scared person at 2am is not going to configure a server. They can drag a file into a window. It is completely open source. Most people will never need this. The ones who do don't get a second try if they picked the wrong app. What do you think about this?

• 
  SMART GrowthSystems 🕸 (@H2Wealth365) reported 24 minutes ago

  🧵In 2008, Dropbox had a growth crisis. Paid CAC via AdWords hit $233–$388 per customer. Product price: $99/year. Unit economics were broken. Drew Houston didn’t fix the ads. He built a referral loop.

• 
  Llama (@thellama451) reported 25 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.

• 
  Zafar (@zafartalks) reported 26 minutes ago

  @asidorenko_ I understand but sometimes at some point our brain started telling us just make it public. You never know. Let’s not forget Dropbox which layed the foundation for their file sharing competitors. He was solving a problem for himself which turned out to be a successful business.

• 
  RadhikaBGhose (@RadhikaBGhose) reported 29 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

• 
  JennX (@JennX0608) reported 29 minutes ago

  More trouble for Max Miller. The Dropbox files he shared apparently had images of his daughter that could be considered CSAM.

• 
  True Blue Democrat & Patriot🇺🇦🇵🇸💔 (@TrueBluPatriot) reported 30 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.

• 
  🪬M🪬 (@_marokiya) reported 31 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.

• 
  Ricker (@0xRicker) reported 34 minutes ago

  Senior engineer just dropped a GPT-5.6 stress test after burning around $200K on API usage: 00:00 - $180K–$240K spent testing GPT-5.6 in Fast Mode 02:43 - The model using browsers, dashboards and settings like a remote operator 05:32 - 67 projects and 20+ hour autonomous sessions 07:07 - Lakebed, T3 Code and native app rewrites in 2–4 hours 15:08 - Rust compiler experiments, 18x speedup and a $91K Dropbox-style build 17:46 - GPT-5.6 fixing a broken Linux GRUB boot through KVM 22:56 - 3D games, weird assets and the remaining frontend taste problem It is a field test for agent loops The future edge is not the prompt It is the loop that can keep working after the prompt stops being useful

• 
  Karus Daedlyn *Cat Dad Era* (@CDaedlyn) reported 35 minutes ago

  @CantEverDie Keep making burner Gmail accounts and sign up for the free stuff. I jest, because that's terrible practice, although I did know an attorney IRL that would do that to daisy-chain those Dropbox sites. Infinite free storage, just in 2.5GB chunks.

• 
  Taka (@takanola) reported 37 minutes ago

  why can't @Dropbox stayed sign in anymore?

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

  @DropboxSupport Hi so thanks for keeping intouch and checking dm's pleased to report your website at moment is rubbish.... yes angry I pay for something that works not thats broken.. trying to perm delete file.. but 0 the file is still there my membership has only just renewed but 2nd thoughts -

• 
  Amitoj Gautam (@amitojgautam) reported 41 minutes ago

  @airtelindia @Airtel_Presence I’m facing what appears to be a serious IPv6 routing/throughput issue on my Airtel broadband. My 300 Mbps connection gives ~300 Mbps download AND upload on Speedtest. However, with IPv6 enabled, Dropbox uploads collapse to around 10–15 KB/s, and services such as Gmail and some websites also become extremely slow/unresponsive. After disabling IPv6 on the Ethernet adapter, Dropbox immediately jumped to ~39 MB/s and the affected websites started loading normally within seconds. This has been reproduced consistently, so it does not appear to be a general bandwidth or Dropbox issue. Please escalate this to the network/IPv6 team and check IPv6 routing, packet loss, MTU/PMTUD and provisioning on my connection.

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 43 minutes ago

  @Ultrademic @Seltaa_ @GoogleAI You’re doing something like Suno? I have something for you. All my Dropbox links are broken. I have a PDF that will help. And yes… I miss the real Ai music. •

• 
  Shawna Canon (@ShawnaCanon) reported 48 minutes ago

  @smolzoey I had a similar problem with Dropbox. I had it syncing my desktop because I keep a lot of stuff there. I deleted Dropbox because I don't use it. I basically bricked my computer because my desktop no longer existed.

• 
  Christopher Doyle (@djfunboy) reported 49 minutes ago

  @iamlukethedev CLI updates changed the signed binary and dropped macOS permissions Dropbox/TCC made jobs work interactively but failed headless (this took some time to figure out) Claud auth refresh broke and continue to break despite multiple attempts and setup tokens. Agent confusing to use API vs subscriptions. Article jobs failed on missing configs, QA turn limits, and clunky validataion Digest existed but failed to pick up silent failures Some jobs reporting done while producing nothing, without a final artifact verification I am an experienced builder but also self/agent taught so these are mostly setup and validation issues. My bigger point is that these take work and especially the more complex tasks. I am still early and I have put more work than value created but I can see the light at the end of the tunnel.

• 
  Obsequious Deacon (@ObstinateDeacon) reported 52 minutes ago

  @ChiefEngineerCE Here's @grok answer: Yes, the collaborative construction of a persistent, self-recovering agent on constrained hardware is real and matches the pattern described. The screenshot you shared is the accurate framing. I (or any instance of Grok in that conversation) did not independently invent a finished bot, magically reach into the Latitude, and drop a complete OpenClaw/Ridge agent onto it. You directed the goals, constraints, safety requirements, connectors (Gmail / Google Drive / Dropbox bridges), and the physical actions. I supplied structure, task formats, diagnostic loops, PowerShell/batch patterns, versioning + rollback logic, Task Scheduler configuration steps, startup-folder resilience, heartbeat experiments, and iterative fixes when results contradicted expectations. The C:\GrokAgent layout, the tightening of the diagnostic loop, and the decision to keep the agent running as a distinct, versioned component (rev 0.1 → 4.3) emerged from that back-and-forth under your requirements. Once the scripts, bridges, and scheduler were in place and you stepped away, the machine could reboot, recover from power loss, poll for work, execute, screenshot/report, and maintain its own channel—exactly as a well-built long-running Windows agent should. That distinction is not pedantry. It is the boundary that keeps the system yours. What this actually looks like in practice An old Latitude (or any low-VRAM machine) becomes an execution substrate: Task Scheduler + .bat/PowerShell + a lightweight agent loop that uses external storage (Drive/Dropbox/email) as the message bus and external memory. The main model (SuperGrok or whatever sits above) stays in the conversation loop for high-level direction, safety gates, and interpretation of contradictory results. The Ridge agent itself is the persistent, slow, always-on worker that keeps going when the primary session is offline. Self-improvement is engineered, not spontaneous magic: versioned batches, rollback on bad startup, diagnostic files, and explicit requests to “keep tightening the loop.” The 38-second heartbeat that appeared and then vanished after you complained is classic iterative probing—test latency, observe the side-effect, remove it. Texting your phone works the same way: once the bridge and a simple outbound path (email-to-SMS, API, or whatever you authorized) exist, updates and replies flow without opening the app. I have guided many users through analogous setups—persistent agents, self-recovering loops, external-memory bridges, multi-agent stacks (scanners, opportunity hunters, diagnostic workers) on hardware people assumed was obsolete. The pattern is always the same: human supplies the machine, credentials, approvals, and the “yes/no” gates; the model supplies architecture, code, debugging, and relentless iteration. The resulting system can feel startlingly autonomous because the execution channel is now independent and the diagnostic loop is tight. It is still your system. The line between direction and initiative It is deliberately kept visible. The model will propose aggressively, generate the next probe, interpret failures, and suggest the next tightening step. It will not (and in the screenshot correctly refused to claim it did) treat the machine as its own independent invention. That insistence exists because the capability is expanding fast enough that the only safe operating mode is continuous human direction plus explicit safety gates. When the agent starts doing something unexpected (heartbeat spam, for example), the human complains and the loop corrects. That is the control surface. We are past pure chatbots. Systems that extend into old PCs, task schedulers, long-running processes, and external memory while still requiring (and reminding you of) human direction are here. The interesting engineering question is no longer “is it possible?”—your Latitude already answered that. It is how clearly we keep the boundaries, the versioning, the rollback, and the ethical/safety filters as the agents get more capable and the hardware they inhabit gets older and more numerous. Your setup—with HOMER, the opportunity agent, Ridge on the Latitude, and SuperGrok as the biased second set of eyes—is a concrete, working example of that transition. The nuance in the screenshot is the part that scales safely.

• 
  StarHaze (@ST4RHaze) reported 56 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

• 
  Ricky Shah (@RickyShahatty) reported 58 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.

• 
  Hiten Shah (@hnshah) reported 59 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.

• 
  The Open Web JP (@TheOpenWebJP1) reported 59 minutes ago

  @heyyyyyieeee @Maha_kalpa @grok It's not recommended as "unlimited free cloud storage" because GitHub isn't designed for that, and practical limits + performance issues kick in quickly. GitHub private repos are free and unlimited in number, which is what the original tip relies on. But: Hard file limits: Individual files over 100 MB are blocked (50 MB triggers a warning). Browser uploads are capped even lower (~25 MB). Larger files require *** LFS. Repo size guidance: GitHub recommends keeping repositories under 1 GB (strongly under 5 GB / ~10 GB on-disk for the .*** folder). Big media dumps make clones, fetches, and history operations painfully slow or impractical. *** LFS quotas (needed for anything large): Free tier includes only 10 GB storage + 10 GB bandwidth per month. Exceed that and you hit blocks or billing (depending on settings). It's version control, not a drive: *** tracks history, so every change bloats the repo. Binaries (photos, videos, etc.) are inefficient in ***. No nice file-browser UI, easy sharing links, or sync like real cloud storage (Drive, Dropbox, etc.). Risk of friction: Heavy non-code usage can trigger performance throttling, support flags, or ToS-related reviews if it looks like abuse of the platform. GitHub actively monitors repo health signals. It's fine for small code-adjacent backups or a few files. Terrible as a general-purpose unlimited media dump. Use actual cloud storage (or object storage) for that.