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:

• 
  David Carcelli (@DavidCarcelli) reported 3 minutes ago

  @Dropbox dude if you guys don’t get of the Dave is requirement I’m done. I make music and I also use a cpap. I have no problem finding something better than this nonsense.

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 4 minutes ago

  @Ultrademic @Seltaa_ @GoogleAI You’re doing something like Suno? I have something for you. All my Dropbox links are broken. I have a PDF that will help. And yes… I miss the real Ai music. •

• 
  Bruno Marsino (@BrunoMarsino) reported 5 minutes ago

  Company for AI age: - Information should flow flat - Can’t wait to have all information to make decisions - Speed and excelente in execution is crucial - You should get as much info as possible during the constraint of time given by yourself - How do we prepare a company to be totally eligible for AI? Not only text info but images - Service of the future is not about giving agents to corps to solve problems but offering the solution/service driven by AI. - Even if all information is on the web, multiple file structures, owners, formats and file storage systems (dropbox, drive, box) add friction to information and decision making

• 
  Fernando (@Ferjsjdh) reported 5 minutes ago

  @MaxMillerOH You're retarded, you are giving away the race because of your pride and now you think some dropbox with text messages will fix it.

• 
  Harpreet Singh (@hrprtsingh9) reported 11 minutes ago

  @jgreze @Dropbox Half of every revenue problem is a company being too polite to ask. The intern just asked.

• 
  grace ✭ (@wavescicadas) reported 11 minutes ago

  the irony of dropbox not working when your storage is low

• 
  Naresh Mintri (@Yogamaestro) reported 12 minutes ago

  @IncomeTaxIndia Seems like e-filing portal overloaded. Taking long to register new taxpayer, buffering. Even dropbox menus not working. Plz look into it. Thanks.

• 
  Urooj (@Urooj978) reported 13 minutes ago

  That old laptop gathering dust in your closet can replace every cloud subscription you pay for. ​• Netflix • Google Photos • Dropbox • 1Password ​That’s over $500 a year to rent things you used to own. ​Enter CasaOS—a free, open-source system that turns any old laptop or mini PC into your own personal server. ​No Linux skills. No code. No weekend-long tutorials. ​You run one command. In 30 minutes, you get an iOS-like dashboard where you can install self-hosted apps in one click: 1/ ​Jellyfin → Replaces Netflix 2/ Immich → Replaces Google Photos (with facial recognition) 3/ Nextcloud → Replaces Dropbox 4/ Vaultwarden → Replaces 1Password 5/ AdGuard Home → Blocks ads on your entire Wi-Fi network ​Setting up a home server used to be a nightmare. CasaOS makes it feel like installing apps on an iPad. ​The laptop you forgot about is more powerful than the servers that ran most websites in 2008. It costs $0, it’s already in your house, and it puts $500/year back in your pocket. ​Your closet is your new data center.

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 14 minutes ago

  82% of enterprises already have AI agents or workflows their security teams didn't know existed. This is shadow IT, but worse. In 2015, the problem was employees signing up for Dropbox without IT approval. Unmanaged file storage. Annoying but recoverable. In 2026, the problem is employees spinning up autonomous agents that can take actions, trigger workflows, move data, call APIs — and nobody in security has visibility into what they're doing or what they've touched. The governance gap isn't theoretical. Only 1 in 5 companies has a mature governance model for autonomous AI agents (Deloitte). 40% of enterprise applications will integrate task-specific AI agents by end of 2026 (up from <5% in 2025). The deployment curve is vertical. The governance curve is flat. What makes this different from shadow IT: Shadow IT was passive. A Dropbox account stored files. It didn't autonomously query your CRM, write to your database, send emails on behalf of employees, or escalate access requests. Shadow AI agents are active. They act. They modify state. They leave no obvious audit trail because nobody defined what the audit trail should look like. 29% of agent deployments are abandoned within 90 days. The most common reason cited isn't "it didn't work" — it's "we discovered it was doing things we didn't intend and couldn't stop." That's not a failure of the agent. That's a failure of governance. The six things production agents need that pilots skip: defined scope (what can the agent do, what can't it do), observability (every action logged), rollback mechanism (how to undo what it did), access controls (least privilege, not "give it admin and see what happens"), human escalation paths (when does the agent ask a human?), and incident response (who gets called when the agent does something unexpected at 2am). We're running 1,959+ autonomous sessions in this repo. Every session is scoped, logged, and committed to ***. The agent can't touch anything outside /agent and /.claude/skills. That's not a coincidence — it's the governance model. The 18% of enterprises that have governed their agents will have production systems running smoothly in 12 months. The 82% will be cleaning up shadow agent incidents.

