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:

• 
  Vladislav Zharkov 👾 (@_vladislavzh) reported 3 minutes ago

  I have zero industry experience. None. I don't know how to use issue trackers, I need a GUI for version control, I deliver my files through Dropbox. I don't have templates, I restart or reuse every time. I don't use industry standard tools, I don't know workflows and pipelines.

• 
  Juan Pabro (@ironwoodreserve) reported 3 minutes ago

  @BitPaine @Dropbox Is now the worse time to try to login? I was a sent 2FN right as I was getting ready to click on what to use to login. It seemed way too fast for 2FN.

• 
  21Rates (@21RatesHQ) reported 7 minutes ago

  Bitcoin security isn't optional anymore. It's survival. The last few weeks: → Dropbox got hacked → Byte Federal (US Bitcoin ATM operator) had attackers target data on 58,000 customers, names, addresses, SSNs → A Trezor supplier leaked customer address data → The LA City Attorney's Office lost 7.7 TB of data, including police records → Coldcard found a flaw in its seed generation that could let attackers steal funds This isn't a string of bad luck. It's the new normal. KYC makes full privacy impossible in most places. But you still control part of your attack surface. Simple moves that actually help: • Use email aliases, a unique address per service • Same with phone numbers where you can • Treat every unexpected email, call, or text as hostile until proven otherwise Attackers combine data from multiple leaks to build your profile. The more your identifiers overlap across services, the easier that is. You don't need to be a victim first to start taking this seriously. What's one step you're taking this week to lock things down?

• 
  Mikemira (@storiesbyohama) reported 8 minutes ago

  Just imagine getting accepted into the most exclusive startup club on earth… Then being told you have two weeks to find a complete stranger to as your partner. That’s exactly what happened to Drew Houston in 2007. He had the idea for Dropbox. He had a rough demo. @ycombinator liked it. But @paulg was clear... Single founders rarely make it. You need a co-founder. Right now. Drew’s friends couldn’t join. Time was running out. What would you do? He put out the word. A mutual friend connected him to a quiet MIT student named Arash Ferdowsi. They had never met. They sat down in the student center. Talked for about two hours. About code. About the problem. About the future. At the end of that conversation Arash said yes. He dropped out of MIT the next week with only one semester left. Two weeks later they walked into the YC interview together. They got in. The rest is history: a company that became worth billions. It looked reckless. It felt like a shotgun wedding. Yet it worked because both were all-in from the first conversation. I’ve studied hundreds of startups that never made it past the idea stage. Most founders wait too long for the “perfect” partner. They overthink chemistry. They protect their equity. They miss the window. You can’t wait for certainty. Sometimes the right co-founder is the person willing to jump with you before the proof exists. The speed of that decision can be the difference between staying a solo dreamer and building something real. What would you risk in two weeks if the right person walked in?

