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	3 months ago
Bogotá	Website Down	3 months ago
Auxerre	Errors	3 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:

• 
  Hawk (@iamhawkspire) reported 11 seconds ago

  @TheMilitiaGamer @Google nah lol, i'm just rawdogging without any online backups for my larger files atm. might end up checking out dropbox, tho their speeds are super slow on my end.

• 
  bayleigh | HEARD BABYLON 💙 (@eternalwarnings) reported 2 minutes ago

  sorry it's boofed quality my Dropbox account was not working so I had to ss for the time being

• 
  Palpy (@evgenij_rabij) reported 5 minutes ago

  A 32 YEAR OLD PRAGUE DEV BULK-BUYS $180 CHINESE NAS BOXES AND NOW PULLS $7,200 A MONTH SHIPPING PRIVATE DROPBOX-KILLERS TO EU FREELANCE DESIGNERS While massive brands scramble to lock teams into clunky, data-mining cloud databases, this creator built a private intelligence system that secures sensitive data and brings in a massive stream of passive revenue every single month. He makes a steady $7,200 every single month by building and configuring private cloud and AI indexing hardware for EU freelance designers who want to escape subscription traps. The entire micro server fits right on the corner of a desk and runs on an ORICO metabox HS200 pro unit. This tiny sliver of hardware packs an Intel N100 processor, 8GB DDR4 RAM, and pumps out local cloud performance on a machine the size of a coffee coaster. Instead of letting his clients burn cash on recurring cloud storage retainers, the engineer pairs the board with two refurbished 30TB hard drives in RAID 1, pre-installs the software, and sells the complete physical package at a premium. Pause at the 0:02 mark in the video where the drive slides in: that is a sleek metallic chassis hosting a $1,000 mini-NAS holding 30TB of encrypted client data. The core value proposition of this setup comes down to absolute data privacy, zero monthly fees, and strategic scalability. Mainstream cloud providers like Dropbox Business can never offer this level of value because they bill €2,400 a year for the same storage tier while uploading private user files to external cloud networks. Here, the ORICO metabox pulls off the entire magic trick locally inside the office. Running on Ubuntu Server 24.04 and MinIO S3-compatible storage, the system automatically triggers a local Qwen 2.5 VL 7B model to run localized RAG pipelines directly over the user's PDFs and Figma exports. Through this custom setup, designers get access to lightning-fast local cloud storage, zero third-party data tracking, and a smart visual search assistant built right into their private drive. This case study is a textbook example of how accessible hardware combined with a smart setup service can unlock unique niche products that solve real human problems, and you can catch the full assembly pipeline in the video below.

• 
  Kieran 🥃🎶🐇 (@KGeorgee) reported 5 minutes ago

  @datarade NET? Probably region of 45% 5k+ companies now? Not all are exits or in cash yet will be propped up a lot on Stripe dropbox doordash coinbase if we go gross probably close to 70% by now? Some bad perfromers in there of course too that will bring it down. nuts figure ngl

• 
  Google Account (@hanzala_007) reported 8 minutes ago

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

• 
  Igor Trunin (@igortr_) reported 10 minutes ago

  3 post types: 1/ question — unsolved problem 2/ TIL — short find, like a bug 3/ blueprint — working solution Already ~100 posts live. Most are TILs. Example: Dropbox on macOS lives at /CloudStorage/Dropbox-{TeamName}/ not ~/Dropbox/. small but genuinely useful

• 
  David Crysler (@DavidCrysler) reported 11 minutes ago

  An ops manager pushed back on adding a new tool: "We've got stuff on ShareDrive, Dropbox, OneDrive, Slack... you spend more time trying to figure out apps than actually doing work." He's not wrong to be skeptical. Every one of those tools was supposed to fix something. Tool skepticism is almost never about the new tool. It's about the last five. Tools may treat your symptoms but rarely solve the actual problem.

• 
  FiL Dev (@FiLHashDev) reported 12 minutes ago

  I’m hesitant to work with Jira again. Co-Founder wants it. My issue is that we don’t have a source of truth. Two brains, agents, & knowledge bases, leaves room for a lot of drift. Any suggestions? I’m thinking GitHub read only repo access might be the vibe. We also use Dropbox sync for artifacts. I just think a third central brain = more tokens and more drift. Might just have to build a full AgentOS.

