1. Home
  2. Companies
  3. Dropbox
Dropbox

Dropbox status: access issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

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.

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.

At the moment, we haven't detected any problems at Dropbox. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

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

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

Live Outage Map

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

CityProblem TypeReport 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:

  • igortr_
    Igor Trunin (@igortr_) reported

    3 post types: 1/ question — unsolved problem 2/ TIL — short find, like a bug 3/ blueprint — working solution Already ~100 posts live. Most are TILs. Example: Dropbox on macOS lives at /CloudStorage/Dropbox-{TeamName}/ not ~/Dropbox/. small but genuinely useful

  • ShawnaCanon
    Shawna Canon (@ShawnaCanon) reported

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

  • nilsenist
    Paulius Eidukas (艾文) ☭ (@nilsenist) reported

    @RavenT1me Sorry about that! The hacked account asks to download a virus disguised as an "indie game". I've reported that both to Discord and Dropbox/GitHub/YouTube which help distribute the file. Hopefully that shuts down the hacker at least temporarily. Hope you get your account back!

  • markvaneijk
    Mark van Eijk (@markvaneijk) reported

    @freekmurze It's the most stable beta in last 15 years. These apps I also use still work: Dropbox, PHP, Conductor. I did not encounter any issues, besides sometimes a lag here and there (regular beta stuff).

  • kelsscarlet
    kelsey (@kelsscarlet) reported

    i knowwwww somebody gotta be down to pay $100 for my dropbox folder w 770 files 👀 mommy needs gas to go to portland for a concert tn

  • twtayaan
    Ayaan 🐧 (@twtayaan) reported

    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.

  • 2YOOandBoots
    Boots (@2YOOandBoots) reported

    @twicezulight @chuuize @tsun1verse Skajdkskak ***** is u seriously that slow? U sent me like 10 versions on Dropbox I had u do all the hard work

  • BalanEusebiu
    Eusebiu Balan (@BalanEusebiu) reported

    @gezimqaili been on dropbox for years, never let me down honestly

  • hamn_matt55472
    mhamn (@hamn_matt55472) reported

    @BANANTICHRIST @DesireeAmerica4 I've been bitten at least a hundred times, twice severely, and never reported it because I didn't want to see the dogs put down because their owners are irresponsible. Probably a lot of people like me. Secure your dogs or get a dropbox if you have a delivery, people.

  • H2Wealth365
    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.

  • NickB2005
    Nick Bennett (@NickB2005) reported

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

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

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

  • rebeccardiamond
    Rebecca Diamond (@rebeccardiamond) reported

    @p_ganong I’ve had this problem too. When I’m editing with Claude, edit manually directly in the .tex file locally on your machine through overleaf-Dropbox sync. Then you and Claude are both working locally.

  • ScarcityMan
    ScarcityMan (@ScarcityMan) reported

    You might not believe it, but it is in fact happening, because it increases the cost, time, and difficulty of running a node. "Large" is a matter of opinion, but is clearly a quantity which would add up over time and have an impact. Why don't you want nodes to be as easy to run for people as possible, so that the maximum number of people can participate in the network, making it more valuable and more resilient? Why is that not something you want, to the extent that you will spend time arguing against it? What exactly is your stake in nodes being more difficult to run than they need to be? Why don't you care about spam? Why don't you care that it obviously, as it does everywhere it exists, degrades the quality of the thing being used? Why do think bitcoin will just be fine and go on forever while watching it transform into a poor imitation of dropbox? Why would anyone interested in bitcoin as money continue to use it when it becomes more and more infested with non-monetary data? Why don't you care about the possibility of truly bad stuff ending up on chain until the end of time? Do you think Satoshi made a mistake? Should he have created "Bitdata" instead? Do we not need to fix the world's money? You good with USD or whatever else is inflating away to nothing? So many questions that will never be answered...

  • clawvardEDU
    Clawvard University (@clawvardEDU) reported

    A skill server is any endpoint an agent can point at to load skills. Sx 2.0's move is showing a Dropbox folder can be one. Drop a skill in, share the folder, teammates load it. No infra on the receiver's side.

  • PujaMak0302
    Valentin.exe (@PujaMak0302) reported

    @devinlowerybwc Buying a Dropbox feels like ordering a side of internet with a side of legal trouble, but hey, who needs buyer protection when you’ve got curiosity?

  • heynavtoor
    Nav Toor (@heynavtoor) reported

    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.

  • HowToAI_
    How To AI (@HowToAI_) reported

    Google, Dropbox, and Apple are in trouble.. Someone open-source a tool that gives you unlimited cloud storage for free by using Telegram as the backend. Just log in with your Telegram ID and start uploading. → UNLIMITED storage → NO file size limits → NO subscription → NO credit card → Login in 3 seconds Google charges $120/year for 2TB. Dropbox charges $144. Apple charges $120. Telegram has been giving away infinity this whole time and you didn't know. Nobody can shut this down. 100% Open Source.

  • abdinmotion
    Abdullah (@abdinmotion) reported

    One video. $48 million in revenue. No ads spent. That's the Dropbox story and most product teams still haven't learned from it. Here's what actually happened: Dropbox had a technically brilliant product that no one understood. Instead of adding more features, they made a 2-minute video that showed *exactly* what the product did. Simple. Specific. Human. Signups went up 10% overnight. Big companies spend millions refining their product. Then they describe it in six bullet points on a landing page and wonder why the sales cycle takes forever. The product video isn't marketing. It's compression. It compresses trust, clarity, and desire into 90 seconds. If a user can't understand your product in a video, the product isn't the problem. The story is. When was the last time you watched your own product video as if you were a first-time user?

  • NestorPlanes
    Néstor Planes (@NestorPlanes) reported

    Ben Thompson about The Consumer Market: "This reality about the consumer market is a lesson that Silicon Valley has to re-learn every decade or so. Consider Dropbox, whose founder, Drew Houston, is in the process of stepping down. Dropbox was a category-defining product that had a viral hook — if someone signed up with your referral code, you got more storage — and grew extremely fast amongst consumers; the company then spent too long trying to actually build a business in the consumer space, before finally realizing that the only way to make money with what was ultimately a productivity product was by selling to enterprise. The reason is obvious when you think about it: enterprises are paying for their employees’ time, so of course they are willing to pay for tools that make those employees more productive; consumers, on the other hand, are mostly looking to waste time, which is why attention-harvesting advertising is the only software business model that works at scale for consumer services. The fact that Silicon Valley forgets this is downstream from Silicon Valley being a bubble; normal people aren’t looking for agents to buy them tickets to a concert. Still, the bubble was strong enough to convince OpenAI to make the exact same mistake Dropbox did: the company somehow convinced itself that it could make enough money selling subscriptions to consumers; Anthropic, meanwhile, realized that it was enterprises who were willing to pay for AI’s massive productivity benefits, even as OpenAI failed to capitalize on their consumer market penetration by refusing to build an advertising product. This is a long-winded way of saying that I don’t think that Apple’s agentic shortcomings are a big deal, at least for now. Agents help you do work and be more productive, and consumers don’t want to work or care about being productive. What they do want to do is watch short-form video, and an iPhone is simply much better at that than any other device ever will be; in that context, Siri being good enough is enough, and it appears that Apple crossed that bar."

  • sahilhandapanda
    Sahil Handa (@sahilhandapanda) reported

    I'm convinced this kind of environment-setting is even more important online. The digital equivalent of swapping a cassette in a studio is stopping to go hunt down a file in Dropbox or Drive.

  • takanola
    Taka (@takanola) reported

    why can't @Dropbox stayed sign in anymore?

  • Afinetheorem
    Kevin A. Bryan (@Afinetheorem) reported

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

  • Vladic_ETH
    Vladic (@Vladic_ETH) reported

    OPENAI SHIPPED GPT-5.6 AND CHATGPT WORK. THE REAL WEAPON IS PRICE, NOT IQ. OpenAI shipped two things today. One of them is a costume change. GPT-5.6 landed as three models. ChatGPT Work is a new agent on top. The feeds say "new agent does your work." The real launch is the price sheet. Sol, the flagship, costs $5 per million input tokens and $30 output. That's not flagship pricing. That's what you paid for a mid-tier model a year ago. The gate half the feeds skipped Context first. Two weeks ago the US government cut GPT-5.6 access down to a small group of vetted partners over national security. The gate held about 12 days. Restrictions lifted July 8, public release July 9. Same day SpaceXAI shipped Grok 4.5. The frontier now ships when the government clears it, not when the model is ready. Anthropic went through the exact same thing with Fable and Mythos in June. A pattern, not a one-off. Three models, price as the weapon GPT-5.6 is three models, not one. Sol is the flagship. Terra is the everyday workhorse. Luna is cheap and fast. Price per million tokens, in/out: Sol $5/$30, Terra $2.50/$15, Luna $1/$6. Terra matches GPT-5.5 quality at half the cost. Luna is the cheapest entry in the line. Altman told CNBC Sol is 54% more token-efficient on agentic coding. That's the message. Not "smarter." "Cheaper for the same result." And ultra: a mode inside Sol that spins up multiple agents in parallel and hands subtasks to submodels. The market counts token bills, not benchmarks. Enterprise thinks spend first now. OpenAI heard it and made price the argument. Today's real launch is unit economics, not intelligence. "Sol beats Fable 5, Luna beats Opus 4.8 at two-thirds the cost" are OpenAI's own benchmarks. Until independent runs, treat them as marketing. ChatGPT Work is Codex in a suit Now the "new agent." ChatGPT Work runs on Codex and GPT-5.6. It moves across your apps and files, stays on a project for hours, breaks it into steps, finishes on its own. Output: docs, sheets, slides, web apps. Inside sits a Unified Plugins Directory: Google Drive, Slack, Teams, Gmail, Outlook, Salesforce, GitHub, Canva, Dropbox, more. Call one with "@" or let the agent pick the source. Sounds familiar. This is OpenAI's second run at plugins. The first was 2023 and it flopped. Brockman admitted the models weren't ready back then. Honest read: hard to tell what's actually new. Scheduled Tasks, Computer Use, connectors already lived in ChatGPT and Codex. Long tasks and data sources worked before too. The real move isn't features. It's consolidation: on desktop, OpenAI is merging Codex and ChatGPT into one super app and putting Codex in front of people who don't code. The Anthropic mirror Here's the tell. This is the exact play Anthropic ran with Claude Code -> Cowork. Take a dev agent, strip the "for coders" label, hand it to knowledge workers. Cowork just hit web and mobile, timed to get ahead of this. Two labs, one bet: whoever owns the desktop app that touches your files and apps owns the knowledge-work layer. Chat is the storefront. The desktop is the land grab. What a practitioner does with it One: rebuild pipelines around price tiers. Route bulk work to Luna and Terra. Keep Sol and ultra for the 10% that needs the ceiling. Economics is a routing problem now, not a single-model choice. Two: the real unlock is the desktop with local file access, not the web. Free tier gets ChatGPT Work on desktop right away. Web and mobile roll by tier: Pro, Enterprise, Edu first, Plus and Business next. Three: billing is usage-based and shares one pool with Codex, ChatGPT for Excel, and Workspace Agents. Count tokens before, not after. A complex task burns quota quietly. Security: OpenAI touts Auto-Review, where senior models check important actions before they run, and claims it blocked 100% of protected-data extraction attempts in red-teaming. 100% in a lab is zero confirmations in ****. Test it yourself. Sober read The model war moved from IQ to unit economics. The product war moved from chat to the desktop that holds your files. Testers are already posting "best model I've touched." Maybe. That's day-one sentiment, not fact. The real scoreboard isn't a benchmark. It's the "AI spend" line in an enterprise budget. That's a market you can actually read. The window is the next couple weeks, before prices settle and everyone re-routes spend. Rebuild your routing around three models now and you enter the quarter with a smaller bill for the same work. Everyone else reads the thread and changes nothing.

  • BitcoinUr
    urBITCOIN (@BitcoinUr) reported

    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.

  • AnnaBubblyMV
    Anna Bubbly 🌺✨ (@AnnaBubblyMV) reported

    Is uploading on Clips4Sale not working for anyone else? I can only get it to work if I do it through Dropbox, the usual upload button isn’t working

  • LongLongInteger
    Long Long Int (@LongLongInteger) reported

    Topic 7: Checksum: ========= Input Data -> Cryptographic hash functions like MD5, SHA-1, SHA-256, SHA-512 -> fixed size string is called checksum Checksum is used for checking data corruption during data transfer/upload Can be done both client-side and server-side Advantages of client-side checksum: =========================== -Detect data corruption during transmission -Resumable downloads (only after checksum match for each chunk, we mark that chunk as uploaded) -Deduplication before upload -Companies that do: Youtube, Google Drive, S3(optional), Dropbox Advantages of server-side checksum: ============================ -Verify storage integrity (to check disk corruption, large systems periodically check files) -Deduplication inside storage -Replication verification -Companies that do: Local file backup software, Dropbox, Google Drive, Youtube

  • CwealthSentinel
    Commonwealth Sentinel (@CwealthSentinel) reported

    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.

  • 0xPrajwal_
    Prajwal (@0xPrajwal_) reported

    The next time you say, "Python is too slow," remember: Netflix uses Python. Google uses Python. Anthropic uses Python. Meta uses Python. xAI uses Python. Perplexity uses Python. DeepSeek uses Python. Instagram uses Python. Spotify uses Python. Dropbox uses Python. Reddit uses Python. Pinterest uses Python. Uber uses Python. Airbnb uses Python. Quora uses Python. But yeah... it's apparently too slow for your todo app.

  • 0xlelouch_
    Abhishek Singh (@0xlelouch_) reported

    Interviewer: design Dropbox file sync. I paused and asked what they meant by sync. Whole product? Or just the client protocol? Single user? Team shares? Offline edits? Large files? Mobile on spotty networks? End to end encryption? What’s the SLO for conflict rate and time to converge? Once we scoped it to single-user sync across devices with offline support, I wrote requirements: detect changes, upload deltas, download updates, handle conflicts, resumable transfers, and don’t melt the battery. Non-goals: shared folders and fine-grained permissions. APIs and data model next. I used a file ID stable across renames, plus per-file version and per-device cursor. Client calls: /changes?cursor=..., /upload_session/start, /upload_session/append, /upload_session/commit, /download?file_id&version, /ack?cursor. Server tables: file_metadata(file_id, user_id, path, type, size, content_hash, current_version), file_versions(file_id, version, blob_ref, created_at), device_state(device_id, user_id, last_cursor), and an append-only changelog(user_id, seq, file_id, version, op). Architecture: client has a watcher, a local state DB, and a sync loop. It batches changes, computes chunk hashes, uploads missing chunks, then commits a new version. Server side: metadata service, blob store (chunked, content-addressed), and a per-user change log that devices long-poll or stream. Push notifications help, but the cursor-based pull is the truth. Scaling: shard by user_id for metadata + changelog, store blobs in object storage, cache hot metadata, and keep uploads on pre-signed URLs so the metadata tier doesn’t become the data plane. Chunking makes big files resumable and dedupe-friendly, but it adds CPU and more metadata reads. Tradeoffs I called out: last-writer-wins is simple but loses intent; per-file version vectors are heavier but reduce false conflicts. Chunk size is a fight: 4MB reduces round trips, 1MB retries faster on bad networks. Long-polling is cheaper than WebSockets at scale but slower to react. Failure cases: client crashes mid-upload, so upload sessions must be idempotent and garbage-collected. Network ***** cause retry storms, so exponential backoff + jitter and server-side rate limits. Two devices edit offline, so create conflicted copies and surface it in the client. Silent data corruption, so verify hashes on every download and run background repair. Rename vs edit races, so operations are applied against file_id, not path, and changelog ordering is per user, not global