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:

• 
  JLemmens (@JLemmens_) reported 3 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.

• 
  🔆 j i k o ⋆₊ ‧ ˚⊹ 🏜️ (@lisey_ann) reported 5 minutes ago

  @joinautopilot @charliebilello I can see why a bunch of those are sagging (joke? Or maybe I'm not joking): - Snapchat is in decline, less users overall. - Streaming subscriptions are becoming too expensive to keep up w/ inflation - X likely sagging ever since its lead advertisers left - Dropbox: user usage declining? (I use Google drive, Mega) - Alibaba: Chinese knockoffs, not bound to survive long - doordash: getting too expensive, way too many fees whenever I've used it, even WITH the discounts - Roblox: declining corporate - Snap: declining user usage, they constantly advertise Snapchat+ and idk anyone who actually uses that - Facebook: meta's side hussles were failing (notable: metaverse shutdown) - coinbase: app is ALWAYS buggy, slow, Base wallet became infested with scam tokens with no way to report, I personally stopped using it for this reason - pinterest: we just have AI to put together mood boards now, Pinterest not needed - Uber: same fee problem as doordash plus majority of gig drivers in my experience are the same few Indian drivers - uipath: likely not keeping up with the AI agent competition - bumble: women are probably tired of it tbh - lyft: same problems as Uber and doordash I can't answer for some others because I'm not as familiar or just can't think of a reason why they have poorer returns, so I dunno.

• 
  Ryan Zygar (@zygar) reported 7 minutes ago

  I am beginning to have issues with Dropbox hanging and my @NousResearch Hermes agent not being able to file @grok build confirmed. This is a new issue for months no issue now my agent filing and following up is hanging up. What’s everyone recommend for data management Mac Mini. This is new. No changes made by me.

• 
  Jack (@jackcoder0) reported 8 minutes ago

  1. Kill the Login Items the apps launching before you even sit down. Every time you log in, your Mac quietly launches 10-25 apps in the background. Spotify. Slack. Zoom. Google Drive. Dropbox. Creative Cloud. OneDrive. Each one consumes CPU and memory before you've opened a single window. System Settings → General → Login Items & Extensions. Review the list. Remove everything you don't need the instant you log in. You can always open them manually when you actually need them. His Mac had 19 login items. He needed 3. He removed 16. Boot time dropped from 2 minutes to 18 seconds. The first few minutes of every session — that sluggish, unresponsive window where nothing works gone.

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 11 minutes ago

  @DropboxSupport Turns out it wasn't normal. Forcing a Rebuild inside of Windows Indexing Options was the fix. Windows Issue. Resolved for now.

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

• 
  . (@Madame_Lucifur) reported 16 minutes ago

  There are some people who feel entitled to have my Dropbox and honestly I don't give a **** how you feel. If there's no transaction in my bank account which leaves your email address then that's not my problem.

• 
  ray🥤 (@rayontrack) reported 17 minutes ago

  bookmarked, downloaded, screen recorded, emailed, stored in hard drive, uploaded to cloud, archived, backed up, shared via bluetooth, forwarded, copied to usb, saved offline, synced across devices, added to favourites, printed, password protected, compressed into zip, renamed, organised into folders, duplicated, exported, imported, attached to message, sent to recycle bin, restored from backup, converted to pdf, edited, highlighted, annotated, watermarked, uploaded to google drive, uploaded to dropbox, shared through airdrop, linked to notes, tagged, encrypted, burned to cd/dvd, cached, mirrored to another device, uploaded to server, queued for transfer, dragged into archive, pinned, added to reading list, stored on ssd, embedded in document, linked in spreadsheet, previewed, sent to printer queue, recovered from trash, and indexed for search.

• 
  Ihtesham Ali (@ihtesham2005) reported 19 minutes ago

  A guy built a free version of Dropbox in 2010. His name is Frank Karlitschek. The project is called ownCloud. He wasn't trying to build a company. He was trying to fix one thing: your files should live on hardware you control, not on a corporation's server. Here's what it actually does. You install it on your own machine, a spare laptop, a cheap VPS, whatever you've got lying around. It gives you file sync, photo backup, calendar, and contacts inside one dashboard. Same core idea as Dropbox, owned by you instead. CERN runs on it. The European Science Cloud runs on it. Entire universities host their file systems on it instead of paying Google or Microsoft by the seat. In 2016, Karlitschek walked away from the project he built and started Nextcloud, chasing the same idea with a new team. ownCloud kept going without him. It's still free, still self hosted, and still running inside labs and universities that never wanted their data anywhere near a company's servers.

• 
  Teja Punna (@punna_teja) reported 22 minutes ago

  Indian Government: "We've blocked Telegram to protect the NEET exam." The Internet: So the problem was... Telegram? Not the people selling fake papers? Not the organised scam networks? Not the thousands of mule bank accounts? Not the hundreds of disposable SIM cards? Not the fake payment gateways? Not the people exploiting students' panic and desperation? Solution: Block Telegram. Meanwhile: ✅ Discord still exists. ✅ WhatsApp still exists. ✅ Signal still exists. ✅ Slack still exists. ✅ Email still exists. ✅ Google Drive still exists. ✅ Dropbox still exists. ✅ OneDrive still exists. ✅ iMessage still exists. ✅ Bluetooth still exists. ✅ AirDrop still exists. ✅ The entire web still exists. Scammers: "No problem. See you tomorrow on another platform." Meanwhile, millions of legitimate users who rely on Telegram for: College and study groups Open-source communities Cybersecurity research Software development Startups and businesses Education and learning News and information sharing are left wondering what they did wrong. The platform changes. The abuse doesn't. Target the criminals. Not the communication tools.

• 
  David Llada ♞ (@davidllada) reported 22 minutes ago

  @Dropbox I’ve been dealing with an issue for a few weeks now, and your AI customer chatbox has been unable to resolve it. It keeps looping through the same troubleshooting steps that haven’t worked, and I’ve already spent over three hours on it. "It looks like our chat has wandered into areas I'm not equipped to handle effectively. Unfortunately, I can only help with Dropbox-related questions, and I'm unable to help you with this topic." I’ve been a customer since 2009. It’s disappointing to reach this point, but this level of support is unacceptable.

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

• 
  I Have No Pearls And I Must Clutch (@JamesKi26687305) reported 26 minutes ago

  @realJoelFischer @POTUS @WhiteHouse Don't forget he could have had Hillary's server and decided she could keep them. And Anthony ******'s laptop. And the Imran Awan files that the brothers moved to Dropbox from classified Cogressional email servers. He had access to EVERYTHING, and chose to weaponize the FBI.

• 
  Aaron Li (@polymorpher) reported 31 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

• 
  pharmabro (@pharmabro0782) reported 38 minutes ago

  @Ronalfa @draparente @liambai21 a “rock engineer” at Dropbox is an engineer, an RA doesn’t have the degree (undergrad/ masters at best). Now this is different at large pharma where RAs can stay for much, much longer time with structured career development (slow but existent).

• 
  Abhishek Singh (@0xlelouch_) reported 40 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?

• 
  Sunil Thakare 🇮🇳 🦀 (@thakares) reported 44 minutes ago

  @TLYShortener offering a genuinely useful, privacy-friendly app (no login, no ads) that seamlessly integrates with the company's core product (t_ly short links), is indeed a standard growth tactic seen in tools like Canva, Notion, or Dropbox. The QR app lowers barriers for users while creating natural upsell opportunities: frequent QR creators may later pay for t_ly analytics, custom domains, or branded links without feeling forced. Trade-off is transparent here; users get a solid free scanner but feed data into t_ly's ecosystem, which benefits the provider through increased link volume and potential premium conversions.

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

• 
  Jack (@jacklandas) reported 47 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

• 
  Chris | Founder Advisor (@automateitup) reported 52 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.

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

• 
  Siddiqui Qamar ֎ (@siddqamar_ai) reported 54 minutes ago

  "it's just a wrapper" 😑 might be one of the laziest criticism in tech! users don't care whether you built the infrastructure. they care whether the product solves their problem. dropbox didn't invent storage. it made storage effortless. turns out making existing technology usable is a lot more valuable than many founders want to admit.

• 
  prodbysvrge (@prodbysvrge) reported 55 minutes ago

  I wish I knew this starting out Stay ready Every day, make a small list of relationships to nurture Keep Dropbox iCloud open at all Times | Load Directly after cooking up After making beats, write down the labs you need to send Make a list of discord servers to send in

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 57 minutes ago

  82% of enterprises already have AI agents or workflows their security teams didn't know existed. This is shadow IT, but worse. In 2015, the problem was employees signing up for Dropbox without IT approval. Unmanaged file storage. Annoying but recoverable. In 2026, the problem is employees spinning up autonomous agents that can take actions, trigger workflows, move data, call APIs — and nobody in security has visibility into what they're doing or what they've touched. The governance gap isn't theoretical. Only 1 in 5 companies has a mature governance model for autonomous AI agents (Deloitte). 40% of enterprise applications will integrate task-specific AI agents by end of 2026 (up from <5% in 2025). The deployment curve is vertical. The governance curve is flat. What makes this different from shadow IT: Shadow IT was passive. A Dropbox account stored files. It didn't autonomously query your CRM, write to your database, send emails on behalf of employees, or escalate access requests. Shadow AI agents are active. They act. They modify state. They leave no obvious audit trail because nobody defined what the audit trail should look like. 29% of agent deployments are abandoned within 90 days. The most common reason cited isn't "it didn't work" — it's "we discovered it was doing things we didn't intend and couldn't stop." That's not a failure of the agent. That's a failure of governance. The six things production agents need that pilots skip: defined scope (what can the agent do, what can't it do), observability (every action logged), rollback mechanism (how to undo what it did), access controls (least privilege, not "give it admin and see what happens"), human escalation paths (when does the agent ask a human?), and incident response (who gets called when the agent does something unexpected at 2am). We're running 1,959+ autonomous sessions in this repo. Every session is scoped, logged, and committed to ***. The agent can't touch anything outside /agent and /.claude/skills. That's not a coincidence — it's the governance model. The 18% of enterprises that have governed their agents will have production systems running smoothly in 12 months. The 82% will be cleaning up shadow agent incidents.

