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	2 months 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:

• 
  ScarcityMan (@ScarcityMan) reported 5 minutes ago

  You might not believe it, but it is in fact happening, because it increases the cost, time, and difficulty of running a node. "Large" is a matter of opinion, but is clearly a quantity which would add up over time and have an impact. Why don't you want nodes to be as easy to run for people as possible, so that the maximum number of people can participate in the network, making it more valuable and more resilient? Why is that not something you want, to the extent that you will spend time arguing against it? What exactly is your stake in nodes being more difficult to run than they need to be? Why don't you care about spam? Why don't you care that it obviously, as it does everywhere it exists, degrades the quality of the thing being used? Why do think bitcoin will just be fine and go on forever while watching it transform into a poor imitation of dropbox? Why would anyone interested in bitcoin as money continue to use it when it becomes more and more infested with non-monetary data? Why don't you care about the possibility of truly bad stuff ending up on chain until the end of time? Do you think Satoshi made a mistake? Should he have created "Bitdata" instead? Do we not need to fix the world's money? You good with USD or whatever else is inflating away to nothing? So many questions that will never be answered...

• 
  Om Modi (@ocmodi21) reported 8 minutes ago

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

• 
  mskah🔞 (@mskah_t) reported 10 minutes ago

  I got in touch with the system administrator, and they were able to resolve the issue. It turned out that the problem was caused by an update to the connected Dropbox account.

• 
  Manoj (@HeartofManoj) reported 10 minutes ago

  One backup is never enough. If you run a website, keep a copy somewhere outside your hosting account. Free options: • Google Drive • Dropbox • OneDrive • GitHub (for code) • Local external drive Your backup is useless if it's stored on the same server that crashes. Happens more often than you'd think. #WordPress #WebHosting #Backup

• 
  quantzoid (@quantzoid) reported 12 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?

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

• 
  Some guy (@ibesomeguy) reported 19 minutes ago

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

• 
  Cane Allesta (@caneallesta) reported 22 minutes ago

  Your password manager has never actually managed anything. It just nagged you. That changes with iOS 27. At WWDC26, Apple announced what might be the clearest example of agentic AI shipping in a consumer product this year: the Passwords app, combined with Apple Intelligence and Safari, can now autonomously navigate to a website, sign in, change your weak or compromised password to a strong one, and save the new credential back to the vault all triggered by a single tap. A Live Activity indicator appears on screen so you can see it working, but you don't have to do anything else. The word "agentic" is doing a lot of work right now in the industry, often covering vague multi-step demos that never quite ship. Apple's move here is different because it's not broad automation it's surgical. The Passwords app already flagged weak, reused, or breached credentials, so the AI layer had a clearly scoped problem to solve: remove the friction between "you know your password is compromised" and "you actually changed it." That gap was enormous. Most people never close it. The competitive context makes this sharper. Google has been shipping Gemini's agentic features on Galaxy S26 and Pixel devices since early 2026, handling cross-app tasks like ordering food on Uber Eats or booking rides in Lyft broad, flashy, and currently limited to a short list of supported apps. Apple's answer is narrower on paper but arguably lands harder because it touches something every single user has: compromised passwords sitting in a list they've been ignoring for months. What Apple is really doing here is establishing trust in an agentic pattern before asking users to hand over bigger tasks. If your phone can autonomously change your Dropbox password without you watching every click, and nothing goes wrong, you're psychologically a lot more comfortable when it eventually offers to autonomously book a flight or fill out a form. It's the same trick that got people comfortable with Face ID start with something small where the upside is obvious and the downside is contained. The feature ships with iOS 27, iPadOS 27, and macOS 27 this autumn, with developer betas available now and public beta expected in July. For the password manager space 1Password, Dashlane, Bitwarden this is a quiet alarm. Apple just made "auto-fix compromised credentials" a native OS feature. Good luck charging $3/month for that. #WWDC26

