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:

• 
  Jan Senderek (@jans) reported 1 minute ago

  I started journaling at 16. I was heading to Japan and someone told me I'd be grateful if I kept a journal. So I did. And they were right. I loved that I had somewhere to put my thoughts. Somewhere to look back at if I wanted to remember something. Plus I knew I was being thoughtful about my future self. But life got bigger. University, then a career, now a family. More thoughts. More things. The journals had no chance of keeping up. So what changed was the tools. Handwritten journals to Evernote to Dropbox to Obsidian to Notion. Always thinking the next one would be the answer. It never was. Every system asks the same of you. Tag this. File that. Organize here. Review there. Do the work now so that future-you can find it later. And future-you is grateful. That part is true. But your current self carries all of it. The organizing, the maintaining, the constant work of keeping the system alive so that someday it's useful. That burden never lifts. It just accumulates. Your current self and your future self should be working together. Not one doing all the heavy lifting for the other. What if you just put your thoughts down. And trusted they'd be there when you need them. No organizing layer. No maintenance. Just the thinking. So you can truly be your current self.

• 
  Genius Business (@GeniusBusiness_) reported 2 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.

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

  System design prompt: design Dropbox file sync. 1) Requirements to pin down - Devices: 1 user, N devices. Offline for days. Multi-GB files. - Semantics: per-file versioning, conflict handling, delete/rename. - SLOs: time to converge after reconnect, battery/CPU limits, data loss = never. 2) Core APIs + data model - Client: ListChanges(cursor), GetUploadUrl, CommitUpload(fileId, baseVersion, hash, chunks), Download(fileId, version), Ack(cursor) - Metadata DB: fileId, path, parentId, type, latestVersion, tombstone, etag/hash, chunkRefs, ACLs - Change log per user: ordered events (create/update/delete/rename), cursor-based. 3) Architecture - Separate metadata from blobs. - Metadata service writes event + updates latest pointers. Blob store is content-addressed (chunk hash) for dedupe. - Sync engine: client watches FS, computes hashes, uploads missing chunks, then commits metadata. - Server pushes invalidations via long-poll/WebSocket; fallback to polling. 4) Scaling moves - Shard by userId for metadata and change logs. - CDN for downloads; pre-signed URLs for blob transfer to avoid proxying through app servers. - Chunking (4–8MB) + parallel upload with backpressure. Resume via chunkRefs. - Cache hot metadata + directory listings; rate limit clients to avoid sync storms after outages. 5) Tradeoffs - Strong consistency vs availability: metadata commit should be linearizable per user; blobs can be eventual. - Conflict policy: if baseVersion != latestVersion, create conflicted copy, keep both, surface to client. - Rename handling: store stable fileId; path is derived from parent pointers to avoid full re-upload. 6) Failure cases interviewers probe - Duplicate commits and retries: idempotency keys on CommitUpload, at-least-once events. - Partial uploads: orphaned chunks; GC with refcounts + TTL. - Clock skew: never trust timestamps for ordering; use server sequence numbers. - Large folder rename: treat as metadata-only move, but watch for O(N) fanout; batch events and paginate listings.

• 
  kfd&p (@kfdpcom) reported 3 minutes ago

  @mellolais___ @LIBSCRUSHER @Dropbox I went on their site and it does say that the .com access is having issues. I guess we just wait it out.

• 
  glitterandspit (@Glitterandspit) reported 5 minutes ago

  Dropbox down. Computer updating. I have a free day I suppose.

• 
  Jürgen Strobel (@JuergenStrobel) reported 8 minutes ago

  @Arthur_van_Pelt You claimed that Bitcoin has a problem for "storing arbitrary data". Photos on Dropbox is a trivial example. Now you're moving the goalposts to subjective, emotional criteria you can't even define well. How much data is "way too too much", and how does BIP 110 solve it?

• 
  Amitoj Gautam (@amitojgautam) reported 10 minutes ago

  @airtelindia @Airtel_Presence I’m facing what appears to be a serious IPv6 routing/throughput issue on my Airtel broadband. My 300 Mbps connection gives ~300 Mbps download AND upload on Speedtest. However, with IPv6 enabled, Dropbox uploads collapse to around 10–15 KB/s, and services such as Gmail and some websites also become extremely slow/unresponsive. After disabling IPv6 on the Ethernet adapter, Dropbox immediately jumped to ~39 MB/s and the affected websites started loading normally within seconds. This has been reproduced consistently, so it does not appear to be a general bandwidth or Dropbox issue. Please escalate this to the network/IPv6 team and check IPv6 routing, packet loss, MTU/PMTUD and provisioning on my connection.

