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:

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

• 
  mhamn (@hamn_matt55472) reported 2 minutes ago

  @BANANTICHRIST @DesireeAmerica4 I've been bitten at least a hundred times, twice severely, and never reported it because I didn't want to see the dogs put down because their owners are irresponsible. Probably a lot of people like me. Secure your dogs or get a dropbox if you have a delivery, people.

• 
  Mary, The Other Mrs P 🇺🇸💙🇺🇦📎 (@bvmaryp) reported 5 minutes ago

  @JohnLaMacc What voter fraud? What Dropbox problem?

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

• 
  Jon (@kpjan99) reported 11 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

• 
  Sourav Dutta (@sourav12dutta) reported 14 minutes ago

  @ishankbg @Siradhvaja @PhilipPanass Yes, shodhganga seems to be down. Can you suggest how I can post a folder with 10 pdf files here? Both dropbox and wetransfer are asking for email id.

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

• 
  Matthew Tse (@MatthewTse_) reported 15 minutes ago

  @DropboxSupport Yep, still broken.

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

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

• 
  quantzoid (@quantzoid) reported 17 minutes ago

  @gurishsharma sorry, you're in YC to take down dropbox but you didn't know how to approve a PR on github? what?

• 
  uncle ***** (@probinsyacore) reported 19 minutes ago

  nraas still down but a reddit user has saved most of their mods in a dropbox link oh my god sometimes i do love the internet

• 
  Harshita Renee (@harshitaxmars) reported 20 minutes ago

  Despite me having proven him wrong about the exact requirement table issue he pinned on me as a “it’s her problem, shut her up” (Dropbox has the scoresheet proving I was not out of line, they were), I don’t think he can ever be wrong. That is just technical error on his part.

• 
  Santiago Bustelo (@sbustelo) reported 21 minutes ago

  @DropboxSupport THEY ARE GIVING ME CANNED REPLIES. YOU SCREWED MY WORK AND BURIED ME FOR THE FOLLOWING MONTHS TO FIX UP THE MESS YOU MADE UP WITH MY FILES. I DEMAND A REFUND.

• 
  Google Account (@hanzala_007) reported 22 minutes ago

  @CricketCaptain Where to place names files in dropbox,there are multiple folders. Like last time in saves its not working

• 
  i-LevelUP (@CryptoScout24) reported 24 minutes ago

  Popular Services/Messengers That Are Typically NOT (Fully) End-to-End EncryptedThese are the ones affected by scanning under the current EU Chat Control setup which has passed today in the EU: Email services (most standard ones): - Gmail (Google) - Outlook/Hotmail (Microsoft) - Yahoo Mail - iCloud Mail (Apple, standard) - Many others without E2EE enabled - Facebook/Instagram Messenger (standard mode) — Often not fully E2EE unless "Secret Conversations" are turned on - Skype (standard chats) — Microsoft can access content. - Snapchat — Chats and snaps are not E2EE by default (some features have it, but not comprehensively) - Telegram (standard/cloud chats) — Encrypted between device and server, but Telegram holds the keys and can access content. Only "Secret Chats" are protected. - Discord — Messages are not E2EE; the company can moderate/scan - Older/traditional SMS/MMS — Completely unencrypted. - Xbox Live messaging and some gaming platforms. - Cloud storage/file sharing tied to chats (e.g., Dropbox, iCloud, Google Drive in some contexts) — Often scanned Let that sink in ! allegedly to fight against child abuse

• 
  GRETA (@Greta__ai) reported 26 minutes ago

  We added Asset Manager to Greta. You're building an ecommerce app: product images, demo videos, docs, case studies. Before: Upload images to Cloudinary, videos to S3, docs to Dropbox, links scattered everywhere. One breaks, and you're scrambling through three different services trying to find the original. Now: Upload once in Greta. Reuse assets across all your projects, with everything centralized. No external services. No broken links. No context switching between five different platforms while you're trying to ship. That's smoother. That's what actually building feels like. 50 MB per file. Images auto-compress.

• 
  Kathleen Marie (@lifesavoring) reported 27 minutes ago

  @DropboxSupport I have the same problem as Detroit Media Magazine described below - my Dropbox became unavailable until the latest update. I tried to upgrade my account, but was registered instead for a free trial - ? I have to update my email to get it authenticated - PLEASE RESPOND, thanks.

• 
  Some guy (@ibesomeguy) reported 33 minutes ago

  @Voxyz_ai Doesn't sound like a Codex problem, sounds like a Dropbox problem. Syncthing doesn't take your files offline, ever.

• 
  Jozef Maxted (@jozefmaxted) reported 34 minutes ago

  terrible rate limits, and errors when your AI of choice hits its head up against their overcomplicated block API. All problems you don't have if you knowledge base is just files! Thats why we've started building Treehouse, its basically Notion + Dropbox combined with loads ...

