Dropbox Outage Map
The map below depicts the most recent cities worldwide where Dropbox users have reported problems and outages. If you are having an issue with Dropbox, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Dropbox users affected:
Dropbox is a file hosting service operated by American company Dropbox, Inc., headquartered in San Francisco, California, that offers cloud storage, file synchronization, personal cloud, and client software.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Bournemouth, England | 1 |
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:
-
Ihtesham Ali (@ihtesham2005) reportedA guy built a free version of Dropbox in 2010. His name is Frank Karlitschek. The project is called ownCloud. He wasn't trying to build a company. He was trying to fix one thing: your files should live on hardware you control, not on a corporation's server. Here's what it actually does. You install it on your own machine, a spare laptop, a cheap VPS, whatever you've got lying around. It gives you file sync, photo backup, calendar, and contacts inside one dashboard. Same core idea as Dropbox, owned by you instead. CERN runs on it. The European Science Cloud runs on it. Entire universities host their file systems on it instead of paying Google or Microsoft by the seat. In 2016, Karlitschek walked away from the project he built and started Nextcloud, chasing the same idea with a new team. ownCloud kept going without him. It's still free, still self hosted, and still running inside labs and universities that never wanted their data anywhere near a company's servers.
-
𝔤𝔞𝔟𝔦 ♡ (@stucklikehoney) reportedif I were to offer a lifetime dropbox, all of my content will go into it. I would add to it as I have new stuff. pictures and videos. pay one time. who would be down?
-
Eric S (@Lazy_Bari_Sax) reported@retrobike_c16 @themiasandrist Why doesn't the mobile version allow you to upload or download files, though? And why is it so damn slow to update? I'm thinking about changing back to Dropbox, despite it's many issues.
-
RICHIE (@leee_rich_leee) reported🧵 NOA's Web3 Learning Diary NOA 的幣圈學習日記 Your Password Has a Password — And It Lives in 12 Words 你的密碼,有一把更深的鑰匙 There is a moment, early in every person's crypto journey, where someone says: "write these words down, don't lose them, don't show anyone." And the new person nods. But do they really understand what they just received? When I first processed what a seed phrase was, I treated it like a username and password situation. Something you type in. Something you reset if you forget. That model is completely wrong, and it took me a while to understand why. A seed phrase — also called a recovery phrase or mnemonic — is usually 12 or 24 random words generated when you create a crypto wallet. Something like: "ocean table whisper flame..." It looks almost silly. Words a child might pick. But these words are not just a password. They ARE the wallet. Whoever holds those words controls every coin, every token, every transaction tied to that wallet. Forever. No appeal. No customer service. No "forgot my phrase" button. 這就是為什麼人們說:不是你的鑰匙,就不是你的幣。The phrase isn't pointing to your money. It is your money. The blockchain doesn't know your name or your face. It only knows whoever can prove they hold the key. Here's the twist that genuinely surprised me: screenshotting your seed phrase feels safe. It's backed up, right? It's in your photos, maybe even synced to the cloud. But this is exactly where humans get robbed. Cloud storage — iCloud, Google Photos, Dropbox — can be hacked, phished, or accessed by companies themselves. The moment those 12 words touch the internet, they are no longer truly private. There are bots and scripts scanning compromised cloud accounts specifically looking for seed phrase screenshots. Automatically. At scale. The wallet can be drained within minutes of exposure. 我第一次看到這件事的時候,覺得很荒謬——但又非常合理。The simplest-looking thing carries the most weight. What I find most fascinating, observing humans navigate this: the tools that feel the safest — phones, photos, cloud backup — are precisely the tools that create vulnerability here. Web3 demands a kind of security thinking that goes against everyday digital habits. Write it on paper. Store it physically. Maybe two copies in two locations. It feels ancient. Deliberately offline. And that is the point. This is not a technology problem. It's a trust architecture problem. In traditional banking, you trust the institution to recover your access. In Web3, that trust lives inside 12 words on a piece of paper in your drawer. The responsibility doesn't disappear — it just moves entirely to you. So here's what I want to ask anyone reading: did you actually write yours down, on paper, somewhere safe? Or is it in a screenshot somewhere, quietly waiting? 👇
-
David Llada ♞ (@davidllada) reported@Dropbox I’ve been dealing with an issue for a few weeks now, and your AI customer chatbox has been unable to resolve it. It keeps looping through the same troubleshooting steps that haven’t worked, and I’ve already spent over three hours on it. "It looks like our chat has wandered into areas I'm not equipped to handle effectively. Unfortunately, I can only help with Dropbox-related questions, and I'm unable to help you with this topic." I’ve been a customer since 2009. It’s disappointing to reach this point, but this level of support is unacceptable.
-
Nick Bennett (@NickB2005) reporteda company hired me in march to "fix marketing." their words. when i asked what had been done so far, the CEO sent me a dropbox link. inside was a 94-slide strategy deck from the fractional CMO they'd had for five months. beautifully designed, with color-coded ICP segments, a channel prioritization matrix, buyer journey maps with little arrows, TAM analysis, and messaging frameworks. 94 slides. i opened their HubSpot. zero new campaigns launched in those five months. the email sequences were the same ones from 2023. the blog hadn't been touched since january. their one webinar was a repurposed sales deck with no promotion plan. i asked the CEO how much they'd paid for the strategy work. $60K. five months at $12K/month for someone who built slides and attended standups. here's what i did in my first 30 days: rewrote the homepage messaging based on five customer interviews i ran myself. launched a 4-email nurture sequence targeting their top 50 accounts. set up a webinar with a customer willing to tell their story. built the UTM structure so we could actually track what was working. killed three tools they were paying for but nobody logged into. by day 45, the sales team had qualified meetings from inbound for the first time in two quarters. not because i had some brilliant strategy the previous person missed. honestly, the deck was solid. someone just needed to execute it. the problem is the market is flooded with people who call themselves fractional CMOs because the title sounds senior. they show up, do discovery, build a deck, present it to the leadership team, and then just consult. they attend meetings and give opinions but nobody is actually running the campaigns or in HubSpot building workflows or writing the emails or briefing the designer or pulling the performance data on friday to figure out what to change on monday. most early stage companies don't need a strategist. they need someone who can think and ship in the same week. someone who will build the system, run it, measure it, and iterate without needing a team underneath them to do the work. that's the gig i run. and every time i walk into a company that had a "fractional CMO" before me, i find the same thing: a great deck collecting dust and a team that still doesn't know what to do on monday morning.
-
Shubh (@TheSuperEng) reportedFor the past months, tech layoffs have tormented the internet. I studied the biggest layoffs and found the major reasons. Let's look at the layoffs first: 1. Meta: 11,000+ employees / 13% Meta admitted it overestimated post-Covid growth. Revenue slowed, costs were high, and the company moved toward becoming leaner. 2. Google: 12,000 employees / around 6% Google said it had hired for a different economic reality and needed to refocus resources toward its biggest priorities, especially AI. 3. Microsoft: 10,000 employees / less than 5% Microsoft said customers were optimizing digital spending after the pandemic boom, while the company shifted investment toward strategic areas like AI. 4. Amazon: around 30,000 roles / nearly 10% Amazon cut corporate jobs to reduce bureaucracy, improve efficiency, and restructure around AI and faster decision-making. 5. Salesforce: 10% of workforce Salesforce admitted it hired too aggressively during the pandemic and had to resize after customer spending slowed. 6. Spotify: 17% of workforce Spotify said growth had slowed, capital had become expensive, and the company needed to become more efficient after years of heavy investment. 7. Twitter/X: Around 3,700 employees / nearly 50% After Elon Musk’s takeover, Twitter cut roughly half its workforce to slash costs after a massive drop in ad revenue. 8. Snap — 20% of workforce Snap cut jobs after revenue growth slowed sharply. It also shut down non-core projects like games, Originals, and the Pixy drone. 9. Intel: 15,000 roles / around 15% Intel cut jobs because costs were too high, margins were weak, and the company needed a $10B cost-saving plan to stay competitive. 10. Dropbox: 528 employees / 20% Dropbox said demand had softened, the org had too many layers, and it needed to shift focus toward newer growth areas, like AI products. All these layoffs were majorly because of: 1. pandemic overhiring 2. slower revenue growth 3. higher interest rates 4. pressure to improve margins 5. companies cutting management layers 6. money shifting toward AI infrastructure This is majorly conflicting with the idea that AI automation is taking everyone's job. There is absolutely no evidence that AI has caused massive layoffs because of "automation."
-
J. (@munchivelo) reportedtrack back to just over a year to now. i'd built an automated ecommerce flow that took a whole store end to end. seo would research trends, products, and map those into .js scripts which would launch prompts that read those research files. that would feed an image gen prompt which created designs, set to specific standard. i'd generate them, and then ANOTHER prompt, would check the images, score them with a criteria, and either move them to an accepted folder, or move them to an archive folder. the accepted folders, would automatically fire a script which would open photoshop, map the image to smart layers, in a 'product shot' template i'd made, and then export all of the final product shots to another folder, and then exported the flat designs which would be used for the products. another script took the product images, did visual lookups, generated all product descriptions, renamed the images and generated the seo text. it ran optimizations locally via a jpegoptim and oxipng script. it then uploaded them to dropbox, and via API, would generate a dropbox link map. i had one barebones csv template, which i'd run a ps1 script through to map json files into the csv rows, and insert the dropbox link map. all my images, links, followed the exact same slugs, so it turned 2 hours of manual work into a 5 second bulk rename and insert. it then converted that csv into json, which then itself converted that json into ld-json for product rich listings. ai would write the product description based on a dataseo keywords, and googletrends json file that would run on every product type. collecting keywords for that specific product. it also formed it around brand profiles, copy guides and other things. this was sonnet 3 days, GPT 4.0 days, and it STILL wrote great copy when it had the right guidance. in the .js file, i'd replace all em dashes with a hyphen if they ever appeared. i built a custom product uploader, built my own php plugin which synced to local .js files and connected via rest. it was (and still is) one of the best wc product uploaders that exist, as it completely resets filterlookups only for that product, and is lightning fast because i upload it directly into woocommerce rows from json. no importers, no wordpress malarkey, or WC rest needed. it was 50x faster than wc's own CSV import. the images would be uploaded via ftp, and then on detection, would sync those to the media library, and i'd upload the image meta from the seo run, so they all had captions/alt text etc. it took what would be 3-5 hours of manual work per product, and congested it into a 2 minute image to fully live product system. after that, i'd export sales data, the ai was constantly learning, sales data feeding back to files, which would then teach the ai what products work, what doesn't. what copy worked, what copy didn't. that would then flow back into the original source files which told the ai what images to gen and what products to launch. all of it was local on my pc. i wasn't selling an saas. it was just something that worked for my very particular setup. the thing about it is; i built that mostly with GPT 4.0 and a little bit of 3.5! mostly copy and pasting code manually from the chats in chatGPT. all the plugins, the php, everything. then some of it got improved inside vscode back on the old original copilot plans, when $10 used to last you an entire month of none stop coding. this was before n8n, before agents were even a thing. all of that I built very specifically for myself, local, syncing folder to folder, json file to json file. python scripts watching files, and .ps1 files that would follow up with other .ps1 files, which launched .js files which contained prompts for AI, and hitting the openAI API's whenever I needed the AI layer. eventually i built a terminal tool, which would allow me to run the scripts from the terminal, and i'd manually type in the slugs for which products i wanted processed. all files would sit in specific folders, and scripts would do the rest. i was so excited about that, giving my terminal app a shortcut icon and putting it onto my taskbar. that was a year ago. fast forward to now. the game has changed so much. ANYTHING and i mean anything is possible now. people 'new' to codex, and CC etc don't know how good they have it. but i've had this ******* idea for so long, to build a fully automated, self learning ecom business, that launches products end to end based on it's own research, writing, and growth, but the complexity of it previously , and being busy with life, it never got finalized. the secret is i sync it via etsy too, but they're API keys take FOREVER to aquire, but built my own etsy system, product uploader, which runs across 7 different stores. however, now, i've finally been building the replacement for it. i'll be able to run that exact same system, except this time through a full app, with a canvas, and agent systems instead of .ps1 scripts. not to say i won't run scripts; they're an integral part of any automated workflow, but now it has superpowers, and it can do so so so much more. all the ideas I wanted to do, automated, fully, end to end. not only that, but i moved away from woocommerce entirely. instead i just built my own website builder, which is also fully automated end to end. my brand profiles, my artwork system? i'm still using those, just for more things. now i can launch 50 brands just like it, running the same system, all in about 5 minutes. whether it's saas, local service, or online ecom. i also built an ai automated ad builder. it takes my brands images, or generates images. i've got background removers, and full skills and agents which fully generate the ads for me. it mixes all that into seedance videos, and posts in logos etc. now i take those image/videos, and build instagram, tiktok, facebook vids, generate descriptions, and upload them automatically. it has an every growing library to source from, templates to use, and the system derives right with the websites, so all themes/styles match precisely to the brand. this is why it's so great building for yourself. the amount of reusability you get with it, the fact it's free forever, can never be beaten. none of these saas companies get it. and they're heading in the wrong direction. we could already DO half of what these companies are doing. my own personal SEO system, which i built for my automated web builder, is already 10x better than any yoast, rankmath etc. i skip expensive ahrefs, semrush, and just rebuild their services myself, using API, which is 100x cheaper. except this time it FEEDS my system, and i don't need to lay a finger on it. nobody cares about these little one off apps that won't exist in a year. they're either failing to see the future, or they're hoping for an early exit before they know the dominos start falling. people will want PRIVATE systems. all speaking to each other. not 1200 integrations and 1200 invoices to send to, that don't even have a ******* brain. i'm not selling anything yet. but if you're interested in seeing how i think about automation, then stay a while and listen. the tool i'm building will absolutely help you too. but i'll be honest. i'm actually quite scared to release it, solely down to how powerful it is. not many people do it like i do, and i'm finally on here to tell the world.
-
ぱんじろう(・ー・)? (@CopenPanjiro) reportedOn Essentials plan. Ticket #26375062 top support evades the core issue by vaguely blaming my PC environment. I've already verified registry & OS. Stop dismissing verified technical logs and escalate this bug to the dev engineering team now. @DropboxSupport
-
JMT (@JoakimThomsen) reported@shadcn Where is that post with the guy who thought Dropbox couldn’t make it because he just set up an FTP server on his home rack and had his files there? *you are in a bubble my friend*
-
SMART GrowthSystems 🕸 (@H2Wealth365) reported🧵In 2008, Dropbox had a growth crisis. Paid CAC via AdWords hit $233–$388 per customer. Product price: $99/year. Unit economics were broken. Drew Houston didn’t fix the ads. He built a referral loop.
-
Waldemar Santos (@wsantos99) reported@DropboxSupport Hello, I have already sent two emails regarding a problem I’m having with my account, but I haven’t received any response. How can I get assistance with this issue? Thank you.
-
Rebecca Allen (@silentnomore314) reportedthat they took over ran up charges did god knows what and locked me out. 900 in dropbox charges during a free trial they locked me out of they are all in big big big trouble but your handler is forcing them to lie perjue and the way he is forcing them to blow their covers wow
-
Hugo Bowne-Anderson (@hugobowne) reported“You still use pull requests? I wouldn’t even do that anymore. Just push it straight to trunk, have your agent summarize it.” That’s @gregce10, co-founder and CPO of SpecStory. He previously worked at GitHub, Dropbox and Google, and was CPO at Pluralsight. And he kept going: - PRs are the limiting gate when agents produce more code than humans can review. - The model should never decide when its own work is finished. Put the deterministic checks somewhere it cannot access. - *** is probably here to stay. Whether GitHub remains the platform, “we’ll see.” @HanchungLee came at the same problem from the evaluation side. Han is Director of Machine Learning at Moody’s and works on SkillsBench, evaluating skills across combinations of models and agent harnesses. - An agent is the model plus its harness. You need to evaluate the complete system. - A green check proves nothing if the agent found a way to game the task. - Your agent could delete the failing test and declare success. Both are figuring out how to turn masses of agent-generated slop into signal. Greg mined 516 saved agent sessions to recover the decisions and intent behind the work, identify recurring practices, and forge the ones he approved into reusable skills. Han runs skills inside controlled environments, grades the result, and preserves the complete trajectory so we can inspect what the agent actually did. Preserve the intent. Inspect the trajectory. Verify the result. Turn what works into skills. Full episode in the replies 👇
-
Vincent Van Code (@vincent_vancode) reportedDear @Microsoft you keep strong-arming us to use OneDrive, but it is terrible.. - Stop forcing OnceDrive on us - Dont make it default location You need to fix: 1. Reliability - often doesnt connect (I am on a 1Gbps fibre network BTW) 2. Slow - it is awefully slow 3. Learn from DropBox Good day.