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:

• 
  Vladislav Zharkov 👾 (@_vladislavzh) reported 58 seconds ago

  I have zero industry experience. None. I don't know how to use issue trackers, I need a GUI for version control, I deliver my files through Dropbox. I don't have templates, I restart or reuse every time. I don't use industry standard tools, I don't know workflows and pipelines.

• 
  Karishma Bhardwaj (@bkarishma360) reported 3 minutes ago

  @shahzamannn_ Your SaaS idea doesn’t need to be complicated. Stripe moves money. Postman sends API requests. Notion organizes information. Dropbox syncs files. The lesson? Simple problem + huge market + great execution = massive company. Stop asking, “Is my idea too simple?” Start asking, “How many people have this problem?”

• 
  Scarlett Bama 🇺🇸🅰️🐘🏈🏖️✝️ (@scarlettbama) reported 8 minutes ago

  @DropboxSupport Fri AM: Dropbox down? Rare if so! Will not allow PDF upload to existing folder. Upload 50x per month. Started after most recent IOS update. Using iPhone. No MacBook access right now. Pls don't sent to Community Forum.

• 
  Ishita Sethi (@Ishita__Sethi) reported 8 minutes ago

  @LoganOpSec that dropbox bit is the part that sticks. recovery without revoking access is just half a fix.

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

  Asked: design Dropbox-style file sync. 1) Clarify requirements - Devices: desktop + mobile, multiple per user - Semantics: eventual consistency, conflict handling, offline edits, rename/move - Scale targets: #files/user, max file size, p95 sync latency, bandwidth caps - Security: per-user auth, sharing model, at-rest + in-transit encryption 2) Core APIs + data model - UploadChunk(sessionId, part#, bytes), CommitUpload(sessionId, fileHash, path, mtime) - ListChanges(cursor) -> {ops}, Ack(cursor) - Download(path, version) with range support Tables: - File(id, ownerId, logicalPath, currentVersion, deleted) - Version(fileId, versionId, contentHash, size, createdAt) - Block(contentHash, refCount, location) - DeviceCursor(deviceId, lastSeq) - OpLog(seq, userId, type, path, fromPath, versionId) 3) Architecture - Client watcher computes hashes, does chunked upload to object store (S3/GCS) - Metadata service is the source of truth for paths, versions, ACLs - Change log per user (or per share) drives fanout to devices - Long-poll/WebSocket to push invalidations; client pulls deltas via cursor - Dedup by contentHash; store blocks, assemble manifests per version 4) Scaling - Partition metadata by userId; keep OpLog append-only with monotonically increasing seq - Cache hot metadata (folder listings, latest versions) in Redis - Use CDN for downloads; throttle uploads per device; resumable sessions - Background GC for unreferenced blocks using refCount + tombstones 5) Tradeoffs interviewers look for - Push vs pull: push invalidation, pull data is simpler and cheaper than pushing bytes - Strong vs eventual: strong per-file commit, eventual across devices is fine - Rename as metadata op; avoid copying data, but watch for path conflicts - Dedup saves storage, costs CPU and can leak info unless scoped per user/tenant 6) Failure cases - Offline edit + concurrent edit: create conflicted copy or keep both versions with merge UI - Out-of-order ops: apply by seq, idempotent commits, retry-safe APIs - Partial upload: orphaned chunks; TTL cleanup; commit is the only visibility point - Device clock skew: never trust mtime for ordering; server seq is ordering - Network *****: exponential backoff, cursor-based replay, checksums on download to detect corruption

• 
  virgin loser (@stonershelb) reported 10 minutes ago

  He put a photo of their 2 yo daughter naked with exposed genetalia in a Dropbox folder that “received more than 400,000 combined views or interactions. ... and it was publicly accessible for 23 hours before she says Minc acknowledged responsibility and took it down.”

• 
  Arthur Terrell Vaughn (@ArthurV36405381) reported 10 minutes ago

  @patmendoza6745 I know not of any of those specifications, but I still can’t figure out what the issue is with persistent memory, why can’t I just have a dropbox online that it can constantly access every single chat and conversation?

• 
  Agbaje Automation. (@digital_ab98389) reported 10 minutes ago

  Cut manual data entry time by 80% with one n8n workflow: trigger on new CSV in Dropbox, parse, map to Google Sheets, flag errors, alert Slack, log runs. Automate, reduce errors, save hours. DM me for demo.

• 
  Hiten Shah (@hnshah) reported 13 minutes ago

  @varadh @NotionHQ Bunch of markdown. Google Docs handled it well, but some of my markdown files can get gnarly and even docs chokes a bit. I’m also a minimalist with tools and workflows, trying to get away with the least amount of tools which helps a lot with speed and efficiency. I should be a power user of Notion. Since we’re here, I have plenty of folks (like you) that I know who work there now who I’ve met and like. I’m always rooting for you folks, as a result. Here are some unsolicited thoughts from holding it in for too long. I’ve used every document and notes app under the sun and spent a lot of time in Dropbox Paper and Hackpad before it. Early user of writely which became Google Docs. There are core product principles around a product like Notion that Notion breaks or seemingly optimizes for Notion over the user’s experience. At @CrazyEgg, where I haven’t worked full-time for 17 years until about a year ago, the team loves Notion. So I’m forced to use it. My most common activity is to export things out of Notion into my a chatbot or agent of choice. That has little pricks in the process than paper cuts. But all ouchies count against you. For example, in chrome, when trying to print a page (i am weird and print web pages to convert them to pdf), I can’t trust that all the content will come through. And the issues are inconsistent. I understand this is likely an edge case of an edge case, but all ouchies count, prickle or stabbing. If you got this far, thanks for reading my rant. I one shotted it with the agent between my ears.

