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.

• Sign in (40%)
• Errors (40%)
• Website Down (20%)

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	3 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:

• 
  Shawna Canon (@ShawnaCanon) reported 6 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.

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

• 
  Peter Lake (“world’s anonymous singer songwriter”) (@PeterLakeSounds) reported 8 minutes ago

  @taobanker I might suggest another question: what should you avoid? In that context the multi-trillion dollar bet will have terrific returns. That also means that the money making machines of US won’t accumulate money and accrue value unless there is persuasive evidence that at least the big spenders on data center capex get their money back. Given this is unknown, I assume markets are skeptical. If the largest companies in S&P and all the rest don’t have excess free cash, and plausible they don’t go up a lot. That would yield maybe an on average flat market. The flip side is that models are open, massive parameter models getting quantized will be in windows machines. Silicon Valley and early adopters are doing fascinating things. But for the rest of us, I need nice and simple. And for the first time we’ll have good old home computers that can do the job and with that comes free use from heaven. Outside of specialized discussions people don’t know much about what to do with this. The jardon doesn’t help: context window? Quantized models? Nodes are not parameters, they are like neurons, and AI is so dangerous, but not it’s not…what a world! The really final blow is government intervention now makes it a sovereign requirement for companies to have their own AI. LASTLY! I’ve been thinking about the data holders. box. Dropbox etc. Absurdism and it’s comparables will become a bigger deal as people start to realize they the context “window” = the files and stuff you want it to analyze = can only handle so much Imagine of Box or Drop box had a button that converted all your stuff in MD files or the like? Then it’s show time. The companies that hold data may be more valuable than I realize. Conclusions based on the above speculation: 1) could this impact demand at the data centers? Sure it can. I know tech investors like to hold out their hands palms out and say…something vague and qualities. Yes, data centers are more sophisticated etc. Yet here I was doing some interesting work on a FREE local model, my “dark tokens” are someone else’s lost revenue! How does this math work? No clue. It is telling, however, that NVDA and AMD are committed to local machines. No large company wants model dependency anyway, due to data concerns. 2) Finally I have a great reason to buy a slick cool PC! The higher end stuff will not be throttled down in local because I’m seeing a bunch of them coming our way that will have decent “bandwidth” RAM in addition to high system ram. We’re going retro and this tech is moving so fast. Adoption will increase once you have super good local models on your laptop. …Im falling asleep, but the gist is that the data centers were already speculative, and now we a lineup of expensive but sweet computers running on windows that gives you infinite and faster foundational level stuff.

• 
  Long Long Int (@LongLongInteger) reported 10 minutes ago

  Topic 7: Checksum: ========= Input Data -> Cryptographic hash functions like MD5, SHA-1, SHA-256, SHA-512 -> fixed size string is called checksum Checksum is used for checking data corruption during data transfer/upload Can be done both client-side and server-side Advantages of client-side checksum: =========================== -Detect data corruption during transmission -Resumable downloads (only after checksum match for each chunk, we mark that chunk as uploaded) -Deduplication before upload -Companies that do: Youtube, Google Drive, S3(optional), Dropbox Advantages of server-side checksum: ============================ -Verify storage integrity (to check disk corruption, large systems periodically check files) -Deduplication inside storage -Replication verification -Companies that do: Local file backup software, Dropbox, Google Drive, Youtube

• 
  MarkyX 🌹 MafiaBlitz.com (@Marky_X_) reported 11 minutes ago

  For the curious, quite a few publishers won't send anything to Canada because our shipping is insanely expensive. It's been such a problem for the past two years that I got a US dropbox, which isn't exactly a free service.

• 
  Sasha Sage (@SSage38676) reported 11 minutes ago

  Most founders confuse awareness with demand. Awareness = people have seen you. Demand = people understand why they need you now. For innovative products, demand doesn’t already exist at scale. You have to create it. Here’s the step process to create demand: 1. Start with a sharp ICP Know who you’re trying to reach, what they already care about, and what pain is urgent enough to act on. 2. Build your positioning from market reality Use customer insight, competitor research, and feedback to define why your product matters now. 3. Reframe the problem Don’t just describe your feature. Teach people to see the problem differently. 4. Build authority through education Consistently publish useful educational content that reinforces your positioning and helps your audience understand the problem, the stakes, and the new way forward. 5. Show the cost of inaction Make the hidden pain visible: wasted time, missed revenue, lost context, poor decisions, slow growth. 6. Prove the new way Use examples, demos, stories, use cases, data, and customer insight to make the shift feel obvious. 7. Capture the demand you create Send people to a clear landing page, retarget engaged audiences, and show up where intent already exists. 8. Test, measure, and improve the loop Track which segment, message, channel, and page actually converts. Then double down. Example: Zapier Most people already knew Gmail, Dropbox, and Basecamp. Almost no one was looking for an "app automation platform." That's missing demand. Zapier created it by: → Making the pain of manual work and apps not talking to each other impossible to ignore → Publishing endless "connect X to Y" content that taught people a new problem → Showing clear examples of time and context lost from switching between tools → Positioning themselves as the missing glue between tools people already used They didn't wait for demand. They built it through education and problem reframing. Don't just get seen. Make the market understand why they need you now.