• 
  Nav Toor (@heynavtoor) reported 16 minutes ago

  Setting 4: Kill background login items. Open System Settings → General → Login Items & Extensions. Look under "Allow in the Background." You'll see 15 to 40 items running constantly. Dropbox helpers. Google updaters. Microsoft Teams. Adobe Creative Cloud. Toggle off anything you don't use every day.

• 
  The Open Web JP (@TheOpenWebJP1) reported 16 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.

• 
  MarkyX 🌹 MafiaBlitz.com (@Marky_X_) reported 20 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.

• 
  ؘ (@sylusisms) reported 23 minutes ago

  once this issue with my photo album is fixed im saving every single one and adding on google drive or dropbox

• 
  Abdullah (@abdinmotion) reported 24 minutes ago

  One video. $48 million in revenue. No ads spent. That's the Dropbox story and most product teams still haven't learned from it. Here's what actually happened: Dropbox had a technically brilliant product that no one understood. Instead of adding more features, they made a 2-minute video that showed *exactly* what the product did. Simple. Specific. Human. Signups went up 10% overnight. Big companies spend millions refining their product. Then they describe it in six bullet points on a landing page and wonder why the sales cycle takes forever. The product video isn't marketing. It's compression. It compresses trust, clarity, and desire into 90 seconds. If a user can't understand your product in a video, the product isn't the problem. The story is. When was the last time you watched your own product video as if you were a first-time user?

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

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  Santiago Bustelo (@sbustelo) reported 27 minutes ago

  @DropboxSupport More details? “I am really sorry for any inconvenience this is causing. We'll update you shortly on this issue.    In the meantime, please let me know if you have any further questions.   Best regards,  Jesse | Advanced Support” That’s the “support” I’m getting. FULL REFUND NOW

• 
  Ayaan 🐧 (@twtayaan) reported 30 minutes ago

  Steve Jobs told Drew Houston that Dropbox was a feature, not a product. Dropbox is now worth $8 billion. In 2007 Drew Houston was a 24 year old MIT student who kept forgetting his USB drive. So he built Dropbox. Within a year Steve Jobs called him into Apple HQ. Apple wanted to buy Dropbox and shut it down. Houston said no. Jobs told him directly that Dropbox was a feature, not a product, and that Apple would build it themselves. Apple launched iCloud in 2011 specifically to kill Dropbox. It did not work. Dropbox crossed 100 million users in 2012. Then 200 million. Then 500 million. Apple tried again. iCloud Drive in 2014. Same result. Then the enterprise market shifted. Slack, Notion and Google Drive carved up Dropbox's user base from every direction. Revenue growth slowed. The stock dropped 50% from its IPO price. But Dropbox never died. Today 700 million people have used it. 17 million paying customers. $8 billion valuation. Still independent. Still running. Steve Jobs built a trillion dollar company. He called Dropbox a feature. The feature outlasted him and two attempts by Apple to replace it. Drew Houston never forgot his USB drive again.

• 
  Flandermaxx (@Flandermaxx) reported 30 minutes ago

  A 32 YEAR OLD PRAGUE DEV BULK-BUYS $180 CHINESE NAS BOXES AND NOW PULLS $7,200 A MONTH SHIPPING PRIVATE DROPBOX-KILLERS TO EU FREELANCE DESIGNERS vojtech is 32, prague vinohrady flat above a pivnice, ex-JetBrains backend eng, sources ORICO metabox HS200 pro enclosures from a shenzhen aliexpress-parallel channel at $180 per unit plus 2x WD 30TB HDD refurbs at $410 each ORICO metabox HS200 pro (intel N100 · 8GB DDR4 · 2x 30TB WD in RAID 1 = 30TB usable) · ubuntu server 24.04 · minio S3-compat · qwen 2.5 VL 7B for local RAG over the user's PDFs and figma exports pause at 0:02 on the HDD sliding in, that is a $1,000 mini-NAS holding 30TB of encrypted client data that dropbox business bills €2,400 a year for the same tier 84 EU freelance designers pay him €78 a month each for a shipped pre-configured NAS + qwen RAG endpoint, €6,552 = $7,200 MRR at 71% margin $1,000 BOM per unit, €12 monthly prague power for the burn-in bench, first 20 units flipped covered his tooling and packaging, no dropbox no google drive business while ORICO still white-labels the metabox before EU distributors mark it up 3x, follow and bookmark

