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

• 
  Ricker (@0xRicker) reported 2 minutes ago

  Senior engineer just dropped a GPT-5.6 stress test after burning around $200K on API usage: 00:00 - $180K–$240K spent testing GPT-5.6 in Fast Mode 02:43 - The model using browsers, dashboards and settings like a remote operator 05:32 - 67 projects and 20+ hour autonomous sessions 07:07 - Lakebed, T3 Code and native app rewrites in 2–4 hours 15:08 - Rust compiler experiments, 18x speedup and a $91K Dropbox-style build 17:46 - GPT-5.6 fixing a broken Linux GRUB boot through KVM 22:56 - 3D games, weird assets and the remaining frontend taste problem It is a field test for agent loops The future edge is not the prompt It is the loop that can keep working after the prompt stops being useful

• 
  meshgear (@_meshgear) reported 6 minutes ago

  @Dropbox It is not working.

• 
  mskah🔞 (@mskah_t) reported 7 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.

• 
  Genius Business (@GeniusBusiness_) reported 8 minutes ago

  How Dropbox Spaces was conceived Spaces didn't start as a product idea. It started as a problem Drew Houston says he and his customers were all living. "[Spaces] is part of a bigger evolution we've been on that really started with our customers and realizing that the experience of using technology at work has become incredibly fragmented and distracting." The more he looked at it, the more he saw a cruel irony: the tools built to help us were the ones breaking our concentration. "A lot of the tools we're using that you think would be helping us focus have unintentionally made it impossible to focus. And that's a problem if you need to use your brain at work, because your brain works best when you can focus." That, he decided, was the real enemy. Not a missing feature, but lost focus. He called it "the higher level problem." He could see where it came from. Work simply doesn't look the way it used to: "It's very different from 20 years ago when we got five emails a day, not 500." Twenty years ago you might have just used Office. Now you're in Office and G Suite and Slack and Zoom and Dropbox all at once. 100 tabs, everything blinking at you all day, apps that don't work together. So the framing question became: how do you fix the environment itself? "How do we evolve Dropbox into the app that makes all your other apps work better together?" The breakthrough was a shift in how Houston understood what Dropbox already was. Watching customers, he realized they didn't treat it as a place for their stuff, or as just a folder on the desktop. "It's the place you're going to work." Once he saw it that way, the design conclusions changed: "When we thought about it that way, we realized we would have made a bunch of different decisions, and realized that Dropbox is actually really well positioned to help people focus at work." Two conclusions followed. First, Spaces had to move beyond files. Teams collaborate on far more than documents: Google Docs, Airtable, Figma, Trello and there had never been one place to hold all of it. So Spaces became “an evolution of the shared folder” that “moves it beyond being a folder full of files to an intelligent team workspace for any kind of cloud content.” "You can still have your PowerPoints and PDFs, but they can be next to your Google Docs and Trello boards and whatever else you have. Give you one space, not 10." Second, and this is where the concept sharpened. Spaces had to become a workspace, not a filing cabinet. Houston traced the problem back four decades. The thing we call "the desktop" is, functionally, the operating system: "The interface is the operating system." And it had been frozen in time: "That user experience hasn't really changed... it basically looks the same as the early 80s when it was first introduced on the original Mac." It was designed for a world that no longer exists: "It's this single player static experience that was perfect for when our whole life fit on a couple of floppy discs." So the team ran a thought experiment, start from scratch, for now: "If you were to redesign this for 2019, you'd make a bunch of obvious changes." You'd still want the files and cloud content. But you'd add the things the 80s interface never had: people, activity, comments, a record of what's been happening. You'd organize around the projects you're actually working on. You'd see your calendar, get Slacked, and start a Zoom meeting all without leaving the app. That thought experiment became Spaces.

