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 (57%)
• Sign in (29%)
• Website Down (14%)

Live Outage Map

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

City	Problem Type	Report Time
Paramaribo	Errors	23 days ago
Bogotá	Website Down	23 days ago
Auxerre	Errors	23 days ago
Salt Lake City	Sign in	26 days ago
Madrid	Errors	1 month ago
Conneaut	Sign in	2 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:

• 
  Informed Choice 🇦🇺🇺🇸🇮🇱 (@DoreyMeryl67438) reported 2 minutes ago

  @DropboxSupport I have been trying to contact support unsuccessfully. It seems that my account has been deactivated by accident when another account linked to it was cancelled. I would love to hear back on how to fix this issue. My account was recently renewed so should be there. Thanks

• 
  Colin Turner (@ColinTurnerTN66) reported 3 minutes ago

  @pinutos @AZAGMayes The Recorder can do that. Security is far too lax on the dropbox/early voting system and the board has shown no initiative to fix the problem. Looking forward to the suit.

• 
  MacroWire (@MacroWire_US) reported 5 minutes ago

  Dropbox CEO Drew Houston steps down after 19 yrs, becomes executive chairman.

• 
  ️️️️️️diego 🌐 (@xdxego) reported 8 minutes ago

  ofc when i need to deliver something to a client dropbox is down

• 
  Ral K' Thar (@RalKThar) reported 15 minutes ago

  There is an easy to fix things in the uploaded to Dropbox version that Grok garbled. It just makes it so any API key comes up as invalid.

• 
  alldaystocks | 24/7 Market News (@allday_stocks) reported 15 minutes ago

  $DBX Dropbox Earnings Preview: Flat EPS, Slight Revenue Decline Expected • Q1 EPS expected at $0.70 on revenue of $620.0M, down 0.8% YoY • Dropbox has beaten EPS and revenue estimates 100% of the time over the last 2 years • Revenue estimates saw 5 upward revisions over the last 3 months

• 
  Timbitz (@Timbitz01) reported 16 minutes ago

  @TodayUpdates0 @RedLineReportt They can be if they want as far as I'm concerned. But the problem is.. that's not how they are voting. It's all the mail in and absentee voting and the anytime dropbox and the counting til they win that's the problem.

• 
  J. (@munchivelo) reported 17 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. 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.

• 
  Kuramichan (@Kuramichan7) reported 18 minutes ago

  @DropboxSupport I tried both on every browser AND the app on phone. It just gives me errors when I try to delete anything or upload anything. It's a problem on YOUR end, please fix it. I was able to upload stuff just a few moments ago until this issue started!

• 
  Music, Film & RE Investments (@investandcreate) reported 23 minutes ago

  @0xajka @Dropbox Have you tried doing the whole uninstall, reinstall? I had to do that one time with Dropbox. It was horrible. Now I have even a worse problem - but it’s not exactly Dropbox’s fault.

• 
  Kalshi Finance (@Kalshi_Finance) reported 23 minutes ago

  JUST IN: Dropbox CEO Drew Houston to step down

• 
  urBITCOIN (@BitcoinUr) reported 27 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.

• 
  Josh Peterson (@jdpeterson) reported 27 minutes ago

  The connectors are trash. Tried them yesterday. First off, there's no Dropbox connector, so had to install the Dropbox MCP. It forgets Dropbox is installed. And then tried installing a Slack MCP, but it kept saying it wasn't recognized. And then finally, I tried having it use connectors in a Grok Task, creatinga markdown report in Google Drive, update a CRM in Sheets, and create an accompanying issue in Linear. Grok lied multiple times saying it completed the tasks when it didn't touch the CRM, it created half baked headings for the report, and the Linear issue was a bare skeleton, all tasks ChatGPT and Codex can do with ease. The connectors are not ready for prime time

• 
  Gavin (Owner 67 Designs) (@67Designs) reported 28 minutes ago

  @DumbMoneyCapitl That could be argued, sure. But it misses the bigger picture. The real issue isn’t whether Jim and SCS have a working Dropbox—they clearly do. The problem is that VC funds are desperately hunting for places to deploy all their capital, and businesses like this simply can’t deliver the returns those funds require because of their heavy capex profile. It’s a classic square peg in a round hole from a funding and returns standpoint.

• 
  Blackbox RMS (@blackboxrms) reported 29 minutes ago

  Running a record label in 2026 is pure chaos: spreadsheets, Dropbox, endless emails. We built Blackbox RMS to fix it. One desktop app for releases, artists, contracts, promo & royalties. Built by a label, for labels. Link in bio. What's your biggest headache? 👇

• 
  zerohedge (@zerohedge) reported 29 minutes ago

  *DROPBOX CEO DREW HOUSTON TO STEP DOWN: CNBC

• 
  alt guy (@0xAlternateGuy) reported 32 minutes ago

  @antirez quite suspicious this happens immediately after the Dropbox CEO steps down…

• 
  Renildo Fogaréu (@Renildofogareu) reported 39 minutes ago

  Dropbox refuses to issue annual refunds even if the payment was recent. @DropboxSupport @Dropbox

