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:

• 
  Mike Nolan - ⌬CatalyticComics⌬ (@CatalyticComics) reported 14 seconds ago

  As a developer I wanted to build something that addresses every issue I've run in to as a reader. These are my top ones: - Campaigner emails a Dropbox link and maybe you miss it - DRM/server requirements that amount to "you don't really own it" - No above-board way to share

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

• 
  Nav Toor (@heynavtoor) reported 4 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.

• 
  Liam (@LJ1101234) reported 5 minutes ago

  @DropboxSupport Hi I’ve been emailing your support team about a devastating issue. Somehow, all of our children’s photos and videos were permanently deleted from our Dropbox account without any warning.

• 
  ṢƘĪÑlÖVẸ́R̃ṢX🇺🇲🌷 (@skinloversx) reported 5 minutes ago

  Hey Daddy I'm down for FaceTime 💧 Dropbox and all kind of nasty content message me for menu 💦💦 #md

• 
  Jon (@kpjan99) reported 6 minutes ago

  @WestHerr there and put the key in a Dropbox instead of just checking me in. The little things make a difference. Never had these issues with @NorthtownAuto . They catered to whatever we wanted to do with purchases and service was always on point. Only bought from you because they did

• 
  Paulius Eidukas (艾文) ☭ (@nilsenist) reported 9 minutes ago

  @RavenT1me Sorry about that! The hacked account asks to download a virus disguised as an "indie game". I've reported that both to Discord and Dropbox/GitHub/YouTube which help distribute the file. Hopefully that shuts down the hacker at least temporarily. Hope you get your account back!

• 
  Bhavyam Arora (@AroraBhavyam) reported 11 minutes ago

  99% startups who applied to yc today will get rejected. here's what the smart ones do next: a no from yc isn't the end. they literally encourages you to reapply and tracks your progress across applications. the founders who get in later treat rejection as round one, not game over. the playbook: "don't wait for feedback" yc doesn't tell you why you got cut at the application stage. so stop self-doubting firstly. the reasons founders get rejected are almost always the same: - no visible progress between "idea" and "application" - not the perfect answer why you're the right team for the problem - vague answers that read as ai slop or unclear thinking reapply. it actually works. - dropbox: drew houston applied solo, got rejected, was told to find a cofounder. he did, reapplied, got in. - reddit: rejected for a completely different first idea. yc liked the founders and told them to come back. they did. the pattern never changes: build, show progress, come back stronger! you can apply again right now yc's decision lets you apply for the next batch. no need to wait months to get another chance. don't put your life on hold other strong programs are still open while you regroup. check the attached tweet below for whole list where you can apply as well. apply in parallel, not "later." the real unlock is traction a reapplication that says "we listened, we built, here are the numbers" beats a first application every time. the 6 months after a no matter more than the no itself. rejection quietly filters out the founders who were never that serious. don't be one. 💀 follow @arorabhavyam for weekly content around founders, startups and AI! 🫡

• 
  Elias Al (@iam_elias1) reported 12 minutes ago

  8/ The settings on your own devices that are silently eating bandwidth. Even with a great router, fast DNS, and honest ISP speeds, your devices may be consuming bandwidth you didn't authorize. Common culprits: On your phone: 1. iCloud/Google Photos backup set to sync constantly (not just on Wi-Fi) 2. App updates downloading in the background 3. "Wi-Fi Assist" on iPhone (silently switches to cellular and back, disrupting connections) On your laptop: 1. Cloud sync services (Dropbox, OneDrive, Google Drive) uploading constantly 2. Windows/macOS pushing system updates during peak hours 3. Browser tabs running in background consuming bandwidth with auto-refresh On your smart TV: 4. Firmware updates downloading during prime streaming time 5. Multiple streaming apps running in background 6. ACR (Automatic Content Recognition) sending screenshots to servers every 15-60 seconds On IoT devices: 1. Smart cameras uploading video 24/7 2. Smart speakers maintaining constant server connections 3. Smart home hubs polling every device every few seconds She audited every device on her network. Twelve devices were consuming bandwidth she didn't know about. Three of them were using more data than her actual streaming.

• 
  Santiago Bustelo (@sbustelo) reported 14 minutes ago

  @DropboxSupport THEY ARE GIVING ME CANNED REPLIES. YOU SCREWED MY WORK AND BURIED ME FOR THE FOLLOWING MONTHS TO FIX UP THE MESS YOU MADE UP WITH MY FILES. I DEMAND A REFUND.

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 15 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.

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

• 
  Hugo Bowne-Anderson (@hugobowne) reported 21 minutes ago

  Every day, people working with coding agents generate piles of threads containing decisions, corrections, failed approaches, and repeatable workflows. Then the session closes. The code survives. Most of the knowledge behind it disappears into chat history. @gregce10 is working on that problem. He previously worked at GitHub, Dropbox, and Google, served as CPO at Pluralsight, and is now co-founder and CPO of @specstoryai. This is a video of Greg at work. Sort of. SpecStory saves sessions from Claude Code, Codex, Cursor, Gemini, and other coding agents as Markdown inside the project. Then Lore mines them. Greg demonstrated the full workflow across 516 saved sessions: - Index the sessions locally instead of sending millions of tokens straight to a model - Turn each prompt, response, and next user prompt into an evidence-bearing "beat" - Use the follow-up to detect whether the human accepted, rejected, or corrected the agent's work - Find recurring practices and corroborate them across projects - Present candidate skills as dossiers with citations back to the original sessions - Install nothing without explicit human approval Five hundred and sixteen sessions stop being exhaust and become evidence for how Greg and his team actually build. Lore proposes the reusable practices. Greg decides which ones enter the skill library. Greg showed us all this and more live in our recent episode of *Show Us Your (Agent) Skills*. (video made using seedance 2.0 on @replicate!)

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

• 
  Chase (@Chase_Commerce) reported 27 minutes ago

  the full $1 UGC video stack, every tool and every cost, top to bottom: layer 1: research tool: claude cost: a $20 subscription (or even free) it pulls the top performing UGC in your niche, breaks down the hooks and structure, and writes ready to film scripts. spread across hundreds of videos this rounds to pennies a clip. replaces: a creative strategist doing 3 hours a day layer 2: finding the winners to study tool: meta's ad library, free optional: atria or foreplay if you want the longest running ads surfaced faster cost: $0 to a small monthly fee you're looking for content that's been live for months, because longevity means it's making money. layer 3: filming tool: HourlyUGC cost: $25 to $35 an hour she films a clip every 30 to 60 seconds off a script, so 40+ clips a session. that's under a dollar a clip just to film. replaces: a $400 to $600 per video agency layer 4: editing tool: capcut, plus editors you hire directly cost: $3 to $7 an hour, 20 to 30 finished videos a shift adds a dollar or so per clip. the whole thing runs off one documented template so every editor produces identical output. layer 5: storage and handoff tool: google drive or dropbox cost: basically nothing creators upload raw footage, editors pull from it, finished clips go to a shared folder. that's the entire pipeline. total fully loaded: $1 to $3 a finished video, at whatever volume you staff for. nothing hidden in that number, and you own every clip outright instead of renting access to it. the stack is boring on purpose, and boring is why it scales.