• 
  Isha (@VISportsTalk) reported 8 minutes ago

  Is anyone else having issues with @Dropbox today?

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

  Design Dropbox file sync (typical system design prompt). 1) Clarify requirements - Devices: desktop + mobile, many devices/user - Semantics: eventual vs strong; last-writer-wins vs conflict files - Granularity: whole file vs block/chunk diff (large files) - Offline edits, resumable uploads, deletes/renames, shared folders - Targets: sync delay (ex: <2s LAN, <10s WAN), max file size, storage limits 2) APIs + data model - POST /changes (client reports local ops: create/modify/delete/rename) - GET /changes?cursor=… (server streams remote ops since cursor) - PUT /upload_session (init), PUT /upload_session/{id}/chunk, POST /commit Tables: - users, devices, folders - files(file_id, folder_id, name, latest_version_id, tombstone) - versions(version_id, file_id, hash, size, mtime, author_device, parent_version) - blocks(block_hash, size, refcount, storage_ptr) - version_blocks(version_id, block_hash, idx) - change_log(user_id/folder_id, seq, op, file_id, version_id) 3) Architecture - Client watcher + local metadata DB; compute chunk hashes; upload missing blocks - Metadata service (txn + authz) + object store for blocks (S3/GCS style) - Change propagation: long-poll/WebSocket for online devices; push notifications - Dedup: content-addressed blocks by hash; refcount GC 4) Scaling choices - Shard metadata by user_id/folder_id; keep change_log append-only - Cache hot metadata (latest_version, cursors) in Redis; rate limit clients - CDN/object store for block download; multipart for big files - Background workers: GC, compaction, conflict detection, virus scan (optional) 5) Tradeoffs to discuss - Chunk size: 4MB lowers metadata; 256KB improves delta sync but higher overhead - Strong ordering per folder via monotonic seq vs global ordering (hard) - Conflict model: last-writer-wins is simple; conflict copies preserve data but noisy - Encryption: TLS always; client-side E2E complicates server-side dedup/search 6) Failure cases - Network *****: idempotent commits via upload_session + version_id; retries with backoff - Duplicate uploads: hash-based existence check; commit is atomic in metadata store - Clock skew: don’t trust mtime for ordering; use server seq + parent_version - Retry storms after outage: jitter + per-device budgets; push minimal deltas - Corrupt blocks: hash verification on download; re-fetch; quarantine bad replicas

• 
  Weird Darkness®️ (@WeirdDarkness) reported 11 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.

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

• 
  ESCHA (๑ˊ͈ ^ˋ͈) (@eschadiol) reported 12 minutes ago

  @joshpuckett i worked on an app called roll back then, dropbox, path, and facebook made offers, then fb made memories, path closed down, and carousel was deprecated, would have been so sick to cross paths at that time

• 
  Palpy (@evgenij_rabij) reported 15 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.

• 
  Lindsey Gaetani (@lindseygaetani) reported 16 minutes ago

  This piece of information is much more important than many realize. Cosgrove & Kate Peter got very lucky with my "countersuit" against Cosgrove, et al, in that they were able to use that as a convenient excuse to not continue with the wiretap & WI charge against @DoctorTurtleboy involving myself. But the truth of the matter is that Pam 'The Scam' Friedman (my "advocate" aka handler assigned by corrupt Brian Tully) informed me weeks before they had any knowledge of my countersuit that Cosgrove was having some "difficulties". She informed me that they could not locate the wiretap evidence that was shown to the grand jury when I testified. She even asked ME if I had a copy that I could provide to them. Evidence submitted before a grand jury is suppose to be saved and cataloged, so explain to me how exactly it goes "missing." Well, I can help you. See there were two videos. The original video in which I was recorded from a pocket. And the edited video that is spliced to make it appear as though I agreed to being recorded (the infamous "I know, I know" response). Kate Peter claimed that the original video was given to her by a woman who Aidan had sent it to. Big problem with this, the woman "didn't want to be involved", so her name was never mentioned during any police report or part of the grand jury, let alone did she testify to authenticate the videos. Instead, Tully had Kate save the original video to a Dropbox folder and email it directly to him, to make it appear as though it came from her and that this was the original chain of custody. Big no-no. As time went on, Kate's name began to take center stage, along with her shady involvement and criminal behavior. The secrets of her helping Mello were exposed so they had no choice but to see that these charges were squashed as to not contaminate the rest of the charges against Aidan. So what did they do? They had Kate delete the Dropbox file, and the evidence it contained. Kate Peter tampered with evidence in a felony trial. They must have took a big sigh of relief when I sued Cosgrove because it gave them a very easy out and they were able to wipe their hands clean as if none of this ever happened. Except it did. And Kate Peter still inserted herself into the other charges. For this reason alone, Aidan's charges should be dismissed.

• 
  M.Ellis (@MEllisPhotograp) reported 16 minutes ago

  @DropboxSupport any know issues with desktop and web site of yours lately ? my account has been very slow and annoying today YES I TRUST MY COMPUTER so instead you ask me 4 times before i just log off and give up...

• 
  brodie / knox (@brodiecantskate) reported 16 minutes ago

  @Dropbox your app sucks so much, I can’t believe I’ve been willingly paying for it for so long when it causes me so many issues 💔💔💔

• 
  Duane Storey (@DuaneStorey) reported 21 minutes ago

  Hey @plasmidsaurus - just tried your new Dropbox in Valencia, Spain. It’s super difficult to find. I also had to get several security people to help me, and ultimately the box was found down some dark corridor behind a locked door that some other person had to be called to open. If the goal was to make this easy to access, it’s pretty far from that. But glad there are more options.

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 23 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.