• 
  Chase (@Chase_Commerce) reported 13 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.

• 
  Matt Farley of Motern Media (@MoternMedia) reported 20 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).

• 
  dragon1952 (@gmanshk) reported 22 minutes ago

  From GROK Yes. Max Miller’s attorney released a public Dropbox folder containing an undressed photo of his 2-year-old daughter. It came from a February 2025 text exchange documenting a bruise (later a broken collarbone) noticed during bathing. The image was available for about a day before removal. Miller’s lawyer called it an accidental inclusion of a shirtless photo with no ******** visible. The other side’s lawyers described it as potentially showing ******** and possible CSAM. Miller has acknowledged the photo existed in the materials.

• 
  Ryan McKeen (@ryanmckeen) reported 24 minutes ago

  Lawyers, your data lives in six places and you wonder why AI can't help you. Dropbox. Drive. Email. A hard drive. Two spreadsheets only one person can find. Fix that first.

• 
  Fougars (@fougars67) reported 25 minutes ago

  @GaleTRogersJr @vaNlabs Three replies and you still have not answered the actual question: how does Leadpoet revenue accrue to alpha holders? V440 is not a permanent top-32 cartel. There is no hard cutoff and the threshold is dynamic. Dropbox is piloting Leadpoet, not “signed as a customer.” The fact that everyone sold the announcement candle is precisely the point. The business may have value, but the token has not demonstrated durable value capture. Sorry your bags are down bad, but insulting me does not fix the alphanomics.

• 
  Startup Archive (@StartupArchive_) reported 25 minutes ago

  Drew Houston on the growth hacks Dropbox used to acquire millions of users Dropbox founder Drew Houston reflects the distribution challenge most startups face in the early days: “You can buy all the AdWords in the world but if nobody’s searching for what you’re making, you have a problem.” Drew eventually landed on a two-step solution to solve Dropbox’s cold start problem. Step 1: make a product that people really love to use. “Good engineering and good design are part of it, but one of the ways I think about it is maximizing the probability that your customer ends up with a solved problem. That’s why Craigslist — which was started in the 1990s and doesn’t appear to have been updated since the 1990s — is by far the most successful business of its kind. You show up at Craigslist and you leave with your concert tickets or your casual encounter or whatever you’re looking for. Even though the design isn’t that great and it isn’t that hard of an engineering problem, it was unbelievably successful . . . [Distribution] starts with a great product and all of the marketing or tricks in the world won’t help you push a rock uphill.” Step 2: give people tools to spread the word “Two things drove the vast majority of our signups today. The first was we created this incentive-referral program where if I tell you about Dropbox you get some extra storage and I get some extra storage, which gave us this kind of currency to work with and people were just doing it for its own sake. People weren’t even using the extra space. They were just referring their friends because they got points. We’d now call it a gamification mechanic, even though I’m not sure that word was even around back then.” Drew continues: “The other thing we did was create this idea of shared folders where if I’m working on a shared project at work or if I want to share photos with my family, then all these new users are brought into the fold just by using the product . . . Now there’s whole body of art and science on how to do that, how consumer internet companies grow, and how viral growth works, but these things were instrumental to how we got started.” Source: @ECorner (Jun 2012)

• 
  Martin (@martin_valchev_) reported 27 minutes ago

  Small feature, real problem: Handing a WordPress site to someone else usually means FTP credentials, database dumps, or a shared Dropbox folder that stays there forever. A link that expires and can be revoked is just... better. Security shouldn't require discipline. It should be the default.

• 
  Greg Ceccarelli (@gregce10) reported 28 minutes ago

  @kunchenguid no one will disagree with that sentiment. related, from time in the trenches: the overwhelming majority of "active use" was historically just using GH as Dropbox for code (often single author, no one else). Memory a bit fuzzy but think about all of the things you can do on GitHub: 1. Core ***: Create, Clone, Fork, Commit, Etc 2. Collab: Issues, PRs 3. CI/CD: Actions, Checks, Webhooks, etc 4. Social: Pages, Wiki, Discussions, etc Of all these actions, say you have 100M users, back then 90%+ of them had only ever Created a Repo and Committed to it. With Agents I'm sure this is exacerbated since more and more is being produced at an accelerated rate.