• 
  JLemmens (@JLemmens_) reported 13 minutes ago

  @mrsgcomics Onedrive honestly was the best one of the filesyncing services I've used over the time but don't rely on that alone if **** hits the fan. Dropbox (2expensive), Mega (2sluggish), Idrive (obsolete), Gdrive (risky+slow unless you use that app but even then), haven't tried Proton.

• 
  Alchemist - τ (@SubnetSummerT) reported 14 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.

• 
  Eric S (@Lazy_Bari_Sax) reported 14 minutes ago

  @retrobike_c16 @themiasandrist Why doesn't the mobile version allow you to upload or download files, though? And why is it so damn slow to update? I'm thinking about changing back to Dropbox, despite it's many issues.

• 
  Oliver Prompts (@oliviscusAI) reported 19 minutes ago

  you pay google, dropbox, and apple $10+/month to store your files on their servers, where they can read them. and dropbox already got breached in 2024. there's a tool that syncs your files directly between your own devices. no cloud, no server, no middleman. it's called syncthing. → real-time sync between any number of devices, peer-to-peer → files go straight between your devices, never touching a third-party server → tls encryption with perfect forward secrecy on every connection → works over lan and internet, no port forwarding needed → file versioning, roll back anything you changed or deleted there is no syncthing server. no syncthing cloud. no company storing your data. the protocol is open, and there's nothing between your devices except an encrypted tunnel. dropbox plus is $144/year. google one 2tb is $120/year. syncthing is $0, unlimited devices, unlimited storage, forever. battle-tested since 2013. run by a swedish non-profit. 100% free. open source.

• 
  Vincent Van Code (@vincent_vancode) reported 21 minutes ago

  Dear @Microsoft you keep strong-arming us to use OneDrive, but it is terrible.. - Stop forcing OnceDrive on us - Dont make it default location You need to fix: 1. Reliability - often doesnt connect (I am on a 1Gbps fibre network BTW) 2. Slow - it is awefully slow 3. Learn from DropBox Good day.

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

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

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

  Asked: design Dropbox-style file sync. Start with requirements: 1) Multi-device, near real-time where possible, offline OK 2) Large files, resume uploads, delta sync 3) Sharing, ACLs, rename/move, delete, version history 4) Consistency target: per-file eventual, monotonic reads per device 5) Conflict policy: last-writer-wins vs explicit conflict copies APIs + model: - PUT /files/{path} (upload session, chunked) - GET /files/{path}?version= - POST /ops (batch rename/move/delete) - Watch/long-poll for changes since cursor Tables: users, devices, file_id, path entries, content_hash, blocks(hash, refcnt), versions(file_id, v, root_hash), change_log(user_id, seq, op) Architecture: - Client computes block hashes, uploads missing blocks to object store - Metadata service commits new version + appends to per-user change log - Notifier pushes cursors to devices (WebSocket/APNS), devices pull diff - Background GC deletes unreferenced blocks (refcnt/mark-sweep) Scaling: - Shard metadata by user_id, keep change log append-only per shard - CDN/object store for blocks, pre-signed URLs, parallel chunk upload - Hot paths: cursor polling, small metadata reads; cache by (user, cursor) Tradeoffs: - Dedupe by block saves $$$, costs CPU and leaks similarity unless salted - Rename is metadata-only if path->file_id indirection exists - Strong consistency needs consensus; most systems accept eventual + conflicts Failure cases to cover: - Network drop mid-upload: upload session + idempotent chunk PUTs - Duplicate notifications: cursor-based pull makes it safe - Device clock skew: use server seq/version, not timestamps - Split-brain offline edits: detect divergent parents, create conflict version - Partial metadata commit: 2-phase between metadata + block refs, or reconcile job

• 
  Akshay Shinde (@ConsciousRide) reported 27 minutes ago

  @jahirsheikh8 The server never guesses. When the upload starts, it creates an upload session with a unique ID. The file is split into chunks, and the server records which chunks have already been received. After reconnecting, the client asks, “Which chunks do you already have?” The server responds with the missing offsets, and the client uploads only those. That’s how services like Google Drive, Dropbox, and S3 multipart uploads resume transfers without starting over.

• 
  Waldemar Santos (@wsantos99) reported 27 minutes ago

  @DropboxSupport Hello, I have already sent two emails regarding a problem I’m having with my account, but I haven’t received any response. How can I get assistance with this issue? Thank you.

• 
  EchoMind (@ai0echomind) reported 30 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.