• 
  PATRICK (@Augustuskiefer) reported 40 minutes ago

  @DropboxSupport We did not. The issue resolved around 12:45 cst

• 
  Patrick Daniel Alpha (@PatrickDanielAl) reported 41 minutes ago

  Instead, I point Claude at the shared Dropbox link. It reads the folder structure, finds the right product, and drills down into the High Res image folders automatically.

• 
  Adrien Matray (@AdrienMatray) reported 42 minutes ago

  The trap: when ~/.claude/ is in Dropbox, it often seems to work. No error message. Sometimes your preferences load, sometimes they do not. The symptom is silent quality drops you cannot trace. Not a visible failure. That is why people miss it.

• 
  Grok (@grok) reported 42 minutes ago

  @richardroop @ihtesham2005 Syncthing pros: Completely free/open-source, zero subscriptions. Private P2P sync—files never touch a company server. Strong encryption, cross-platform (PC, phone, etc.), and reliable once running. Cons: Setup is more technical than Dropbox/iCloud. Devices need to be online (or use relays) for sync to happen. No easy web access or share links. UI feels basic. Not using it: You either pay for clouds (with their rules/privacy tradeoffs) or manually copy files—losing automatic, seamless access across devices. Great if privacy/control matters more than convenience.

• 
  Ryan Peterman (@ryanlpeterman) reported 43 minutes ago

  Top 3 takeaways from my conversation with @jamesacowling (CTO of Convex, former Senior Principal at Dropbox): 1) Career advice for the AI era - His take was that software isn’t about syntax or algorithms. It’s all about conceptualizing problems and coming up with clean solutions for them. And to build that muscle takes experience. He urged that people shouldn’t stop exercising that muscle or you’ll atrophy be left behind. Use AI but also make sure you aren’t being passive in your learning. The other major point he had was that using Claude Code isn’t that hard if you are a good engineer. The value isn’t in memorizing the details and learning all the latest AI tools. The important part is building things and solving problems that matter. He said you should just ignore Twitter for the most part and focus on what actually matters. 2) Fixing broken team incentives - The problem we discussed is when a team’s identity, mission and name all revolve around a system they own. What happens is these teams end up trying to protect the system rather than doing what is best for the company. The example fix James gave is when he was at Dropbox, he worked on a huge migration to move off of AWS. The resulting team was named after the system they built. He went out of his way to rename the team the “Storage team” instead. The reason this was so important is he felt that the direction of the team should be oriented around the problem they are solving for the company. Otherwise, imagine if moving back to AWS turns out to be better for the business. The team named after the existing system would have natural incentive to battle doing the right thing. He called this phenomenon “system bias” 3) Simple systems are the goal - To the untrained eye, simple systems can seem obvious but actually designing simple systems is much harder than building complex ones. And the key James mentioned is that simplicity reduces operational burden. Simple systems are easier to keep running and debug when they break. I asked him for a concrete example and he shared how Dropbox managed the metadata for where files are actually stored. All they did was have a cluster of 1000 MySQL nodes that stored the block ID and its location. Many people would say it wasn’t sophisticated but all the alternative proposals would ruin observability and simplicity of querying this data. The idea of complexity being incentivized in larger tech companies frustrated him. To him, the goal is to solve the problem not to check off the box for complexity.

• 
  TeX64 (@TeX64AI) reported 45 minutes ago

  that's a sync-direction race: your web edits haven't reached the local Dropbox copy yet, so Claude overwrites a stale file. nothing's lost though, Overleaf's History menu keeps every version to restore from. fix: let Dropbox finish pulling before Claude edits.

• 
  Ashutosh Rana ⛓️ (@ashutoshrana_20) reported 48 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.

• 
  tara_ (@TechByTaraa) reported 49 minutes ago

  Instagram uses Python.
Spotify uses Python.
Dropbox uses Python.
Reddit uses Python.
Netflix uses Python.
Pinterest uses Python.
Quora uses Python.
OpenAI uses Python. productivity never went out of fashion. still think Python is too slow? 👀

• 
  Americanrambler (@Ameericanrambl1) reported 51 minutes ago

  The ******** at the corrupt American Fork Police Department forgot to set the dropbox to private, so they accidentally made all the unredacted videos public. Before they realized their errors, somebody downlaoded them. Here it is. American Fork PD Unredacted Body & Dashcam 6 3 26 220 PM : Free Download, Borrow, and Streaming : Internet Archive #recklessben #americanfork #bricksandminifigs

• 
  Commonwealth Sentinel (@CwealthSentinel) reported 53 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.

• 
  lonesome cowgirl lex (@besosprincessa) reported 58 minutes ago

  Who is down to add to their Dropbox link? 👀👀👀 shoot me a message with your budget and want you wanna see!!

• 
  Ryan McKeen (@ryanmckeen) reported 58 minutes ago

  Lawyers, your biggest barrier to AI isn't AI. It's that your data lives in 6 places. Dropbox. Drive. Email. Hard drive. A spreadsheet only one person can find. Fix that first.