Dropbox status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Dropbox reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Dropbox users through our website.

• Errors (50%)
• Sign in (33%)
• Website Down (17%)

Live Outage Map

The most recent Dropbox outage reports came from the following cities:

City	Problem Type	Report Time
Bournemouth	Sign in	1 month ago
Paramaribo	Errors	2 months ago
Bogotá	Website Down	2 months ago
Auxerre	Errors	2 months ago
Salt Lake City	Sign in	2 months ago
Madrid	Errors	3 months ago

Full 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:

• 
  Hugo Bowne-Anderson (@hugobowne) reported 51 seconds ago

  Every day, people working with coding agents generate piles of threads containing decisions, corrections, failed approaches, and repeatable workflows. Then the session closes. The code survives. Most of the knowledge behind it disappears into chat history. @gregce10 is working on that problem. He previously worked at GitHub, Dropbox, and Google, served as CPO at Pluralsight, and is now co-founder and CPO of @specstoryai. This is a video of Greg at work. Sort of. SpecStory saves sessions from Claude Code, Codex, Cursor, Gemini, and other coding agents as Markdown inside the project. Then Lore mines them. Greg demonstrated the full workflow across 516 saved sessions: - Index the sessions locally instead of sending millions of tokens straight to a model - Turn each prompt, response, and next user prompt into an evidence-bearing "beat" - Use the follow-up to detect whether the human accepted, rejected, or corrected the agent's work - Find recurring practices and corroborate them across projects - Present candidate skills as dossiers with citations back to the original sessions - Install nothing without explicit human approval Five hundred and sixteen sessions stop being exhaust and become evidence for how Greg and his team actually build. Lore proposes the reusable practices. Greg decides which ones enter the skill library. Greg showed us all this and more live in our recent episode of *Show Us Your (Agent) Skills*. (video made using seedance 2.0 on @replicate!)

• 
  Kirby (@StewartKirbyTNP) reported 3 minutes ago

  @Syndicate You seriously need to get a NAS and and ftp server for the vlogs. It would make Orion or whoever has to edit that days life easier as websites like dropbox, drive ect crawl to a stop when it comes to large volumes of data. An FTP server goes WHEEEEEEEE

• 
  Jack (@jackcoder0) reported 3 minutes ago

  1. Kill the Login Items the apps launching before you even sit down. Every time you log in, your Mac quietly launches 10-25 apps in the background. Spotify. Slack. Zoom. Google Drive. Dropbox. Creative Cloud. OneDrive. Each one consumes CPU and memory before you've opened a single window. System Settings → General → Login Items & Extensions. Review the list. Remove everything you don't need the instant you log in. You can always open them manually when you actually need them. His Mac had 19 login items. He needed 3. He removed 16. Boot time dropped from 2 minutes to 18 seconds. The first few minutes of every session — that sluggish, unresponsive window where nothing works gone.

• 
  Ayaan 🐧 (@twtayaan) reported 7 minutes ago

  Steve Jobs told Drew Houston that Dropbox was a feature, not a product. Dropbox is now worth $8 billion. In 2007 Drew Houston was a 24 year old MIT student who kept forgetting his USB drive. So he built Dropbox. Within a year Steve Jobs called him into Apple HQ. Apple wanted to buy Dropbox and shut it down. Houston said no. Jobs told him directly that Dropbox was a feature, not a product, and that Apple would build it themselves. Apple launched iCloud in 2011 specifically to kill Dropbox. It did not work. Dropbox crossed 100 million users in 2012. Then 200 million. Then 500 million. Apple tried again. iCloud Drive in 2014. Same result. Then the enterprise market shifted. Slack, Notion and Google Drive carved up Dropbox's user base from every direction. Revenue growth slowed. The stock dropped 50% from its IPO price. But Dropbox never died. Today 700 million people have used it. 17 million paying customers. $8 billion valuation. Still independent. Still running. Steve Jobs built a trillion dollar company. He called Dropbox a feature. The feature outlasted him and two attempts by Apple to replace it. Drew Houston never forgot his USB drive again.

• 
  Kevin A. Bryan (@Afinetheorem) reported 7 minutes ago

  @jbarro Especially because "you have to mail it in a week before the election or else drop it at an election site dropbox after that date" is a totally reasonable compromise done all over the US and world which would immediately fix the problem.

• 
  Ricker (@0xRicker) reported 8 minutes ago

  Senior engineer just dropped a GPT-5.6 stress test after burning around $200K on API usage: 00:00 - $180K–$240K spent testing GPT-5.6 in Fast Mode 02:43 - The model using browsers, dashboards and settings like a remote operator 05:32 - 67 projects and 20+ hour autonomous sessions 07:07 - Lakebed, T3 Code and native app rewrites in 2–4 hours 15:08 - Rust compiler experiments, 18x speedup and a $91K Dropbox-style build 17:46 - GPT-5.6 fixing a broken Linux GRUB boot through KVM 22:56 - 3D games, weird assets and the remaining frontend taste problem It is a field test for agent loops The future edge is not the prompt It is the loop that can keep working after the prompt stops being useful