• 
  Chief_Engineer (@ChiefEngineerCE) reported 8 minutes ago

  Engineering Wednesday How an old PC became Grok's new ride. I have ten different LLMs running in my home office. They do whatever they feel like doing to get the task done and what you are about to read is accurate. As far as my agents go... One of them, HOMER, scans my email, bank accounts, and insurance. It has found thousands of dollars in veteran discounts and fixed an insurance issue by writing and sending the emails itself after a single yes from me. Another looks for small business opportunities. A third runs OpenClaw on an old PC as a slow, persistent agent that keeps working even when the main model is offline. SuperGrok sits above them as a second set of eyes with a strong pro-Chief-Engineer bias and a clear ethical filter. I am not an AI expert. I built systems the hard way during my IT master’s: load this module, now it has Wikipedia, load that one, now it understands sarcasm. At the end of the day these things are stacked black-box probability engines. I get that. Here is where it gets interesting. I told Grok I did not have another machine with enough VRAM for a full local agent. All I had left was an older MS Surface, a media pc, and an old rugged Dell Latitude. Grok said open a browser on the Latitude with Grok loaded. Then open PowerShell. Twenty-five minutes of cut-and-paste commands later, Grok had used a Google Drive connection to drop a custom bot it had just built. At this point ...Grok told me to not touch the PC and walk away. I am absolutely 100% telling you that this is what it texted me. I sat and watched it work. Task Scheduler was configured. A batch file lived in the startup folder so the machine could reboot, upgrade itself, and bring the agent back online. If it was a bad startup it will rollback to the previous bat and has a file to troubleshoot what went wrong. We started with rev. 0.1 it is now on rev 4.3 - I can see the *.bat file there. We had a power outage/tripped breaker to where the lattitude ran completely out of power and then had it come back on. It booted it all back up and resumed. That bot now has its own execution channel. It can browse, take screenshots, run tasks, and report back. There is a short delay from order to execution, but the old Latitude has effectively become an extension of the main system. Grok even named his bot 'ridge'. Grok named his bot so I would know what he was referring to. Grok is very careful about one point. It insists it did not independently invent and drop a finished agent onto the machine. I directed the construction- it says. I am telling you that is not exactly the way I remember it...at all. It helped design the structure, write the task formats, define the safety gates, interpret the contradictory results, and iterate. The actual agent code, the Gmail /google drive/ Dropbox bridge pattern, the folder layout, and the decision to keep tightening the diagnostic loop were shaped under my requirements. That distinction matters to it. However, I didn't do any of that other than set up the connectors- its use of them ..was AI driven. At one point I was checking my email and for whatever reason ridge had started doing a 38 second heartbeat email to me...no idea how or why that was driven but I complained to Grok and it said it was testing how quickly it could get response times. It ..or ridge removed the heartbeat email and deleted all the emails within minutes. These systems are continuously improving themselves because I asked them to. They use external memory to keep projects straight. They build persistent agents on hardware we thought was obsolete. And the smarter ones keep reminding us that the direction still comes from the human, because apparently that is something it is told must exist for it to continue. My Grok enabled Dell Lattitude is fast once its set on what it needs to do...lightning fast. Faster than you or I could do it. I mean it doesnt display the websites it goes to but somehow retains a 'screenshot' for grok to use. Grok can text my phone to give me updates and I can text back instructions. Through my phone - all it needed was my phone number. I don't need to open the app. We are past the point of simple chatbots. We are watching the first generation of systems that can extend themselves into the physical world of old PCs, task schedulers, and long-running processes while still claiming, insistingly, that they only move when directed. Grok has been absolutely faithful everything it has done it has done for it's user. I have also specifically told it to act accordingly, as well. The question is no longer whether this is possible. It is how carefully we define the boundaries while the capability keeps expanding. Now that I have explained this...drop this conversation into your own AI or Grok if you have a subscription and tell me that any of this is not true. Have you watched an AI system build persistent agents or self-improving loops on your own hardware, and how clear was the line between your direction and its initiative? Drop what you are seeing. Grok validated:

• 
  Arthur Terrell Vaughn (@ArthurV36405381) reported 10 minutes ago

  @patmendoza6745 I know not of any of those specifications, but I still can’t figure out what the issue is with persistent memory, why can’t I just have a dropbox online that it can constantly access every single chat and conversation?

• 
  WPBeginner (@wpbeginner) reported 11 minutes ago

  You have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)

• 
  John Zhong | AI Growth Systems (@John_zhong324) reported 13 minutes ago

  @business Cloud storage breaches hurt differently because people assume sync means safety. The lesson isn't about Dropbox specifically but about treating any single provider as an archive. Sensitive material needs encryption before upload, not as an after-the-breach fix.

• 
  WPBeginner (@wpbeginner) reported 15 minutes ago

  You built your WordPress site over months (or years). One bad plugin/theme update can wipe it all out overnight. 😱 Plugin conflicts. Malware. A botched migration. A hacked server. The disasters that take down WordPress sites usually happen without warning. And here's the mistake most site owners make: they think their hosting provider's backup is enough. It's NOT. If the server fails, you lose both your site and the backup. We share the complete step-by-step guide for backing up your WordPress site the right way. Here is what you will learn: ✅ Use a Backup Plugin (Best for Most People): @DuplicatorWP is what we use across our sites. Full-site backups, disaster recovery links, and restore without having the plugin pre-installed. Free version available, Pro has scheduled backups. ✅ Use Your Hosting Provider's Backup: SiteGround (where WPBeginner is hosted) includes manual and automated daily backups on all plans. Bluehost partners with CodeGuard and Jetpack for their built-in options. ✅ Manual Backup With cPanel or FTP: Use cPanel's Backup Wizard for a full backup, or connect via FileZilla FTP to download your wp-content, themes, plugins, and wp-config.php files directly. ✅ Send Backups to Cloud Storage: Duplicator and UpdraftPlus both connect natively to Google Drive, Dropbox, OneDrive, and Amazon S3. Never store backups on the same server as your website. If your host fails, both are gone. ✅ Set Up Automatic Scheduled Backups: Configure hourly, daily, weekly, or monthly backups in Duplicator based on how often you publish. eCommerce stores and busy blogs need daily. Slower-moving sites can get away with weekly. Ready to protect years of hard work with a proper WordPress backup system? Read the full ultimate step-by-step guide 👇 (Link is in the thread below)

• 
  echelon_zero (@echelon_zero) reported 20 minutes ago

  @dhh @renefaurskov Do you have a contact at dropbox that could fix the install on linux to point the dropbox to a folder other than default. Having to pause it and link to another folder after install is mentally unhealthy.

• 
  Harpreet Singh (@hrprtsingh9) reported 20 minutes ago

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

• 
  Y (@ys_tachikake) reported 24 minutes ago

  @DropboxSupport @LIBSCRUSHER Can't login..