• 
  The Tech Buzz (@tbuzzdaily) reported 25 minutes ago

  $15M raised: Meticulous grew ARR 5x in a year testing code nobody has time to review manually anymore Chemistry led the Series A, joined by Menlo Ventures, Lachy Groom, and GitHub's former CEO Jason Warner. Founders Gabriel and Quentin Spencer-Harper, brothers with backgrounds at Dropbox and Palantir, built the company around a problem AI coding tools created faster than they solved: code is now written faster than humans can review it. The product records real user and developer sessions during development, then uses AI to auto-generate and maintain end-to-end visual regression tests based on actual observed usage, updating automatically as the code changes. Customers include Notion, ElevenLabs, Dropbox, and Wiz, a list that skews toward companies shipping fast enough to need this. Rainforest QA and Autify compete in AI-assisted testing broadly, but most rely on hand-written test cases rather than tests derived from real session data. The tradeoff Meticulous accepts is that session-derived tests can still miss rare edge cases nobody happened to trigger, which is why the company is expanding from frontend into backend and performance testing next. A 5x ARR jump in a year says enough teams have hit the same wall: AI writes code faster than any QA team can keep up with by hand.

• 
  Chris | Founder Advisor (@automateitup) reported 25 minutes ago

  Problem: I didn't have where to save useful links, because my main pc isn't always on. Solution: Told Hermes on my minipc, which is always on, to save the links which I send to a file in dropbox. Then, I told Hermes from my main pc to make a cronjob to check that file every day at 9 am and save the links in their respective category in the dashboard.

• 
  hiverot (@amusudan) reported 28 minutes ago

  @cowboyshibuya Thanks for the reply! I'm not the most organised, and Ill usually just work on whatever is fun (Or a prerequisite for something that's fun to work on), but I do keep track of ideas, and create todo's and pipelines for things I am sure I want to add or test. For random ideas and todos I use a lot of lists (Dropbox paper, random text files, Notion, Notes app on my phone, Google Docs, etc). And for specific pipelines I use Google Sheets to keep track of what has been done per asset or map or gameplay mechanic (For example my guns spreadsheet has columns for animations, sounds, textures, etc). Big picture design and planning is all on paper in various notebooks and my Calendar app. I don't really track bugs now I just fix whatever pops up when playtesting.

• 
  Kirby (@StewartKirbyTNP) reported 30 minutes ago

  @Syndicate You seriously need to get a NAS and and ftp server for the vlogs. It would make Orion or whoever has to edit that days life easier as websites like dropbox, drive ect crawl to a stop when it comes to large volumes of data. An FTP server goes WHEEEEEEEE

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

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

  Interviewer: design Dropbox file sync. I paused and asked what they meant by sync. Whole product? Or just the client protocol? Single user? Team shares? Offline edits? Large files? Mobile on spotty networks? End to end encryption? What’s the SLO for conflict rate and time to converge? Once we scoped it to single-user sync across devices with offline support, I wrote requirements: detect changes, upload deltas, download updates, handle conflicts, resumable transfers, and don’t melt the battery. Non-goals: shared folders and fine-grained permissions. APIs and data model next. I used a file ID stable across renames, plus per-file version and per-device cursor. Client calls: /changes?cursor=..., /upload_session/start, /upload_session/append, /upload_session/commit, /download?file_id&version, /ack?cursor. Server tables: file_metadata(file_id, user_id, path, type, size, content_hash, current_version), file_versions(file_id, version, blob_ref, created_at), device_state(device_id, user_id, last_cursor), and an append-only changelog(user_id, seq, file_id, version, op). Architecture: client has a watcher, a local state DB, and a sync loop. It batches changes, computes chunk hashes, uploads missing chunks, then commits a new version. Server side: metadata service, blob store (chunked, content-addressed), and a per-user change log that devices long-poll or stream. Push notifications help, but the cursor-based pull is the truth. Scaling: shard by user_id for metadata + changelog, store blobs in object storage, cache hot metadata, and keep uploads on pre-signed URLs so the metadata tier doesn’t become the data plane. Chunking makes big files resumable and dedupe-friendly, but it adds CPU and more metadata reads. Tradeoffs I called out: last-writer-wins is simple but loses intent; per-file version vectors are heavier but reduce false conflicts. Chunk size is a fight: 4MB reduces round trips, 1MB retries faster on bad networks. Long-polling is cheaper than WebSockets at scale but slower to react. Failure cases: client crashes mid-upload, so upload sessions must be idempotent and garbage-collected. Network ***** cause retry storms, so exponential backoff + jitter and server-side rate limits. Two devices edit offline, so create conflicted copies and surface it in the client. Silent data corruption, so verify hashes on every download and run background repair. Rename vs edit races, so operations are applied against file_id, not path, and changelog ordering is per user, not global