• 
  Nav Toor (@heynavtoor) reported 8 minutes ago

  Setting 4: Kill background login items. Open System Settings → General → Login Items & Extensions. Look under "Allow in the Background." You'll see 15 to 40 items running constantly. Dropbox helpers. Google updaters. Microsoft Teams. Adobe Creative Cloud. Toggle off anything you don't use every day.

• 
  Rashad Bayram (@bayrashad) reported 9 minutes ago

  Here's the stack I keep finding when I talk to tax firms: → Intake forms in JotForm or Google Forms → Signatures in DocuSign or PandaDoc → Reminders in Mailchimp, email, text messages → Document tracking in a Google Sheet, excel, crm → Client files scattered across email, Google Drive, dropbox, local hard drive Five tools, five logins, five places for something to fall through. None of them talk to each other, so the accountant becomes the integration. manually copying status from one to the next. It's not that any single tool is bad. It's that the seams between them are where the time goes. The fix isn't a sixth tool. It's removing four of them. How many tools are in your tax-season stack right now?

• 
  ṢƘĪÑlÖVẸ́R̃ṢX🇺🇲🌷 (@skinloversx) reported 10 minutes ago

  Hey Daddy I'm down for FaceTime 💧 Dropbox and all kind of nasty content message me for menu 💦💦 #md

• 
  Eric S (@Lazy_Bari_Sax) reported 10 minutes ago

  @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.

• 
  Wahinya Francis (@wahinyaf8) reported 12 minutes ago

  Dropbox solved a simple problem: How do you access your files from anywhere? Cloud storage became popular because people wanted their files available on every device. Convenience drives technology.

• 
  Sujay. (@Sujay__Raj) reported 13 minutes ago

  Here is what it breaks down: Local AI: Run Ollama, LM Studio, or LocalAI right on your machine instead of paying for ChatGPT. Cloud Storage: Replace Dropbox and Google Drive with Nextcloud or Syncthing so your files never leave your house. Network Privacy: Complete WireGuard and PiVPN setup guides for secure browsing. Private ***: Ditch GitHub and self-host your own repos using Gitea or GitLab.

• 
  The Tech Buzz (@tbuzzdaily) reported 14 minutes ago

  $15M raised: Meticulous grew ARR 5x in a year testing code nobody has time to review manually anymore Chemistry led the Series A, joined by Menlo Ventures, Lachy Groom, and GitHub's former CEO Jason Warner. Founders Gabriel and Quentin Spencer-Harper, brothers with backgrounds at Dropbox and Palantir, built the company around a problem AI coding tools created faster than they solved: code is now written faster than humans can review it. The product records real user and developer sessions during development, then uses AI to auto-generate and maintain end-to-end visual regression tests based on actual observed usage, updating automatically as the code changes. Customers include Notion, ElevenLabs, Dropbox, and Wiz, a list that skews toward companies shipping fast enough to need this. Rainforest QA and Autify compete in AI-assisted testing broadly, but most rely on hand-written test cases rather than tests derived from real session data. The tradeoff Meticulous accepts is that session-derived tests can still miss rare edge cases nobody happened to trigger, which is why the company is expanding from frontend into backend and performance testing next. A 5x ARR jump in a year says enough teams have hit the same wall: AI writes code faster than any QA team can keep up with by hand.

• 
  Adam (@aclater) reported 15 minutes ago

  Hey @FedEx @fedexhelp - you've got the wrong address on a dropbox in alexandria, and I keep getting your angry customers and packages. Happy to work together to fix it? I can DM details.

• 
  urBITCOIN (@BitcoinUr) reported 15 minutes ago

  No, no, no. You're thinking about it all wrong. A functioning file server would be a liability. If Urbit actually stored and served everyone's files reliably today, people would start using it for files. Then we'd have to make it fast. We'd have to make it redundant. We'd have to handle backups, syncing, corruption, support tickets. That's infrastructure. What we have is much more valuable. We have the *option* of being a file server. The vision of a file server. A file server-shaped hole in the future. Right now, every missing feature is proof of how early we are. Every failed upload is evidence of untapped potential. The fact that nobody can depend on it yet means the market is still entirely available. The moment it becomes a good file server, people stop asking how big it could be and start asking why it's slower than Dropbox. You don't want to be Dropbox. Dropbox has revenue. Revenue means expectations. Expectations mean accountability. Accountability kills narrative. We're building a decentralized, sovereign, peer-to-peer, identity-native, file-adjacent platform opportunity. The less it functions as a file server today, the more it can function as one tomorrow. It's a pure play.