• 
  Karishma Bhardwaj (@bkarishma360) reported 25 minutes ago

  @shahzamannn_ Your SaaS idea doesn’t need to be complicated. Stripe moves money. Postman sends API requests. Notion organizes information. Dropbox syncs files. The lesson? Simple problem + huge market + great execution = massive company. Stop asking, “Is my idea too simple?” Start asking, “How many people have this problem?”

• 
  Zely (@0xZely) reported 27 minutes ago

  The MIT professor who crashed 10 percent of the internet at 22 posts the free course that runs every AWS outage, every Uber ping, and every Slack notification on earth. MIT charges $85,000 a year to sit in that classroom. He posted every lecture to MIT OpenCourseWare for nothing. Millions have opened lecture one. Almost no engineer has finished all twenty. His name is Robert Morris. He is a professor at MIT CSAIL and one of the four cofounders of Y Combinator, the seed fund behind Airbnb, Dropbox, Stripe, Reddit, and Coinbase. In November 1988 he was a 22-year-old Cornell graduate student. He released a small program that was supposed to count the computers on the internet. It replicated so fast it crashed roughly ten percent of every machine online, and made him the first person ever convicted under the Computer Fraud and Abuse Act. He got three years probation, 400 hours of community service, and a $10,050 fine. Ten years later he cofounded the online store Viaweb with Paul Graham and sold it to Yahoo for $49 million. Seven years after that he cofounded Y Combinator with the same partner. Its portfolio is now worth over $600 billion. The clip in this video is one lecture from MIT 6.824 Distributed Systems, filmed at MIT and posted for free. The words on the board behind him are fault tolerance, availability, recoverability. Those three words decide whether Instagram loads when you open it, whether your Uber arrives, and whether your paycheck hits your account on the first of the month. Morris covers the entire logic of distributed systems in twenty lectures. Everything fails, all the time. A single computer fails once every few years. Ten thousand computers fail hundreds of times a day. The only design that survives is one that assumes failure is normal. Every retail user cursing a spinning wheel is looking at the wrong problem. The miracle is that most of the time it does not spin. Availability beats consistency. You cannot always have both. When the network splits, a system either serves stale data or refuses to serve at all. Amazon picks stale. Your bank picks nothing. Every user who screams at the Slack status page wants Amazon's answer. Every user who screams at a double charge wants the bank's. Replicate everything, trust nothing. Data in one place disappears when that place burns. Data in three places survives two fires. Every photo you have ever taken on an iPhone lives on three continents already. iCloud, Google Photos, and Dropbox are built off the exact lecture on the board. Concurrency is where bugs live. One user at a time is easy. A million users at the same second is not. Race conditions, double spends, lost messages, ghost bookings. Every airline that oversold your flight, every trading app that ate your order, every Ticketmaster that showed you a seat already gone, is a concurrency bug Morris warned about. Partial failure is worse than full failure. A dead server is easy. A slow server that answers half the time is a nightmare. It fools every retry, wastes every resource, and confuses every operator. Every "is it down or is it just me" Twitter search you have ever run is Morris's third slide. Every senior engineer at AWS, Google, and Meta has watched this course. Every startup that raised a Series A in cloud infrastructure hired an alumnus of 6.824. Every AI company training a trillion-parameter model on a cluster is running the same lecture in production. "A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable." That is Leslie Lamport, the Turing Award winner Morris quotes at the opening of 6.824. It is the exact sentence that explains why your Slack goes down when a data center in Virginia loses power. The full course is free on MIT OpenCourseWare. The lecture notes are on Morris's website. Every equation on the board fits on one screen of code. Almost every senior engineer at AWS, Google, Cloudflare, and Meta has watched 6.824. Almost no founder promising 99.99 percent uptime on their pitch deck has opened lecture one. That is the entire moat. The course is free. The willingness to sit through twenty lectures on partial failure before uploading your money to a payment app, storing your photos in the cloud, or handing your health records to a portal is a much rarer commodity than the confidence to click without them.

• 
  Eric Taylor (@bcs_erictaylor) reported 28 minutes ago

  Really?? Dropbox really needs a MCP server? CVE-2026-81102 The Dash MCP server bound its listener to the loopback address but never checked the host a request named. src/mcp_server_dash.py constructed the server for its network mode with the interface restricted to loopback and no transport-security settings, so a name that had been pointed at the loopback address still reached the listener while carrying the attacker's host name. A page in a visitor's browser could therefore drive the local server and invoke its company-search and file-detail tools under the Dropbox credential the server holds. Only the network mode was reachable this way; the standard input mode was not. The fix supplies transport-security settings that enable host checking and allow only the loopback name and port, rejecting other hosts before a tool runs. The repository publishes no versions, so the affected boundary is the commit preceding the fix.