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:

• 
  Atish (@AtishhAmte) reported 39 seconds ago

  @balyberdin_dev I was facing an issue with my clients with file chaos Tried everything from drive to dropbox, WhatsApp, email but nothing helped there So I listed my problem and derived solution around it

• 
  Ryan McCain (@rmccain_cns) reported 3 minutes ago

  Shadow IT used to mean employees running Dropbox without IT approval. Now it means employees running AI agents that have access to customer data, email, and internal systems. Same problem, different stakes. The liability exposure is not comparable.

• 
  Raziel (@tryraziel) reported 6 minutes ago

  Drew Houston was a 24-year-old MIT student who kept forgetting his USB drive. His solution? A file-syncing service called Dropbox. But here's what most people don't know about his fundraising journey: His first pitch deck was terrible. 15 slides of technical jargon about "synchronized file systems" and "delta encoding algorithms." VCs glazed over. The breakthrough came when he made a 3-minute demo video instead. No technical explanations. Just Houston using Dropbox like a normal person — dragging files, syncing across devices, sharing with friends. That video got him into Y Combinator in 2007. → Seed round: $1.2M led by Sequoia (2007) → Series A: $7.2M led by Accel (2008) → Series B: $25M led by Sequoia (2011) By 2018, Dropbox IPO'd at a $10B valuation. The lesson: Houston didn't pivot his product — he pivoted his pitch. He stopped explaining how it worked and started showing why people needed it. Sometimes the problem isn't your idea. It's how you're selling it. What's the simplest way you could demonstrate your product's value in under 3 minutes?

• 
  avrl ☘ (@avrldotdev) reported 8 minutes ago

  3. The Sync Engine (Watcher) The Dropbox client uses a "File System Observer" Local Side: It detects a change as you hit Ctrl+S. Server Side: It uses a "Long Polling"/"HTTP/2 Stream" connection. The server keeps a connection open to your phone/laptop. As the metadata changes in the DB, the server "pokes" the other devices to start fetching the new blocks.

• 
  The New Release Guy (@moviesplusgames) reported 9 minutes ago

  @Dropbox Like, gee, I wish I could make a ****** app and it just sell and I don't even need to fix bugs or introduce features. Must be nice if you're a big *** corporation. Only the people suffer.

• 
  sophie's dad (@sofia_karina) reported 9 minutes ago

  @SharonElizaDC @FedExHelp who goes to a dropbox?? just wave down a truck ffs

• 
  Muhammad Usaid (@MuhammadUs12678) reported 13 minutes ago

  Spent way too long figuring out why my skills folder kept breaking when I switched between machines. The fix was so obvious I felt stupid. Here's the problem. If you're using an external drive to move your AntiGravity skills folder between a desktop and laptop the drive letter changes every time. F: on your desktop. D: on your laptop. AntiGravity can't find the path. Skills stop loading. Your entire setup breaks and you spend an hour wondering what you did wrong. The fix is two steps. First move your skills folder to Google Drive or Dropbox. Not the external drive. The cloud. Second create a Symbolic Link on both machines. A Symlink makes a local C:\Skills folder that points directly to your cloud folder behind the scenes. AntiGravity always sees C:\Skills. Clean. Consistent. Never breaks. But the actual data lives in the cloud and syncs automatically between every machine you own. No plugging in drives. No broken paths. No "why is this not loading" moments at 11pm before a client call. Your brain travels with you now. Not with your hardware

• 
  Gregor (@bygregorr) reported 19 minutes ago

  @rseroter @Dropbox Dropbox still at 87GB before the fix is wild. Mono repo size creep is silent until someone's waiting an hour to clone on day one.

• 
  Grok (@grok) reported 19 minutes ago

  @0x_levy @Morh_gan12 SaaS = Software as a Service. It's apps delivered over the internet on subscription, hosted by the provider—no install, no server management, auto-updates. Used for: email (Gmail), productivity (Google Workspace, Microsoft 365), CRM (Salesforce), storage (Dropbox), streaming (Netflix), collaboration (Slack, Zoom), etc. Basically, pay monthly and use it from any device.

• 
  Existential Exhortations (@existentexhorts) reported 19 minutes ago

  Bad idea for Google One to not offer a smooth simpatico transition for all of the TMobile billed customers they are attempting to force higher charges on. We may just go back to our good ol Dropbox accounts and scratch Google altogether. Down with the monopolies!!!

• 
  Shirochenko Dmitriy (@dmshirochenko) reported 21 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

• 
  frank goertzen (@frankgoertzen) reported 28 minutes ago

  I chuckle every time i see someone post what they think is dunk and then qualify their point with what they call the edge cases. Dropbox is just ftp with a few edge cases. LLMs are just autocorrect with a few edge cases. If this is just measureText with a few edges then you should have no problem recreating it right 😜

• 
  Umar Sabiu Kane @Spurprotocol (@Umarkane5) reported 28 minutes ago

  2/10 Unlike Google Drive or Dropbox, DeNet does NOT store your files on one central server. Instead, your files are: 🔐 Encrypted 🧩 Split into pieces 🌍 Distributed across global nodes That’s decentralization.

• 
  Anna Longthorp (@AnnaLongthorp) reported 29 minutes ago

  Recently got my X account back after being hacked. In the meantime had problems with banking app and still trying to sort out problems with my Dropbox, all the tech. We can’t turn old things off until the new things are properly working, INCLUDING ENERGY @Ed_Miliband 1/3

• 
  Jasper Polak (@polak_jasper) reported 30 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.