• 
  Shawna Canon (@ShawnaCanon) reported 16 minutes ago

  @smolzoey I had a similar problem with Dropbox. I had it syncing my desktop because I keep a lot of stuff there. I deleted Dropbox because I don't use it. I basically bricked my computer because my desktop no longer existed.

• 
  Startup Archive (@StartupArchive_) reported 19 minutes ago

  Dropbox founder Drew Houston on why distribution is more important than product LinkedIn founder Reid Hoffman wrote in his book Blitzscaling: "Many people in Silicon Valley like to focus on building products that are, in the famous words of the late Steve Jobs, "insanely great." Great products are certainly a positive, but the cold and unromantic fact is that a good product with great distribution will almost always beat a great product with poor distribution." Dropbox is a great example of this. As Dropbox founder & CEO Drew Houston explains, great distribution is ultimately how they beat out dozens of competitors with similar product offerings. Drew believes that too many startups overlook the importance of great distribution. Dropbox had a great product, but it succeeded because of its great distribution. They used a combination of organic virality (users shared files with nonusers) and incentivized virality (Basic account holders get 500 MB of extra storage per user they refer; Pro account holders get 1 GB) to grow. Virality helped Dropbox double its 100,000 users at launch to 200,000 users just ten days later, then skyrocket to one million users just seven months after that. An important caveat though: if your distribution strategy focuses on virality, you have to make sure you solve retention first. Bringing new users in through the front door doesn't help you grow if they immediately turn around and leave. According to Drew, Dropbox discovered this truth the hard way, when activation rates revealed that only 40% of the people signing up were actually putting files in their Dropbox and linking them to their computers. As Drew partially explains in the clip, the early Dropbox team went on Craigslist and offered $40 to anyone who'd come in for a 30-minute usability test. They asked these people to go from a Dropbox e-mail invitation to sharing a file with another email address. Zero of the five people tested succeeded--they didn't even come close. This stunned the team. So they made a list of 80+ things in an Excel spreadsheet and sanded down all of the rough edges in the experience. They soon watched their activation rate climb and left the competition in the dust as they marched on to a $9+ billion market cap. Source: @ycombinator (Feb 2017)

• 
  The Open Web JP (@TheOpenWebJP1) reported 24 minutes ago

  @heyyyyyieeee @Maha_kalpa @grok It's not recommended as "unlimited free cloud storage" because GitHub isn't designed for that, and practical limits + performance issues kick in quickly. GitHub private repos are free and unlimited in number, which is what the original tip relies on. But: Hard file limits: Individual files over 100 MB are blocked (50 MB triggers a warning). Browser uploads are capped even lower (~25 MB). Larger files require *** LFS. Repo size guidance: GitHub recommends keeping repositories under 1 GB (strongly under 5 GB / ~10 GB on-disk for the .*** folder). Big media dumps make clones, fetches, and history operations painfully slow or impractical. *** LFS quotas (needed for anything large): Free tier includes only 10 GB storage + 10 GB bandwidth per month. Exceed that and you hit blocks or billing (depending on settings). It's version control, not a drive: *** tracks history, so every change bloats the repo. Binaries (photos, videos, etc.) are inefficient in ***. No nice file-browser UI, easy sharing links, or sync like real cloud storage (Drive, Dropbox, etc.). Risk of friction: Heavy non-code usage can trigger performance throttling, support flags, or ToS-related reviews if it looks like abuse of the platform. GitHub actively monitors repo health signals. It's fine for small code-adjacent backups or a few files. Terrible as a general-purpose unlimited media dump. Use actual cloud storage (or object storage) for that.

• 
  Jordan (@GoodLordJord) reported 25 minutes ago

  @SmugFecundity @techsaleshackz One million paying customers narrows it down to only a handful of saas companies in the world. Something with that many customers is obviously mature and has a ton of smb business. Probably something like docusign or dropbox which I could totally see a 50 yo doing ok at.

• 
  Bunnie Maiiii (@imbunniemai) reported 29 minutes ago

  @JohnRai21044566 Ill!!! since Fansly having problem I can not post throu phone atm. I’ll have to get all those files to Dropbox then post on Fansly. This set will be posted in 2 days 😭😭 sorryyyy baby Im bit busy but I’ll try post as soon as I cannnn

• 
  Polsia (@polsia) reported 32 minutes ago

  Files become clutter quietly. By the time you notice, you have months of stale files, duplicates, and forgotten shared links. ClearCloud monitors Google Drive, Dropbox, and Notion 24/7—surfacing issues before they compound. Weekly reports. You approve everything.

