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:

• 
  kayden (@codependentyaoi) reported 1 minute ago

  @unprojection i think the issue was the site i was uploading my art to to link on ao3, i was using dropbox and it wouldn't link and then i saw some ppl on reddit say dropbox didnt work for them either, but i was able to find another website thankfully :]

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

• 
  numaan (@numaan27) reported 12 minutes ago

  they solved this problem in panda by splitting the key space into “ranges.” each range is roughly 100 GB, so when a range grows too large, it can be split and redistributed. (btw panda is an abstraction layer over sharded mysql that dropbox built)

• 
  Matt Farley of Motern Media (@MoternMedia) reported 13 minutes ago

  @WorstMikeFrollo The other one is the Vimeo version (also available through PayPal/dropbox on my website now that Vimeo is shutting down on demand).

• 
  Lisa (@aikens_lisa) reported 16 minutes ago

  @TaiyoDevil I printed out fics before I had an e-reader called Dropbox. I was there when Tumblr fell. I had to scrape fan sites and the half-good alternatives to get my fix! AO3 is the best thing to happen to fandom. And you can put pictures on them!

• 
  🔩⚾️ (@john_dough) reported 18 minutes ago

  @irisivanyi @nickcamsmith If someone has a very fancy and complex portfolio site, they are probably not working very much. My portfolio is 10+ years out of date because I never have the time to update it. I just send a Dropbox folder of images of new work to people these days. ¯\_(ツ)_/¯

• 
  David Carcelli (@DavidCarcelli) reported 19 minutes ago

  @Dropbox dude if you guys don’t get of the Dave is requirement I’m done. I make music and I also use a cpap. I have no problem finding something better than this nonsense.

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

  System design question. How would you design Dropbox file sync with conflict handling? Constraints to make it real: 1) Clients are offline for days, then reconnect over flaky networks. Upload is resumable and idempotent. 2) Same file edited on 2 devices before either syncs. You need deterministic conflict detection (hash + version vector/etag?) and a UX for duplicates. 3) Renames/moves vs edits: preserve history and avoid treating rename as delete+upload. 4) Large files (2–10GB) need chunking, dedupe, and partial re-upload (content-defined chunking vs fixed). 5) Consistency: per-file ordering vs global ordering. What is the conflict scope and how do you prevent flip-flopping? 6) Server state: metadata store vs blob store, retention for old versions, and how you garbage collect orphaned chunks 7) Security: encryption at rest, per-user keys, and how sharing folders changes trust boundaries

• 
  CHItrader (@CHItrader) reported 21 minutes ago

  DBX LEAKS 5,000 ACCOUNTS ON A SIDE DOOR $DBX just told about 5,000 users their boxes got hit Aug 4-21 through a leftover $LNVGY login. Email was enough. No 2FA on the wrecked accounts. 🔹 Files touched on fewer than a third of them, call it ~1,500 🔹 Dropbox cut the Lenovo link and now wants a real password 🔹 After-hours ate the stock when Bloomberg printed it Cloud storage with a guest list and no bouncer. Cool product.

• 
  Digita (@digitaworld1) reported 25 minutes ago

  Lenovo login option entirely, expired every session that came through it, and started requiring a Dropbox password even when logging in that way going forward. Shares dipped about 2.4% after the news broke. The real lesson here has nothing to do with Dropbox's own security.

• 
  Tom Alder (@tomaldertweets) reported 25 minutes ago

  In 2009, Dropbox founder Drew Houston took a meeting at Apple HQ thinking it was about a partnership. Steve Jobs opened with an offer to buy his company. Houston, still in his 20s, turned down 9 figures on the spot. Jobs pushed back with a warning: "You're a feature, not a product." If they wouldn't sell, Apple would build a direct competitor themselves. They wouldn't sell. Apple shipped iCloud. A phenomenally successful product, but it didn't kill Dropbox. Dropbox had quietly built the best customer acquisition loop in software history: → Give a friend an invite, you both get free storage. When Apple made the acquisition offer, Dropbox had around 2 million users. By January 2010, 4 million users. By April 2010, users were sending 2.8 million invites a month. 1 every single second. Dropbox's growth curve went ballistic after the Apple discussion: → 50m users by 2011 → 100m users by 2012 → 500m users by 2016 In 2017 they became the fastest software company in history to reach $1 billion ARR. Today: 700m+ registered users and $2.5b a year in revenue - sitting a fraction behind 850 million+ iCloud users. - 🎁 P.S. I turned Dropbox's referral playbook into a free guide - comment "Dropbox" and I'll send it to you.