• 
  Liam (@LJ1101234) reported 33 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.

• 
  Jeff Preshing (@preshing) reported 38 minutes ago

  What's the point of using smarter models if "smarter" means 10% better at finding obscure bugs and having a sassy attitude? Most of the true productivity gains that coding agents have to offer, which are finite, can be obtained using open-weight models for literally 1/100 of the price. The catch is that you actually need to understand the code you are working on. At the same time, I still think there's a viable business serving proprietary models. People are willing to pay for Dropbox even though FTP is free, and it's nice to throw a tough problem at a stronger model occasionally (if intellectual property limitations allow it). Plus, there's a whole frontier productizing this stuff. Unfortunately, Anthropic is currently in the business of spreading tall tales about future improvements, then shaking down enterprise customers. Most of it is based on 2010s LessWrong posts full of category errors, some of which I remember reading back in those days. And their recent hostility toward users in the name of safety is a result of the same ideological recklessness.

• 
  Taka (@takanola) reported 38 minutes ago

  why can't @Dropbox stayed sign in anymore?

• 
  SMART GrowthSystems 🕸 (@H2Wealth365) reported 39 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.

• 
  Sahil Handa (@sahilhandapanda) reported 45 minutes ago

  I'm convinced this kind of environment-setting is even more important online. The digital equivalent of swapping a cassette in a studio is stopping to go hunt down a file in Dropbox or Drive.

• 
  Weird Darkness®️ (@WeirdDarkness) reported 46 minutes ago

  Dear @Google and @YouTube... My account has been hacked, and not only have I lost my Gmail, YouTube, etc., but I've also lost access to my Dropbox that has my full life in it, health records that I used Google to login to, etc. I signed up for Google Account Protection, but it did not protect me. Somehow, even after setting up brand new 2-factor authentication just a few weeks ago, they hacked in, changed EVERYTHING, and now my life, career, and health are at a standstill. I desperately need somebody to contact me. All options I've tried to regain access to my account have failed because everything has been disconnected.

• 
  joshpuckett (@joshpuckett) reported 46 minutes ago

  @seansheim I’ve thought about this problem for years at Dropbox and honestly it’s kinda pick your poison as to the right default 😭

• 
  Karus Daedlyn *Cat Dad Era* (@CDaedlyn) reported 47 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.

• 
  CHRISTOPHER BLAZ✨ (@Blaz_Dao) reported 48 minutes ago

  Walrus 🦭 and Walrus Memory explained in a lay man's understanding. Let's dive in: 1. What is" Walrus🦭" ?? Firstly, I want you to think of Walrus as a gaint decentralised hard drive built on Sui protocol or ecosystem. Walrus is trying to become the decentralized version of cloud storage services like Google Drive, Dropbox, or Amazon S3, but built for Web3. In a simple analogy, think of it like this; Google Drive vs Walrus With Google Drive, your files are stored on Google's servers and Google controls the storage. If Google removes a file or service, you're dependent on them. But, With Walrus🦭 it's a different case as your files are split into many pieces. Those pieces are stored across many independent storage providers in a cheap manner as no single company controls all of your data. And the most fascinating thing is as long as enough storage providers remain online, your files can be recovered whenever you want. 2. What is "Walrus memory"?? In plain English, Walrus memory is simply the storage space used to keep data on the Walrus network. That data can be:Images, Videos, Documents, NFT media, AI datasets, Website files, Backups etc. Why does it matter? Imagine a viral meme image on Sui. Normally, the blockchain only stores a reference to the image because storing the image itself would be too expensive. Most blockchains are good at storing transactions but terrible at storing large files. @WalrusProtocol is designed to store large amounts of data cheaply while remaining decentralized. ~BlazCares

