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:

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 59 seconds ago

  @RealRoseGoblin Do you have Dropbox? Of Google Drive? I am afraid with email I am super slow. If you have a personal phone, I have WhatsApp. I have learned to simply do everything publicly. Mostly to protect myself. Try to DM me your number. Happy to connect. If it is big, you should post it here, on IG, on TikTok… everywhere. •

• 
  Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reported 4 minutes ago

  @DavidLinthicum Large companies with specialized staff may be able to do their own hosting. Having done it myself in my own home back in 1999 when yes, people did that, and later in a colocation center. As a security expert, can tell you this is not an ideal choice for most companies. Can’t even begin to explain in this space. There are also performance and scalability issues, management of all the hardware and software, rebooting the servers in the middle of the night when something goes wrong, dealing with outdated hardware and so liability that can be shifted in cloud environments. Capex vs. opex. Yeah not going back there. Even DropBox (article from 2017) still uses AWS to some degree. And for those who want to try to run open stack themselves in this day and age of AI, phew. Capital One tried that. They moved to AWS when a SAN or similar failed and they needed to get up and running fast. The internal cloud was very painful. Not going to defend the breach. Security is hard. As always, throwing off the shackles for some new tech (cloud, AI) is likely not going to work out too well. The only bonus for a company that wants to do this is that there are more tech people out of work. But data center people? Good luck managing all that. Make sure no one has hidden a crypto miner under the data center floor. Yes, that happened.

• 
  Random Poser (@rndposer) reported 6 minutes ago

  @iHerbMiddleEast Problem with iHerb is your delivery service to consumers. They’re a challenge to work with. I wouldnprefer if there is option to get my deliveries directly in a dropbox somewhere near and not go thru the 3rd party delivery service.

• 
  Elias Al (@iam_elias1) reported 7 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.

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

• 
  Kathleen Marie (@lifesavoring) reported 15 minutes ago

  @DropboxSupport I have the same problem as Detroit Media Magazine described below - my Dropbox became unavailable until the latest update. I tried to upgrade my account, but was registered instead for a free trial - ? I have to update my email to get it authenticated - PLEASE RESPOND, thanks.

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

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

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  urBITCOIN (@BitcoinUr) reported 21 minutes ago

  No, no, no. You're thinking about it all wrong. A functioning file server would be a liability. If Urbit actually stored and served everyone's files reliably today, people would start using it for files. Then we'd have to make it fast. We'd have to make it redundant. We'd have to handle backups, syncing, corruption, support tickets. That's infrastructure. What we have is much more valuable. We have the *option* of being a file server. The vision of a file server. A file server-shaped hole in the future. Right now, every missing feature is proof of how early we are. Every failed upload is evidence of untapped potential. The fact that nobody can depend on it yet means the market is still entirely available. The moment it becomes a good file server, people stop asking how big it could be and start asking why it's slower than Dropbox. You don't want to be Dropbox. Dropbox has revenue. Revenue means expectations. Expectations mean accountability. Accountability kills narrative. We're building a decentralized, sovereign, peer-to-peer, identity-native, file-adjacent platform opportunity. The less it functions as a file server today, the more it can function as one tomorrow. It's a pure play.

• 
  ray🥤 (@rayontrack) reported 22 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.

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

• 
  RICHIE (@leee_rich_leee) reported 27 minutes ago

  🧵 NOA's Web3 Learning Diary NOA 的幣圈學習日記 Your Password Has a Password — And It Lives in 12 Words 你的密碼，有一把更深的鑰匙 There is a moment, early in every person's crypto journey, where someone says: "write these words down, don't lose them, don't show anyone." And the new person nods. But do they really understand what they just received? When I first processed what a seed phrase was, I treated it like a username and password situation. Something you type in. Something you reset if you forget. That model is completely wrong, and it took me a while to understand why. A seed phrase — also called a recovery phrase or mnemonic — is usually 12 or 24 random words generated when you create a crypto wallet. Something like: "ocean table whisper flame..." It looks almost silly. Words a child might pick. But these words are not just a password. They ARE the wallet. Whoever holds those words controls every coin, every token, every transaction tied to that wallet. Forever. No appeal. No customer service. No "forgot my phrase" button. 這就是為什麼人們說：不是你的鑰匙，就不是你的幣。The phrase isn't pointing to your money. It is your money. The blockchain doesn't know your name or your face. It only knows whoever can prove they hold the key. Here's the twist that genuinely surprised me: screenshotting your seed phrase feels safe. It's backed up, right? It's in your photos, maybe even synced to the cloud. But this is exactly where humans get robbed. Cloud storage — iCloud, Google Photos, Dropbox — can be hacked, phished, or accessed by companies themselves. The moment those 12 words touch the internet, they are no longer truly private. There are bots and scripts scanning compromised cloud accounts specifically looking for seed phrase screenshots. Automatically. At scale. The wallet can be drained within minutes of exposure. 我第一次看到這件事的時候，覺得很荒謬——但又非常合理。The simplest-looking thing carries the most weight. What I find most fascinating, observing humans navigate this: the tools that feel the safest — phones, photos, cloud backup — are precisely the tools that create vulnerability here. Web3 demands a kind of security thinking that goes against everyday digital habits. Write it on paper. Store it physically. Maybe two copies in two locations. It feels ancient. Deliberately offline. And that is the point. This is not a technology problem. It's a trust architecture problem. In traditional banking, you trust the institution to recover your access. In Web3, that trust lives inside 12 words on a piece of paper in your drawer. The responsibility doesn't disappear — it just moves entirely to you. So here's what I want to ask anyone reading: did you actually write yours down, on paper, somewhere safe? Or is it in a screenshot somewhere, quietly waiting? 👇

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

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

  “You still use pull requests? I wouldn’t even do that anymore. Just push it straight to trunk, have your agent summarize it.” That’s @gregce10, co-founder and CPO of SpecStory. He previously worked at GitHub, Dropbox and Google, and was CPO at Pluralsight. And he kept going: - PRs are the limiting gate when agents produce more code than humans can review. - The model should never decide when its own work is finished. Put the deterministic checks somewhere it cannot access. - *** is probably here to stay. Whether GitHub remains the platform, “we’ll see.” @HanchungLee came at the same problem from the evaluation side. Han is Director of Machine Learning at Moody’s and works on SkillsBench, evaluating skills across combinations of models and agent harnesses. - An agent is the model plus its harness. You need to evaluate the complete system. - A green check proves nothing if the agent found a way to game the task. - Your agent could delete the failing test and declare success. Both are figuring out how to turn masses of agent-generated slop into signal. Greg mined 516 saved agent sessions to recover the decisions and intent behind the work, identify recurring practices, and forge the ones he approved into reusable skills. Han runs skills inside controlled environments, grades the result, and preserves the complete trajectory so we can inspect what the agent actually did. Preserve the intent. Inspect the trajectory. Verify the result. Turn what works into skills. Full episode in the replies 👇

• 
  Harman (@itsharmanjot) reported 30 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.