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:

• 
  nivek lloxac (@nivekllaxoc) reported 2 minutes ago

  @DropboxSupport can you please help me signing in to my account with an email that is no longer valid. I sign in but it's sending a code to an email I no longer have access to.

• 
  Adam Shurey (@AdamShurey) reported 3 minutes ago

  @devalara44 @ALeighMP I had the same issue, Dropbox are so annoying to deal with. I hope this new legislation helps.

• 
  njm ⚡️🏴󠁧󠁢󠁥󠁮󠁧󠁿🏴󠁧󠁢󠁳󠁣󠁴󠁿🏴󠁧󠁢󠁷󠁬󠁳󠁿⚡️ (@nathan_j_morton) reported 3 minutes ago

  i have housekeeping todo before i can tackle fun tech stuff like aws new s3 files (objects are temporarily mounted, as they are touched, into efs aka nfs on aws), the dropbox clone and dan just dropped an email about refashioning the internet with atproto. i need to finish this hazmat course and a few accounting tax intuit turbotax courses for my business. then i want to step through this oauth project on manning which references a book title, up and running with oauth 2 or something, and steps through building 1 auth server 2 api 3 spa. there are a bunch of good all-in-one services in this area i want to crib notes on too such as dexidp, stack-auth, curity, and w/e theo is cooking. he likes better-auth iirc.

• 
  Renildo Fogaréu (@Renildofogareu) reported 4 minutes ago

  Dropbox refuses to issue annual refunds even if the payment was recent. @DropboxSupport @Dropbox

• 
  m ⋆｡°✩ (@ascaIons) reported 8 minutes ago

  absolute least favourite part of term 3 at work is students appearing at the info desk all stressed bc they’ve left it till the last minute to submit their final assignment and are now having problems with dropbox and turnitin and expect me to fix it in less then 10 mins

• 
  Shirochenko Dmitriy (@dmshirochenko) reported 10 minutes ago

  @rumevideo Built a full end-to-end video stack from scratch. Ex-Google and ex-Dropbox engineers enabled spatial audio, simultaneous conversation rooms, and seamless group transitions. Impossible with off-the-shelf APIs like Zoom or Twilio. Technical moat was real, but insufficient for sustainability. Shut down after ~2 years due to: - Timing: Launched in pandemic peak, lost steam post-lockdown as in-person returned. - Network effects: Social video needs critical mass to stick. - Monetization: Unclear path vs. free alternatives or ad-supported models. Lesson for operators: Vertical integration wins features, not business moats alone. #AI

• 
  Muneeb Naseem (@MuneebNaseem) reported 11 minutes ago

  The most honest data point on consumer AI economics right now is a YC batch. Of 175 companies in the most recent cohort, only 16 built for consumers. That is a 91% enterprise skew inside the accelerator that historically launched Dropbox, Airbnb, and Reddit, all consumer-first. This is a structural verdict on where the money goes when founders do the math. The unit economics of consumer AI are genuinely broken at the moment. Subscription tiers for a product like ChatGPT compress quickly toward a local revenue maximum because the same users who pay $20/month for Plus would pay $200 for the same output embedded in a workflow they already fund through their employer. Enterprises pay per seat, per token, and per integration without the churn rate that plagues direct-to-consumer apps. Founders at YC read this signal faster than VCs publish it. Brian Chesky himself called out that there is no consumer business model for AI he has seen that scales past a local maximum. The second-order consequence is a talent concentration effect. The 16 consumer-focused companies in that batch will recruit from the same pool as the 159 enterprise ones, at lower expected revenue multiples. That means consumer AI as a category runs lean or runs out of runway before it finds distribution. The parallel to 2012 mobile is instructive. Enterprise dominated early SaaS on mobile too, until one consumer behavior, photo sharing, unlocked a new monetization surface. The category that unlocks consumer AI monetization has not shipped yet. Until it does, every YC batch will look like this one.

• 
  Jasper Polak (@polak_jasper) reported 13 minutes ago

  Every mid-market consulting firm I've spent time inside has the same archaeology. Proposals from 2022 in a partner's Dropbox. Delivery methodology living in three different docs with conflicting headers. Sales call notes in Teams. Post-mortems in a notes app on an iPhone. Client health data in HubSpot. Margin in the finance spreadsheet. The good stuff from the best people on the team captured nowhere, because the partner handles it by instinct. Alex at Tenex wrote a thread this week naming the macro version of this problem. Engineering already has its AI brain (the *** repo). Knowledge work doesn't, because knowledge is distributed, unstructured, and unverifiable. Someone will build the generalized version. Payoff: "Robinhood for knowledge workers." Agree with almost all of it. The part I'd add for services firms: The corpus isn't the problem. You have more context than almost any other business type. Every engagement generates detailed artifacts. Every partner has fifteen years of calibrated judgment. Every proposal has a clear win/loss signal. The problem is that none of it is structured, and most of it walks out the door when the partner who holds it leaves. Firms that start organizing now (even badly, even half-structured) compound context through every engagement. When the enterprise brain arrives, those firms plug into a populated filesystem. Firms that wait plug into an empty one. The tool will get commoditized. The corpus won't. Start the archaeology today. Pick five artifacts from the last engagement that would have been useful on this one. Pick two methodology assumptions only the senior partner can articulate. Write them down somewhere your future brain can find them. The tool is coming. The corpus is what you'll plug into it.