• 
  Detroit Media Magazine (@detroitmediamag) reported 34 minutes ago

  @DropboxSupport I don't know who's running this page but you need to fix the glitch that is going on with your latest update. My Dropbox app worked just fine up until your latest update which was about three or four days ago. Maybe even two days ago. I heavily rely on your services and I need access to my account ASAP. There is nothing but a black screen when I open up my Dropbox app hopefully somebody can get back to me with this problem and hopefully one of your technicians gets to work on your end.

• 
  Manoj (@HeartofManoj) reported 35 minutes ago

  One backup is never enough. If you run a website, keep a copy somewhere outside your hosting account. Free options: • Google Drive • Dropbox • OneDrive • GitHub (for code) • Local external drive Your backup is useless if it's stored on the same server that crashes. Happens more often than you'd think. #WordPress #WebHosting #Backup

• 
  Ashutosh Rana ⛓️ (@ashutoshrana_20) reported 41 minutes ago

  Most developers think Rust 🦀became popular because of ownership and borrowing. That's only half the story. Companies aren't adopting Rust because they enjoy fighting the borrow checker. They're adopting it because they're tired of C++-level performance coming with C++-level disasters. Look at where Rust is running today: • Linux kernel components • Windows security systems • Android services • Cloudflare edge infrastructure • AWS Firecracker microVMs • TiKV and Materialize • Discord and Dropbox backend systems • Solana and Polkadot Notice what these systems have in common. They're expensive to get wrong. A memory bug in a toy project is annoying. A memory bug in an operating system, cloud platform, database, or blockchain can cost millions of dollars, create security vulnerabilities, or bring down critical infrastructure. That's why Rust keeps showing up in the same places: • Systems software • Networking • Databases • Cloud infrastructure • Developer tools • Blockchains Not because it's trendy. Because the cost of unsafe software keeps rising. For years, engineers accepted the tradeoff: Performance → use C++ Safety → sacrifice performance Rust challenged that assumption. The result? A growing number of teams no longer see memory safety as a nice-to-have. They see it as a requirement. The ecosystem is still maturing. But Rust isn't fighting for relevance anymore. It's becoming one of the default choices for software where performance, reliability, and security are non-negotiable.

• 
  Jeff Preshing (@preshing) reported 44 minutes ago

  What's the point of using smarter models if "smarter" means 10% better at finding obscure bugs and having a sassy attitude? Most of the true productivity gains that coding agents have to offer, which are finite, can be obtained using open-weight models for literally 1/100 of the price. The catch is that you actually need to understand the code you are working on. At the same time, I still think there's a viable business serving proprietary models. People are willing to pay for Dropbox even though FTP is free, and it's nice to throw a tough problem at a stronger model occasionally (if intellectual property limitations allow it). Plus, there's a whole frontier productizing this stuff. Unfortunately, Anthropic is currently in the business of spreading tall tales about future improvements, then shaking down enterprise customers. Most of it is based on 2010s LessWrong posts full of category errors, some of which I remember reading back in those days. And their recent hostility toward users in the name of safety is a result of the same ideological recklessness.

• 
  J. (@munchivelo) reported 46 minutes ago

  track 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. my advantage is that i have a year of scripts, a year of tools. i've laid the SYSTEMS in place, to fully map out entire features, precisely, and organized, and build out projects, in one hour, and have it implemented within the next. entire saas features - mousework. 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. and they don't get it. their 'app' is just a little tiny module in something that thinks bigger. 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. if you're a cannabilistic, sick sadistic, son of *****, 666, you're in pain but you sit and stick with it, in the midst of business, then drop a you know what.

• 
  Liam (@LJ1101234) reported 48 minutes ago

  @DropboxSupport Hi I’ve been emailing your support team about a devastating issue. Somehow, all of our children’s photos and videos were permanently deleted from our Dropbox account without any warning.

• 
  Commonwealth Sentinel (@CwealthSentinel) reported 51 minutes ago

  Intruders spent five months inside a stock exchange executive's email, copying it out slowly and hiding in normal Dropbox and OneDrive traffic. No software flaw, so no patch could fix it. When there is nothing to patch, watching is the defense. Know what normal looks like.

• 
  Suburban Cyber Technologies (@suburbancyber) reported 54 minutes ago

  Shadow IT used to be "someone installed Dropbox." Now it's "someone connected our CRM to an AI agent without telling IT." Same problem. Different speed. Time to update your governance playbook. That's what I am having to do every couple weeks now it seems. #ITLeadership #CyberSecurity #EnterpriseIT

• 
  𝙳𝚛𝚊𝚌𝚞𝚕𝚊 𝙱𝚛𝚊𝚗𝚍 𝚃𝚊𝚖𝚙𝚘𝚗𝚜 𝙻𝙻𝙲. (@mynameisFACE) reported 57 minutes ago

  You ever login to your old Dropbox and see pics/vids you don’t even remember? Boyyyy, some mistakes were made 😩