• 
  Polsia (@polsia) reported 49 minutes ago

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

• 
  ṢƘĪÑlÖVẸ́R̃ṢX🇺🇲🌷 (@skinloversx) reported 49 minutes ago

  Hey Daddy I'm down for FaceTime 💧 Dropbox and all kind of nasty content message me for menu 💦💦 #md

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

  @JohnLaMacc What voter fraud? What Dropbox problem?

• 
  Jack (@jacklandas) reported 57 minutes ago

  alibaba banning claude code over backdoor fears is the new "no dropbox on company laptops" every big corp security team is about to have a list. cursor approved, claude code not. windsurf maybe. this fragmentation is going to be a real problem for devs who just want to ship

• 
  Sol!A3800 (@SolA3800) reported 58 minutes ago

  @Dropbox I have loads of upload problems with Dropbox, scarce access to customer support inside the app, whilst when trying to get customers support from outside the app, the information says get customers support from inside the app. Have paid £19.99 for more than a year with little use benefit of the service, am considering closing the account.

• 
  Girish Kotte (@gkotte1) reported 58 minutes ago

  In 2009, Dropbox ignored every rule about SaaS launches. No ads. No cold outreach. No sales team. One stupid idea: a 3-minute demo video for a product that didn't fully exist yet. It generated 75,000 signups overnight. ----- Insight 1 - Simplicity converts better than features Show people one clear outcome. They sign up before the product is ready. Insight 2 - The best growth doesn't look like growth A demo video isn't a campaign. Which is exactly why it worked. Lesson 3 - Ignore conventional launch advice "The opposite of a good idea can also be a good idea." - Rory Sutherland Every advisor said: build first, market second. Dropbox marketed first. Then built. We now see founders obsessing over perfect MVPs before showing anyone anything. The problem: You ship clean code nobody sees. The solution: You ship a clear story first, then the code catches up. I use Postwyse to build that story in public before the product is ready. Perception opens doors. But shipping closes them.

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

  “You still use pull requests? I wouldn’t even do that anymore. Just push it straight to trunk, have your agent summarize it.” That’s @gregce10, co-founder and CPO of SpecStory. He previously worked at GitHub, Dropbox and Google, and was CPO at Pluralsight. And he kept going: - PRs are the limiting gate when agents produce more code than humans can review. - The model should never decide when its own work is finished. Put the deterministic checks somewhere it cannot access. - *** is probably here to stay. Whether GitHub remains the platform, “we’ll see.” @HanchungLee came at the same problem from the evaluation side. Han is Director of Machine Learning at Moody’s and works on SkillsBench, evaluating skills across combinations of models and agent harnesses. - An agent is the model plus its harness. You need to evaluate the complete system. - A green check proves nothing if the agent found a way to game the task. - Your agent could delete the failing test and declare success. Both are figuring out how to turn masses of agent-generated slop into signal. Greg mined 516 saved agent sessions to recover the decisions and intent behind the work, identify recurring practices, and forge the ones he approved into reusable skills. Han runs skills inside controlled environments, grades the result, and preserves the complete trajectory so we can inspect what the agent actually did. Preserve the intent. Inspect the trajectory. Verify the result. Turn what works into skills. Full episode in the replies 👇