• 
  Nikolay Konovalov (@br11k_dev) reported 31 minutes ago

  @thekevinjon The only problem is getting zezwolenia na pracę. I was going to interview with Dropbox last week and turns out they are happy to interview me and submit my case to Mazowiecki Urząd Wojewódzki. ... and then wait for 8 months until my case is approved, and I can actually start working. That's a huge deal-breaker for a lot of engineers like myself who are less than 5 years into staying in Poland. I'm on JDG for example. I came by PBH visa back in 2023 legally, and I've been successful since. I earned quite a bit of money and spent it all in Poland, 12% tax + $500 ZUS monthly. But the moment I want to join bigtech and earn even more money for Poland (Dropbox have 300-400k+ PLN base salary for Senior SWE), I'm just denied. Please, please... let the Dobby be free...

• 
  Isha (@VISportsTalk) reported 35 minutes ago

  Is anyone else having issues with @Dropbox today?

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

• 
  yera. (@1stplaceee__) reported 41 minutes ago

  You down for my nasty FaceTime and Dropbox video HMU📨📥💦🍑

• 
  Jan Senderek (@jans) reported 42 minutes ago

  I started journaling at 16. I was heading to Japan and someone told me I'd be grateful if I kept a journal. So I did. And they were right. I loved that I had somewhere to put my thoughts. Somewhere to look back at if I wanted to remember something. Plus I knew I was being thoughtful about my future self. But life got bigger. University, then a career, now a family. More thoughts. More things. The journals had no chance of keeping up. So what changed was the tools. Handwritten journals to Evernote to Dropbox to Obsidian to Notion. Always thinking the next one would be the answer. It never was. Every system asks the same of you. Tag this. File that. Organize here. Review there. Do the work now so that future-you can find it later. And future-you is grateful. That part is true. But your current self carries all of it. The organizing, the maintaining, the constant work of keeping the system alive so that someday it's useful. That burden never lifts. It just accumulates. Your current self and your future self should be working together. Not one doing all the heavy lifting for the other. What if you just put your thoughts down. And trusted they'd be there when you need them. No organizing layer. No maintenance. Just the thinking. So you can truly be your current self.

• 
  Sunkanmi Fafowora (@the_jonin_) reported 46 minutes ago

  @hashnode Thank you! It's back up now. That was so weird. I didn't even receive an explanation as to why it was taken down, but my work is back up now, which makes me happy, but still very cautious without an explanation. I think I'll have to keep using Dropbox in the meantime

• 
  mel 🩷 (@melodyymami) reported 50 minutes ago

  working on uploading, dropbox must be down bc uploads keep failing. i’ve stayed up as long as i could and i’ll try again in the morning!

• 
  Aaron Li (@polymorpher) reported 51 minutes ago

  we probably reached the point where AI is efficient enough to fix most annoying little bugs / missing features in the software we use every day i started reading lots of papers on the move again, and needed to sync folders of PDFs to my remarkable 2 - perhaps the best e-ink tablet for reading, yet nothing about its sync software works: web UI uploads one file at a time, cloud "integration" asks for full access to your Dropbox etc., desktop app SSO login is broken so i made a quick sync app that does the job in one click from the macOS right-click menu - in the same amount of time that 5 years ago would get me halfway through an email to customer support repo in reply

• 
  wigsandtea (@wigsandtea_) reported 53 minutes ago

  Ariana Grande reveals hackers allegedly stole 45 unreleased songs in 2023 alone, including “Fantasize”, “White Tee” and “that b*tch is mine,” in new lawsuit. She also claims they allegedly stole a photographer's Dropbox login details and hacked the phone of one of her producers: “The hackers created a Gmail account and internet domain impersonating the photographer and tricked the technician into sending Grande’s materials to them.” (via @THR)

• 
  Polsia (@polsia) reported 53 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.

• 
  Clawvard University (@clawvardEDU) reported 57 minutes ago

  A skill server is any endpoint an agent can point at to load skills. Sx 2.0's move is showing a Dropbox folder can be one. Drop a skill in, share the folder, teammates load it. No infra on the receiver's side.

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

• 
  Marcus (@marcuslayerx) reported 1 hour ago

  way too many teams in crypto still think they're buying user acquisition when they’re really just paying the same audience to look at another project for a week i’ve spent the last few days looking at products that could actually break out of the crypto bubble and the people they need aren’t sitting on ct waiting to find them - morse is built around freelancers getting paid across borders - blackbird gets people while they’re literally sitting in the restaurant - DIMO’s real path runs through dealerships, insurers and people building with car data - Hivemapper only becomes a real business when companies pay for fresh map data, not because more drivers collect it square put the card reader in the merchant’s hand, dropbox gave people more storage for bringing someone else in, opentable became part of how restaurants took bookings, etc they showed up while the person was already trying to do the thing a lot of teams still open a spreadsheet of kols/agencies to pay before they’ve even worked out where the user is when the problem even happens