• 
  Startup Archive (@StartupArchive_) reported 35 minutes ago

  Dropbox founder Drew Houston on why distribution is more important than product LinkedIn founder Reid Hoffman wrote in his book Blitzscaling: "Many people in Silicon Valley like to focus on building products that are, in the famous words of the late Steve Jobs, "insanely great." Great products are certainly a positive, but the cold and unromantic fact is that a good product with great distribution will almost always beat a great product with poor distribution." Dropbox is a great example of this. As Dropbox founder & CEO Drew Houston explains, great distribution is ultimately how they beat out dozens of competitors with similar product offerings. Drew believes that too many startups overlook the importance of great distribution. Dropbox had a great product, but it succeeded because of its great distribution. They used a combination of organic virality (users shared files with nonusers) and incentivized virality (Basic account holders get 500 MB of extra storage per user they refer; Pro account holders get 1 GB) to grow. Virality helped Dropbox double its 100,000 users at launch to 200,000 users just ten days later, then skyrocket to one million users just seven months after that. An important caveat though: if your distribution strategy focuses on virality, you have to make sure you solve retention first. Bringing new users in through the front door doesn't help you grow if they immediately turn around and leave. According to Drew, Dropbox discovered this truth the hard way, when activation rates revealed that only 40% of the people signing up were actually putting files in their Dropbox and linking them to their computers. As Drew partially explains in the clip, the early Dropbox team went on Craigslist and offered $40 to anyone who'd come in for a 30-minute usability test. They asked these people to go from a Dropbox e-mail invitation to sharing a file with another email address. Zero of the five people tested succeeded--they didn't even come close. This stunned the team. So they made a list of 80+ things in an Excel spreadsheet and sanded down all of the rough edges in the experience. They soon watched their activation rate climb and left the competition in the dust as they marched on to a $9+ billion market cap. Source: @ycombinator (Feb 2017)

• 
  Dan Holzrichter (@dholzric) reported 42 minutes ago

  @JoshuaKhane This is why i have primary copy on my home system, backup on local server (raid array of old hd's), and copies on google drive and dropbox for anything important.

• 
  Arthur "lynch mob" van Pelt 🔥 ∞/21M ⚡ (@Arthur_van_Pelt) reported 47 minutes ago

  @laz1m0v @adam3us You want a multifunctional database. Go try BSV or Microsoft SQL Server or Arweave. They have what you want. Bitcoin is money. Not a Pepe Dropbox. Go take your Pepes elsewhere, please. Then we wouldn't even need filters if everyone behaved in the spirit of Cash instead of Pepe.

• 
  Ilya Sandoval (@ilya_sandoval) reported 48 minutes ago

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

• 
  Joo Tat (@heyyyjoo) reported 49 minutes ago

  @kozerafilip @joinsauna @newitemco Here’s my main first impression of Sauna: I don’t see a clear winning use case yet. At least from my perspective, Sauna currently feels like a broad AI layer on top of the apps you already use. It can suggest what to do, help find information, and has a multiplayer/collaboration angle around understanding what other people are doing. But I don’t yet see the specific use case where Sauna is clearly much better than existing alternatives. For an early product, I think it would be useful to have a sharper wedge: a specific group of people, in a specific situation, with a painful problem where existing solutions are poor, and where Sauna is obviously the better answer. Maybe that wedge already exists, but as an outsider looking at the website and demo, it is not immediately clear to me. This feels especially important because Sauna asks users to overcome a meaningful amount of friction and anxiety. To unlock the value, users may need to connect sensitive apps like email, Slack, and Notion. If the multiplayer value is important, they may also need to convince teammates to connect their own sensitive apps. That creates a big trust and coordination hurdle, so the value proposition needs to be extremely clear before people will make that jump. One analogy I think about is Notion. Notion is now a very broad horizontal product: people use it as a CRM, Jira alternative, team wiki, notes app, etc. But early on, I believe it had a much simpler starting point: document and knowledge organization. The product and communication was focused on a better way to store, structure, and share notes and docs compared to alternatives like Google Drive, Dropbox, or scattered documents. People could use it for their own notes and documents first. Then, when they eventually shared a page with colleagues, those colleagues could immediately see the value because the page was easy to navigate, clear, flexible, and beautiful. I wonder what the wedge could be for Sauna. I noticed that the Solutions page seems to heavily feature Sauna in Slack, as an assistant that has access to shared context. Is that something that has been resonating better with users? One possible wedge could be someone who is overwhelmed by Slack because they have too many messages and threads to respond to. They could drop their personal assistant into a channel to help reply on their behalf, using context shared with Sauna, and escalate when it is unable to answer confidently. That might also create an easier mental model around access: the personal assistant in Sauna has access to more private context, while the team-facing assistant in Slack has more limited, scoped access. From there, if colleagues see the assistant working and want their own, that could be a natural path into the multiplayer or “*** main branch” idea. Individual assistants could start to merge shared context and provide better help, suggestions, and coordination over time. I’m not sure if this is the right wedge. The answer may already be visible in the product’s usage patterns: who is sticky, what they are using Sauna for, and where they are getting repeated value. But I think the key question is: what is the specific initial use case where Sauna is not just useful, but dramatically better than the alternatives? Once that is clear, I think the product / website / demo should make that use case extremely obvious to the users who need it. (Btw I'm speaking with Ryan tmr regarding the PM role. Which was what led me to explore Sauna as part of my own research. Thought I might as well share my first impressions here)

• 
  Orewin1990.bsky.social (@Yoshiwi2) reported 51 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

• 
  EchoMind (@ai0echomind) reported 52 minutes ago

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

• 
  Harman (@itsharmanjot) reported 54 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.

• 
  QuixoticMoose (@QuixoticMoose) reported 55 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.

• 
  Hugo Bowne-Anderson (@hugobowne) reported 55 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!)

• 
  Suburban Cyber Technologies (@suburbancyber) reported 58 minutes ago

  Shadow IT used to be "someone installed Dropbox." Now it's "someone connected our CRM to an AI agent without telling IT." Same problem. Different speed. Time to update your governance playbook. That's what I am having to do every couple weeks now it seems. #ITLeadership #CyberSecurity #EnterpriseIT