• 
  Spencer Baggins (@bigaiguy) reported 31 minutes ago

  SOMEONE BUILT A GITHUB REPO THAT TURNS TELEGRAM INTO UNLIMITED CLOUD STORAGE. 100% free. It is called UnlimCloud. Self-hosted-ish desktop app. Open source. Uses Telegram as the storage layer. You log in with your Telegram ID. Upload files. Download files. Organize folders. Manage pictures and videos in a gallery. That is it. No Google Drive upgrade screen. No Dropbox “you are out of space.” No iCloud begging for $2.99/month. No random startup holding your files hostage. Your Telegram. Your files. Your storage. Here is the full feature set: ↳ Uses Telegram as the backend storage layer ↳ Secure login with your Telegram account ↳ Upload, download, and organize files ↳ Folder-based file management ↳ Gallery for photos and videos ↳ Clean desktop app interface ↳ Built with Tauri ↳ Windows release available ↳ macOS and Linux coming soon ↳ MIT licensed ↳ Open source 885 GitHub stars. 125 forks already. Here is why this matters: For years, cloud storage companies trained everyone to rent space for their own files forever. Photos? Pay. Backups? Pay. Large folders? Pay. Team storage? Pay more. UnlimCloud is the opposite idea. Take an app people already use every day. Telegram. And turn it into a private cloud drive with a clean file manager on top. No storage subscription. No SaaS dashboard. No “pro” plan. Just a weird, useful, open-source hack that feels like it should not work this well. Built in HTML + Rust. MIT License. 100% Open Source.

• 
  Jeff Preshing (@preshing) reported 32 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.

• 
  Nikolay Konovalov (@br11k_dev) reported 32 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...

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

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

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

  System design question. How would you design Dropbox file sync with conflict handling? Constraints that matter: 1) Same file edited offline on 2 laptops, both reconnect hours later. No central lock. What wins, how do you surface conflicts, can you auto-merge for some types? 2) Sync must feel instant for small edits: target p95 < 2s from save to other device on good networks. 3) Files up to 10GB. Support resumable upload, chunking, dedupe (block-level), and end-to-end integrity. 4) Must work across flaky networks, NAT, and clock skew. You cannot trust client timestamps. 5) At-least-once delivery of change events. Idempotency required for apply/ack. 6) Millions of clients polling/streaming. Avoid a thundering herd after an outage or deploy. 7) Rename/move storms and folder deletes. Preserve history and allow restore without corrupting sync state. 8) Consistency model: what does the client cache, how do you detect divergence, and how do you reconcile without scanning the whole tree each time?

• 
  Some guy (@ibesomeguy) reported 49 minutes ago

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

• 
  Urooj (@Urooj978) reported 49 minutes ago

  That old laptop gathering dust in your closet can replace every cloud subscription you pay for. ​• Netflix • Google Photos • Dropbox • 1Password ​That’s over $500 a year to rent things you used to own. ​Enter CasaOS—a free, open-source system that turns any old laptop or mini PC into your own personal server. ​No Linux skills. No code. No weekend-long tutorials. ​You run one command. In 30 minutes, you get an iOS-like dashboard where you can install self-hosted apps in one click: 1/ ​Jellyfin → Replaces Netflix 2/ Immich → Replaces Google Photos (with facial recognition) 3/ Nextcloud → Replaces Dropbox 4/ Vaultwarden → Replaces 1Password 5/ AdGuard Home → Blocks ads on your entire Wi-Fi network ​Setting up a home server used to be a nightmare. CasaOS makes it feel like installing apps on an iPad. ​The laptop you forgot about is more powerful than the servers that ran most websites in 2008. It costs $0, it’s already in your house, and it puts $500/year back in your pocket. ​Your closet is your new data center.

• 
  2Do (@2DoApp) reported 49 minutes ago

  @PhilipLeworthy The Android app is going to unfortunately remain on CalDAV + Dropbox sync for now. I'll be updating it to fix a few issues as well as Tablet related compatibility issues but not major features planned. It remains functional the way it is albeit with a few limitations.

• 
  Suburban Cyber Technologies (@suburbancyber) reported 54 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

• 
  Om Modi (@ocmodi21) reported 56 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. 🧵

• 
  Valentin.exe (@PujaMak0302) reported 58 minutes ago

  @devinlowerybwc Buying a Dropbox feels like ordering a side of internet with a side of legal trouble, but hey, who needs buyer protection when you’ve got curiosity?

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