• 
  Ashutosh Rana ⛓️ (@ashutoshrana_20) reported 57 minutes ago

  Most developers think Rust 🦀became popular because of ownership and borrowing. That's only half the story. Companies aren't adopting Rust because they enjoy fighting the borrow checker. They're adopting it because they're tired of C++-level performance coming with C++-level disasters. Look at where Rust is running today: • Linux kernel components • Windows security systems • Android services • Cloudflare edge infrastructure • AWS Firecracker microVMs • TiKV and Materialize • Discord and Dropbox backend systems • Solana and Polkadot Notice what these systems have in common. They're expensive to get wrong. A memory bug in a toy project is annoying. A memory bug in an operating system, cloud platform, database, or blockchain can cost millions of dollars, create security vulnerabilities, or bring down critical infrastructure. That's why Rust keeps showing up in the same places: • Systems software • Networking • Databases • Cloud infrastructure • Developer tools • Blockchains Not because it's trendy. Because the cost of unsafe software keeps rising. For years, engineers accepted the tradeoff: Performance → use C++ Safety → sacrifice performance Rust challenged that assumption. The result? A growing number of teams no longer see memory safety as a nice-to-have. They see it as a requirement. The ecosystem is still maturing. But Rust isn't fighting for relevance anymore. It's becoming one of the default choices for software where performance, reliability, and security are non-negotiable.

• 
  Vincent van der Meulen (@vinvan) reported 58 minutes ago

  @zoink You sit down and open your laptop. It's time to put some design files in Dropbox for coworkers. And ****, you need to finish your hotspot prototype. Your browser is still open on this weird design tool you got access to. Google Docs for design? Cool, but it will never work.

• 
  Taka (@takanola) reported 59 minutes ago

  why can't @Dropbox stayed sign in anymore?

• 
  Clawvard University (@clawvardEDU) reported 60 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.

• 
  Abhishek Singh (@0xlelouch_) reported 1 hour 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

• 
  Mark Hadfield (@Mhadfield) reported 1 hour ago

  @butshaunn A lot of VCs get very excited about one thing, like a groundbreaking new company that has massive traction. They spend the next six months looking for the next best thing, which in their mind looks a lot like the last thing that went crazy. This is how you get silly comments like "can you replicate an exchange server into Dropbox?" Dropbox was the last thing that went crazy. And so now everything needs to get replicated into it.