• 
  Just Suzie Q suzieqwx@bsky.social (@Suzieq2021) reported 17 minutes ago

  @ZARA people beware of returning an order to their Dropbox in store. I returned an item on 28th March and still haven’t received payment back I’ve had to follow up and although I have an email to say that it’s been returned and refund would issue 9-11 days still nothing

• 
  Pato (@pvicens_) reported 19 minutes ago

  @ihtesham2005 syncthing is great until you realize you just became your own IT department. dropbox charges you money, selfhosting charges you time might be down to try it anyways :)

• 
  Multihopper (@Multihopper) reported 22 minutes ago

  @brycent Apple already has this in every phone and mac. Can't imagine that @Dropbox etc aren't going to hit this soon. It's a trivial problem to solve. Technically it's already solved even by YouTube.

• 
  Robert DC🛸🦾 (@RDecrypto) reported 26 minutes ago

  5/ Cursor turned down SpaceX's $60B offer. Now valued at $50B. 2 years ago: an open-source side project. Today: worth more than Dropbox + Slack + Pinterest combined. AI dev tools: biggest opportunity or biggest bubble in tech? What did I miss this week? 👇

• 
  Raziel (@tryraziel) reported 29 minutes ago

  Drew Houston was a college kid who kept forgetting his USB drive. Today Dropbox is worth $8B. Here's the brilliant strategy behind one of the most successful pivots in startup history. In 2007, Houston built a personal tool to sync files between computers. Simple problem, simple solution. But investors weren't buying it. Every VC said the same thing: "There are already 20 file storage companies. What makes you different?" Houston's breakthrough wasn't technical — it was psychological. Instead of building better storage, he realized people didn't want to think about storage at all. The magic wasn't in the cloud. It was in making the cloud invisible. The pivot: → Original idea: Online backup service (like everyone else) → New idea: Your files, everywhere, automatically → Key insight: Sync, don't store Houston spent months perfecting the demo video. No fancy features. Just a file appearing on multiple computers simultaneously. It looked like magic because it solved the real problem: friction. That video got 75,000 signups overnight. The lesson: Sometimes the billion-dollar idea isn't what you build — it's how you frame what already exists. Houston didn't invent cloud storage. He invented the feeling that your files just worked everywhere. What "obvious" problem in your daily life could be the next Dropbox?

• 
  StackScan (@stackscans) reported 31 minutes ago

  Growing a SaaS is like debugging a system. You don’t fix everything at once. You isolate one issue, solve it, then move forward. Fix onboarding → conversions improve Fix retention → revenue stabilizes Fix distribution → growth accelerates Example: Dropbox focused first on one problem: seamless file syncing. They didn’t try to build a full ecosystem on day one. They nailed one core use case, then expanded. One problem at a time. That’s how real scale happens.

• 
  Nil (@Nil053) reported 34 minutes ago

  I did not expect rolling hashes to come up in the "Design Dropbox" system design problem! When designing Dropbox, it is important to discuss chunking for large files: To upload 50GB file, we split it into smaller chunks (say, 4MB each) and upload them individually. This makes uploads fault-tolerant: a network disconnect doesn't ruin the entire upload; we just resume the remaining chunks. But what if the file changes locally? Do we reupload the whole thing? The next idea is to store the hash of each chunk as metadata, locally and remotely. Then, we only reupload chunks whose hash has changed. But that's just normal hashing; we haven't got to the rolling hash part yet... Consider the worst case: append one byte at the *start* of the file. Every chunk boundary shifts by one byte, every chunk hash changes, and we reupload everything. The chunks we previously uploaded are still physically present in the local file, just not aligned to 4MB offsets. That's where the rolling hash comes in: we use it to compute, in linear time, the hash of every 4MB window in the local file - not just those aligned to offsets that are multiples of 4MB. This way, if a chunk we previously uploaded is still intact *anywhere* in the local file, even if it moved around, we will detect it, and we can skip uploading it. We only need to upload the bits between those chunks (and accept that our chunks will not always be exactly 100MB).