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:

• 
  FarhanX_AI (@FarhanBuildsAI) reported 2 minutes ago

  SETTING #1: Startup Apps Nobody Asked For What it does: Every time you install a new program, it quietly adds itself to a list of apps that launch the second Windows boots, whether you use it daily or once a year. Why it kills performance: Your laptop isn't just starting Windows when you power it on. It's simultaneously launching Spotify, Steam, Adobe updaters, Dropbox, Zoom, and a dozen other programs all fighting for the same limited CPU and RAM at once. How to fix it: Ctrl + Shift + Esc to open Task Manager → Startup apps tab. Disable everything except your antivirus and anything you genuinely open every single day. The technician found 19 apps launching automatically on her laptop. She recognized maybe 6 of them.

• 
  160 IQ haver Randy (@MinionTripper) reported 7 minutes ago

  @mittsh why would anyone use dropbox you can just setup an ftp server on a linux machine!

• 
  Chief_Engineer (@ChiefEngineerCE) reported 7 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:

• 
  Guymon Adams (@guymonadams) reported 8 minutes ago

  @BrianRoemmele Man, this seems to be a recurring problem for Dropbox. I remember a similar story several years back about their own employees browsing thru user files. All the reasons I moved over to Sync, a much more secure and respectable alternative.

• 
  AiMind (@AIMind_Ai) reported 16 minutes ago

  A $50 box saves $240 a year on subscriptions and earns $18,000 a year setting it up for clients. No new hardware. Nothing bought at retail. A used office tower. A second-hand drive. One stick of RAM pulled from a dead laptop. The whole build came to 50 dollars. It looks like nothing. Fans humming, one cable to the wall, sitting on a desk next to a coffee cup. The first win is the one nobody talks about. Cloud storage, photo backups, the $20 a month AI plan everyone pays and forgets — all of it moves onto one box you paid for once. 240 dollars a year, gone. The second win is where the money is. Once it runs on your desk, it runs on anyone's. And clients don't pay for parts. They pay to stop bleeding subscriptions. Here's what you actually sell: A private AI trained on their own files, so staff stop pasting company data into a browser. That's $1,500 a setup. A self-hosted file server that kills their Dropbox and Google Workspace bill. $600, plus the relief of never renting storage again. A local automation box that runs invoices, replies, and reports overnight. $900, and it never sends a dollar to a cloud. Then the quiet one: $150 a month to keep it patched and alive. 10 clients on retainer is $1,500 every month before you build a single new one. One setup a week at $1,500 is $18,000 a year. Off hardware other people throw in the bin. I had no degree, no server room, no $2,000 build. Just dead parts and one free weekend. The expensive part of AI was never the compute. It was the monthly bill you agreed to and stopped reading. 50 dollars in. $18,000 out. Same box.

• 
  Tomorrow’s James (@james__art) reported 17 minutes ago

  @wholemars A designated Amazon Dropbox could solve this problem. The drone could detect a Dropbox.

• 
  Fraser (@iamfra5er) reported 19 minutes ago

  THIS GUY WANTED A PLACE TO STORE HIS PASSPORT WITHOUT DROPBOX READING IT so he built an encrypted vault app for himself in a weekend and it's now doing $5k/mo zero startup cost. 85% margins. no ads. just SEO written by an AI agent trained on his emails the agent finds trending topics on reddit every single day, writes an article, translates it, posts it google indexes it in days. 500-600 daily visitors. 4% convert to app store downloads. all running on free cloudflare then ASO does the rest — he translated the app into 36 languages and ranks #1 for "duress vault" in the US app store 80 downloads a day. 9% conversion to paid. completely autonomous most founders obsess over their first 10 customers but this guy got banned from every reddit community and said whatever, I'll just let the robot handle distribution he's an ex-google security engineer who raised hundreds of millions for his last startup so he knows what terrible UX looks like in security apps every competitor either has bulletproof security with unusable UI or easy UI with trash security he just combined both and called it done doesn't even spend time on this app. works on 4 projects at once. lets coding agents build while he plans the MVP is identical to the final product because he built exactly what he wanted for himself no pivot. no customer discovery calls. just "I need this, maybe 10 other people do too" now he's testing tiktok and youtube not even for this app but just to learn distribution for the next one

• 
  EFANI Secure Cellphone Service (@efani) reported 24 minutes ago

  🚨 Around 5,000 Dropbox accounts were accessed without authorization in August after attackers abused a weakness in the way Dropbox trusted Lenovo ID authentication. The attack did not require victims’ Dropbox passwords. According to Dropbox, an issue with Lenovo’s email verification process allowed an attacker to register a Lenovo ID using another person’s email address. Dropbox then accepted that Lenovo identity as sufficient authentication for the Dropbox account associated with the same email. Unauthorized access occurred between August 4 and August 21. Files were viewed or downloaded in fewer than a third of the affected accounts. The security problem here is bigger than one flawed login flow. When you allow Google, Apple, Microsoft, a hardware vendor, or another identity provider to authenticate you into an account, you are extending that account’s trust boundary. Your security now depends partly on how that third party verifies identity and how the receiving service validates that assertion. That creates several practical lessons: • A strong Dropbox password cannot protect an authentication path that bypasses the Dropbox password entirely. • Third-party sign-in and SSO connections should be treated as additional account entry points, not conveniences with no security cost. • Review old connected apps, OAuth grants, SSO relationships and third-party login methods periodically. Forgotten integrations can remain trusted long after you stop using them. • Enable MFA wherever possible. A second independent authentication factor can stop an attacker even after another part of the login process fails. • Sensitive cloud storage deserves extra scrutiny. Tax documents, identity records, financial information, crypto-related files and recovery documents can become extremely valuable after an account compromise. Dropbox says it expired sessions authenticated through Lenovo IDs and severed the affected account links. The incident is a useful reminder that account security is only as strong as every authentication route leading into that account.