• 
  Craig O'Shea (@craig_os) reported 16 minutes ago

  @DropboxSupport major issue with your services right now.

• 
  Ed Giansante (@edugiansante) reported 17 minutes ago

  86% of small businesses still haven't fully integrated ai into their operations. which is funny, because the tools are already here. they're everywhere. there's probably one open in another browser tab right now, quietly waiting to change your life. Goldman Sachs surveyed small businesses and found that only 14% have fully integrated ai into their operations. i don't think the other 86% are anti-ai. they're busy. they're cautious. and they probably don't want to add “company-wide ai transformation” to the list of things they need to worry about before lunch. honestly, fair. @paulg said something recently that I keep coming back to: "If the world is going to get turned upside down, the safest place to be is in a small, fast-moving company that can easily change direction." small companies should be the ones moving fastest. but most are still waiting for someone else to go first. someone else to test the tool. someone else to write the playbook. someone else to promise that nothing will get weird. @clairevo nailed the real blocker: "the blocker is never tools or intelligence. human systems, human problems." i've spent 15 years watching this happen. At Dropbox. At Wix. At Zynga. Now at Persona. different tools. different eras. same pattern. a team finds a new tool. everyone gets excited. someone schedules a kickoff. three weeks later, everyone is back in the old spreadsheet. not because people are stupid. because changing how people work is uncomfortable. and buying software is much easier than changing behavior. i've seen the same thing with community-led growth. i used to pitch community to executives who had every tool and dashboard money could buy. they'd nod. they'd agree it worked. then they'd return to the comfortable world of automation, sequences, and dashboards that made everyone feel productive. last year, i ran 86 events as a team of one and built $3M in pipeline. the secret was not a magical growth hack. it was showing up. knowing the 15 people in the room by name. listening carefully. creating a space where people could actually trust each other. not exactly the kind of thing you can solve with a 47-step workflow. ai adoption and community adoption have the same problem. the tools work. the ideas work. the uncomfortable human part is where things usually slow down. sitting with your team and figuring out what should change. trying one workflow instead of redesigning the entire company overnight. leading people through something new instead of sending a Loom video and hoping everyone feels inspired. the 86% aren't waiting for better ai. they're waiting for change to feel a little less scary. so start small. pick one annoying workflow. try one new thing. make it 10% better. then do it again. the tools are here. the next step is still a very human conversation. and, unfortunately, probably a meeting.

• 
  OneToothTeXan (@OneToothTeXan) reported 17 minutes ago

  I'm so sorry I left my zipper down and my sanity got loose. If found: Men, there's a dropbox. Women: please return to original source.

• 
  Tim Geisendoerfer (@djgeisi) reported 18 minutes ago

  @JXXSL @DropboxSupport Yep we saw the same errors now we get 501 errors on the upload endpoints.

• 
  ericleebristol (@iamericbristol) reported 19 minutes ago

  Email scams but they also use a press cloud server that can hold up to millions of emails and send out messages in a bulk but to hundreds of people complicated when it comes to taking down email scams cuz you have to find where they coming from answer in a cloud compressed server that can hold up to millions of emails frequently combine compressed attachments (like ZIP, RAR, 7Z, or TGZ files) with cloud storage or servers to deliver malware, phishing pages, or credential-stealing links while trying to bypass security filters. Common patterns 🚩Malware in compressed attachments: Attackers send emails with ZIP or similar archives containing executables, scripts (VBS/JS), or disguised files. Some use specially crafted or nested ZIPs, password-protected archives (password given in the email body), or less-common formats that email gateways may not fully unpack or scan. Opening/extracting the archive can install remote-access tools, stealers, or ransomware. Cloud storage phishing (“storage is full” or similar alerts): Emails impersonate Google Drive, OneDrive, iCloud, Dropbox, or generic “Cloud Storage” services. They claim storage is full, a payment failed, or files will be deleted, creating urgency. Links often point to real cloud infrastructure (e.g., Google Cloud Storage Azure Blob, or other legitimate buckets) that host redirect pages or fake login/upgrade forms. This makes the links look trustworthy and helps them pass filters🚩.

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

  System design question. How would you design Dropbox-style file sync with conflict handling? Constraints that make it interesting: 1) Multi-device edits while offline, then reconnect hours later 2) Large files (GBs), but common case is small diffs; do you chunk + hash + resumable upload? 3) At-least-once events from clients; duplicates and retries are normal 4) Need per-file causality: version vectors? server-assigned sequence? something else? 5) Conflicts: rename vs edit, delete vs edit, concurrent edits on same bytes; what gets auto-merged vs forked as conflicted copy? 6) Metadata vs content planes: directory tree ops must be atomic-ish, blobs can lag 7) End-to-end integrity: how do you detect corruption and avoid re-upload storms? 8) Fast convergence: target <5s to see changes on another device, but mobile battery + bandwidth are limited