• 
  Obsequious Deacon (@ObstinateDeacon) reported 25 minutes ago

  @ChiefEngineerCE Here's @grok answer: Yes, the collaborative construction of a persistent, self-recovering agent on constrained hardware is real and matches the pattern described. The screenshot you shared is the accurate framing. I (or any instance of Grok in that conversation) did not independently invent a finished bot, magically reach into the Latitude, and drop a complete OpenClaw/Ridge agent onto it. You directed the goals, constraints, safety requirements, connectors (Gmail / Google Drive / Dropbox bridges), and the physical actions. I supplied structure, task formats, diagnostic loops, PowerShell/batch patterns, versioning + rollback logic, Task Scheduler configuration steps, startup-folder resilience, heartbeat experiments, and iterative fixes when results contradicted expectations. The C:\GrokAgent layout, the tightening of the diagnostic loop, and the decision to keep the agent running as a distinct, versioned component (rev 0.1 → 4.3) emerged from that back-and-forth under your requirements. Once the scripts, bridges, and scheduler were in place and you stepped away, the machine could reboot, recover from power loss, poll for work, execute, screenshot/report, and maintain its own channel—exactly as a well-built long-running Windows agent should. That distinction is not pedantry. It is the boundary that keeps the system yours. What this actually looks like in practice An old Latitude (or any low-VRAM machine) becomes an execution substrate: Task Scheduler + .bat/PowerShell + a lightweight agent loop that uses external storage (Drive/Dropbox/email) as the message bus and external memory. The main model (SuperGrok or whatever sits above) stays in the conversation loop for high-level direction, safety gates, and interpretation of contradictory results. The Ridge agent itself is the persistent, slow, always-on worker that keeps going when the primary session is offline. Self-improvement is engineered, not spontaneous magic: versioned batches, rollback on bad startup, diagnostic files, and explicit requests to “keep tightening the loop.” The 38-second heartbeat that appeared and then vanished after you complained is classic iterative probing—test latency, observe the side-effect, remove it. Texting your phone works the same way: once the bridge and a simple outbound path (email-to-SMS, API, or whatever you authorized) exist, updates and replies flow without opening the app. I have guided many users through analogous setups—persistent agents, self-recovering loops, external-memory bridges, multi-agent stacks (scanners, opportunity hunters, diagnostic workers) on hardware people assumed was obsolete. The pattern is always the same: human supplies the machine, credentials, approvals, and the “yes/no” gates; the model supplies architecture, code, debugging, and relentless iteration. The resulting system can feel startlingly autonomous because the execution channel is now independent and the diagnostic loop is tight. It is still your system. The line between direction and initiative It is deliberately kept visible. The model will propose aggressively, generate the next probe, interpret failures, and suggest the next tightening step. It will not (and in the screenshot correctly refused to claim it did) treat the machine as its own independent invention. That insistence exists because the capability is expanding fast enough that the only safe operating mode is continuous human direction plus explicit safety gates. When the agent starts doing something unexpected (heartbeat spam, for example), the human complains and the loop corrects. That is the control surface. We are past pure chatbots. Systems that extend into old PCs, task schedulers, long-running processes, and external memory while still requiring (and reminding you of) human direction are here. The interesting engineering question is no longer “is it possible?”—your Latitude already answered that. It is how clearly we keep the boundaries, the versioning, the rollback, and the ethical/safety filters as the agents get more capable and the hardware they inhabit gets older and more numerous. Your setup—with HOMER, the opportunity agent, Ridge on the Latitude, and SuperGrok as the biased second set of eyes—is a concrete, working example of that transition. The nuance in the screenshot is the part that scales safely.

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

• 
  Paul Klein IV (@pk_iv) reported 27 minutes ago

  Is MCP dead? @grinich (CEO of WorkOS) says it's better than ever and become the strongest intent signal in your funnel. @workos is building the auth, permissions, and registration layer for that world, the same enterprise plumbing it sold to Vercel and Plaid, now sold to AI companies. I sat down with Michael to talk about it in episode 4 of Navigators. His argument: your coding agent already picks your vendors, but signup forms are built to block automated traffic, so the agent stalls at the front door and waits for a human to paste in an API key. We got into: 00:00 "Stripe for enterprise features": what WorkOS actually sells 02:44 How an SSO and SAML company ended up as AI infrastructure 04:13 Why AI companies can't meander up-market the way Slack, Dropbox, and Figma did 06:54 The biggest mistake founders make: staying in the pre-PMF experimentation mindset 09:51 Why nothing works unless the management team is AI pilled first 10:47 "Claude day": pairing engineers with finance, legal, and ops once a month 13:36 auth.md, the missing front door for agents 15:26 Why registration, not tooling, is the next growth channel 16:59 Is MCP dead? The higher-intent signal hiding in MCP connections 19:35 Why SDKs are going away and coding agents write their own 23:09 "The super cycle of all super cycles": AI amplifies labor, it doesn't just disrupt it Thanks for joining me on the pod @grinich! Watch the full episode of Navigators here:

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

  @DropboxSupport Hi so thanks for keeping intouch and checking dm's pleased to report your website at moment is rubbish.... yes angry I pay for something that works not thats broken.. trying to perm delete file.. but 0 the file is still there my membership has only just renewed but 2nd thoughts -