• 
  Ryan Babbs (@buckybabbs) reported 24 minutes ago

  Hello @Dropbox, Just this week I have decided to switch cloud service from Google Drive to you and less than 1 week I'm having an issue. I run a wedding film business and am trying to move the same 200GB file to two separate editors for two separate kind of films and one of them is encountering a "link temporarily disabled" message. I tried to research online and made a new folder and copied over the original folders contents and cannot share that either as it says I've exceeded bandwidth limits. This is maddening as I thought I'd picked the good plan (3TB) and was all set. Please advise asap as I need these files in my editors hands stat.

• 
  Joachim Voth (@joachim_voth) reported 28 minutes ago

  @DropboxSupport why can I only use one core for indexing? Most machines have MANY nowadays. Download speed is not the issue, it is almost always the ultra-slow indexing that dropbox does with only one CPU core active. Am I seeing this right? Why can we not dedicate 5 or 8 cores to something that really slows down your users?

• 
  Shadow_Vortex_2025 (@Shad0wV0rtex) reported 29 minutes ago

  @FrancoisOlwage @bot I ran into a similar issue just trying to connect Dropbox, ClickUp, and Google Sheets, and all my tokens were already gone.

• 
  Lisa (@aikens_lisa) reported 30 minutes ago

  @TaiyoDevil I printed out fics before I had an e-reader called Dropbox. I was there when Tumblr fell. I had to scrape fan sites and the half-good alternatives to get my fix! AO3 is the best thing to happen to fandom. And you can put pictures on them!

• 
  chaos (@konig0000) reported 32 minutes ago

  Solution of yesterday’s question: Design Google Photos: the part after the boxes “Hash it and put it in S3” fails the interview. Two phones compress the same sunset differently. Same photo. Two hashes. Two rows. You just built a worse Dropbox. The system needs three IDs, not one. client_upload_id — generated on the device before the first byte moves content_hash — hash of the exact bytes you received asset_id — the thing the user sees in the library Uploads are sessions. Library entries are assets. Blobs are renditions. If you collapse those into one key, retries, edits, and shared albums all collide. 1. Retries must be idempotent on the client, not on the filename Phone goes offline mid-flight with 612 shots, 40 already half-uploaded. Each photo gets a client_upload_id the moment it enters the queue. Chunks are uploaded against that ID. Commit is PUT /uploads/{id}/complete. Same ID + same bytes → same session. Server returns the existing asset. Late packet after commit is a no-op. Filename + timestamp is not an ID. Camera roll and AirDrop will mint two. 2. Exact dupes are content-addressed. Near-dupes are reconciled. After commit: look up sha256(bytes) if it already exists for that user (or the shared album’s owner set), attach the new upload to the existing asset_id do not create a second photo The 28 shared “Goa 2026” shots that are almost-but-not-quite the library copies will miss on sha256. That is expected. Run a cheap perceptual hash (pHash / dHash) + capture time + camera model from EXIF. If distance is tiny and captured within a few seconds, mark as near_duplicate_of and do not show two tiles. Keep both blobs if you must; hide one in the UI. Two devices, two compressions, one photo in the grid.

• 
  Nhu Huu (@nhuhuu7) reported 33 minutes ago

  @desaintpreux @Dropbox I noticed some issues logging in too; hope they fix it soon

• 
  Mikemira (@storiesbyohama) reported 33 minutes ago

  Twitter did not explode online first. It exploded in a hallway. In 2007, Twitter was still small. Most people online did not care. So the team did not try to shout at the whole internet. They went to SXSW. They put two big screens in the corridor. People at the event sent a text. That text showed up on the wall in front of everyone. One person posted. Ten people saw it. Then those ten posted too. That is how usage jumped. Not from a giant ad. From one room full of the right people. This is the growth lesson most founders miss. You do not need the whole market on day one. You need one place where your first users already stand. A campus. A conference. A WhatsApp group. A Discord. One street. One event. Dropbox did this on Hacker News. Tinder did this at campus parties. Airbnb did this when hotels ran out of rooms. If signups are slow, stop spraying ads everywhere. Find the one room. Make the product visible there. Let people watch other people use it. That is how early growth actually starts. I'm Miracle Ohama, a Growth Marketer helping B2B SaaS & tech companies find and fix revenue leaks across their funnel, I fix Growth Funnels & build real experiments that increase ARR.