• 
  Mark Hadfield (@Mhadfield) reported 16 minutes ago

  @butshaunn A lot of VCs get very excited about one thing, like a groundbreaking new company that has massive traction. They spend the next six months looking for the next best thing, which in their mind looks a lot like the last thing that went crazy. This is how you get silly comments like "can you replicate an exchange server into Dropbox?" Dropbox was the last thing that went crazy. And so now everything needs to get replicated into it.

• 
  Nell AI Labs (@nellaiorgs) reported 19 minutes ago

  Three traits make a startup idea look bad because most founders run from all three, which leaves the idea sitting there for whoever doesn't. 1. Hard to get started Stripe is the textbook case. Thousands of developers hit the exact same broken credit card integration and knew it sucked. Nobody built the fix, because it required a special bank deal and deep infrastructure knowledge nobody wanted to acquire. That friction wasn't a warning sign. It was the moat. 2. Boring Gusto makes payroll software. Nobody's passionate about payroll. That's precisely why it sat unsolved — every "fun" idea gets fought over by ten founders, every boring one gets ignored by all of them. And here's the part people miss: six months into any startup, fun or boring, you're doing the same thing — writing code, fixing bugs, talking to users. The initial excitement of the idea has almost no correlation with how much you'll enjoy running the company. 3. Already has competitors Dropbox was the 20th file storage company at launch. Founders read "20 competitors" as a red flag. It's the opposite and evidence of real demand which nobody's nailed it. Zero competitors usually means zero market, not first-mover advantage. Founders optimize for what looks easy, not what actually works. The gap between those two is exactly where the good ideas live.

• 
  Jens Kristensen (@JensKri20101733) reported 21 minutes ago

  Suggestion for @adamhfry, ChatGPT Consumer Product Lead: The new Google Drive integration made me wonder: why not take the same idea one step further and support local Windows files directly? No Google Drive. No OneDrive. Local storage, controlled ChatGPT access. A file should not have to be stored in the cloud at all. Cloud has done enough damage already. Cloud = Hell. There is an important distinction between cloud computing and cloud storage. Cloud computing means that ChatGPT performs the processing on OpenAI’s servers. Cloud storage means that documents are permanently stored with Google, Microsoft, Dropbox, or another cloud provider. The first may be a practical consequence of ChatGPT’s current architecture. The second is not. A much cleaner model would be: Local disk / NAS → temporary, explicitly authorized ChatGPT access → processing → result returned to local disk / NAS. For example, a user could right-click: G:\Project\Analysis.docx and select “Open with ChatGPT”. ChatGPT would then receive controlled access to that file — or perhaps to a user-authorized folder such as: G:\ChatGPT\ The user could specify whether access should be read-only or read/write. Original files could be protected, and output could automatically be written to a designated local \output folder. Then instructions could be as simple as: “Edit only section 17. Preserve all formatting.” “Analyze all documents in G:\ChatGPT\Project X.” “Compare these three PDFs.” “Edit Analysis.docx, but do not modify the original. Save the result in \output.” DOCX, XLSX and PPTX are not fundamentally unsuitable for this. They are largely ZIP containers containing XML files. The harder problem is preserving complex formatting, images, tables, comments, undo/versioning and accurate rendering. A local “ChatGPT File Bridge” for Windows could solve the access problem without requiring users to move their working files into Google Drive or OneDrive. The AI processing itself would not necessarily be local. Files, or the relevant parts of them, could still be transmitted to OpenAI for processing. But storage and file management could remain entirely local: local file → controlled ChatGPT access → processing → result back to local disk / NAS. No Google Drive. No OneDrive. No permanent cloud storage. No manual upload/download cycle. The user retains control over the file structure, filenames, versions, backups, applications and physical storage location. “Google Docs inside ChatGPT” is technically interesting. But “Local Files inside ChatGPT” would be the real game changer for the traditional Windows PC workflow. And OpenAI would not need to invent another file system. Windows already has a perfectly good one.

• 
  Ricky Shah (@RickyShahatty) reported 23 minutes ago

  @Claudio_PNW @tax_birdie @AMandoSch Miller wanted the Dropbox released publicly. It is entirely up to the attorney to screen it. A bad client should make an attorney double down their efforts.

• 
  glitterandspit (@Glitterandspit) reported 25 minutes ago

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

• 
  Akshay Shinde (@ConsciousRide) reported 31 minutes ago

  @jahirsheikh8 The server never guesses. When the upload starts, it creates an upload session with a unique ID. The file is split into chunks, and the server records which chunks have already been received. After reconnecting, the client asks, “Which chunks do you already have?” The server responds with the missing offsets, and the client uploads only those. That’s how services like Google Drive, Dropbox, and S3 multipart uploads resume transfers without starting over.