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.

• Sign in (40%)
• Errors (40%)
• Website Down (20%)

Live Outage Map

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

City	Problem Type	Report Time
Bournemouth	Sign in	2 months ago
Paramaribo	Errors	3 months ago
Bogotá	Website Down	3 months ago
Auxerre	Errors	3 months ago
Salt Lake City	Sign in	3 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:

• 
  Ihtesham Ali (@ihtesham2005) reported 2 minutes ago

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

• 
  Teja Punna (@punna_teja) reported 3 minutes ago

  Indian Government: "We've blocked Telegram to protect the NEET exam." The Internet: So the problem was... Telegram? Not the people selling fake papers? Not the organised scam networks? Not the thousands of mule bank accounts? Not the hundreds of disposable SIM cards? Not the fake payment gateways? Not the people exploiting students' panic and desperation? Solution: Block Telegram. Meanwhile: ✅ Discord still exists. ✅ WhatsApp still exists. ✅ Signal still exists. ✅ Slack still exists. ✅ Email still exists. ✅ Google Drive still exists. ✅ Dropbox still exists. ✅ OneDrive still exists. ✅ iMessage still exists. ✅ Bluetooth still exists. ✅ AirDrop still exists. ✅ The entire web still exists. Scammers: "No problem. See you tomorrow on another platform." Meanwhile, millions of legitimate users who rely on Telegram for: College and study groups Open-source communities Cybersecurity research Software development Startups and businesses Education and learning News and information sharing are left wondering what they did wrong. The platform changes. The abuse doesn't. Target the criminals. Not the communication tools.

• 
  Aaron Li (@polymorpher) reported 9 minutes ago

  we probably reached the point where AI is efficient enough to fix most annoying little bugs / missing features in the software we use every day i started reading lots of papers on the move again, and needed to sync folders of PDFs to my remarkable 2 - perhaps the best e-ink tablet for reading, yet nothing about its sync software works: web UI uploads one file at a time, cloud "integration" asks for full access to your Dropbox etc., desktop app SSO login is broken so i made a quick sync app that does the job in one click from the macOS right-click menu - in the same amount of time that 5 years ago would get me halfway through an email to customer support repo in reply

• 
  Santiago Bustelo (@sbustelo) reported 9 minutes ago

  @DropboxSupport THEY ARE GIVING ME CANNED REPLIES. YOU SCREWED MY WORK AND BURIED ME FOR THE FOLLOWING MONTHS TO FIX UP THE MESS YOU MADE UP WITH MY FILES. I DEMAND A REFUND.

• 
  yera. (@1stplaceee__) reported 9 minutes ago

  You down for my nasty FaceTime and Dropbox video HMU📨📥💦🍑

• 
  Ayaan 🐧 (@twtayaan) reported 13 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.

• 
  Rashad Bayram (@bayrashad) reported 13 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?

• 
  RyanFox.eth (@ryanfoxeth) reported 16 minutes ago

  “consumer doesn't run on problems” 👏 Consumers will pay to be entertained. Businesses will pay to be productive. This is a lesson the tech industry is forced to learn every decade or so. Apple, Microsoft, Google, Mozilla, Dropbox, Evernote, Quip, AirTable, Trello, etc have all learned this the hard way. We saw it play out in crypto. Today it’s playing out in OpenAI vs Anthropic.

• 
  The Open Web JP (@TheOpenWebJP1) reported 16 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.

• 
  Santiago Bustelo (@sbustelo) reported 17 minutes ago

  @DropboxSupport More details? “I am really sorry for any inconvenience this is causing. We'll update you shortly on this issue.    In the meantime, please let me know if you have any further questions.   Best regards,  Jesse | Advanced Support” That’s the “support” I’m getting. FULL REFUND NOW

• 
  SMART GrowthSystems 🕸 (@H2Wealth365) reported 17 minutes ago

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

• 
  meshgear (@_meshgear) reported 19 minutes ago

  @Dropbox It is not working.

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

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

• 
  Grant B. (@GrantB423) reported 21 minutes ago

  yo Sam, anyway you could dm the Dropbox link for your “ghosts’n’stuff” remix? it was taken down off every single platform @Jauzofficial

• 
  Kieran 🥃🎶🐇 (@KGeorgee) reported 28 minutes ago

  @datarade NET? Probably region of 45% 5k+ companies now? Not all are exits or in cash yet will be propped up a lot on Stripe dropbox doordash coinbase if we go gross probably close to 70% by now? Some bad perfromers in there of course too that will bring it down. nuts figure ngl

• 
  Hugo Bowne-Anderson (@hugobowne) reported 29 minutes 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!)

• 
  FiL Dev (@FiLHashDev) reported 32 minutes ago

  I’m hesitant to work with Jira again. Co-Founder wants it. My issue is that we don’t have a source of truth. Two brains, agents, & knowledge bases, leaves room for a lot of drift. Any suggestions? I’m thinking GitHub read only repo access might be the vibe. We also use Dropbox sync for artifacts. I just think a third central brain = more tokens and more drift. Might just have to build a full AgentOS.

• 
  uncle ***** (@probinsyacore) reported 33 minutes ago

  nraas still down but a reddit user has saved most of their mods in a dropbox link oh my god sometimes i do love the internet

• 
  Random Poser (@rndposer) reported 37 minutes ago

  @iHerbMiddleEast Problem with iHerb is your delivery service to consumers. They’re a challenge to work with. I wouldnprefer if there is option to get my deliveries directly in a dropbox somewhere near and not go thru the 3rd party delivery service.

• 
  Peter Lake (“world’s anonymous singer songwriter”) (@PeterLakeSounds) reported 40 minutes ago

  @taobanker I might suggest another question: what should you avoid? In that context the multi-trillion dollar bet will have terrific returns. That also means that the money making machines of US won’t accumulate money and accrue value unless there is persuasive evidence that at least the big spenders on data center capex get their money back. Given this is unknown, I assume markets are skeptical. If the largest companies in S&P and all the rest don’t have excess free cash, and plausible they don’t go up a lot. That would yield maybe an on average flat market. The flip side is that models are open, massive parameter models getting quantized will be in windows machines. Silicon Valley and early adopters are doing fascinating things. But for the rest of us, I need nice and simple. And for the first time we’ll have good old home computers that can do the job and with that comes free use from heaven. Outside of specialized discussions people don’t know much about what to do with this. The jardon doesn’t help: context window? Quantized models? Nodes are not parameters, they are like neurons, and AI is so dangerous, but not it’s not…what a world! The really final blow is government intervention now makes it a sovereign requirement for companies to have their own AI. LASTLY! I’ve been thinking about the data holders. box. Dropbox etc. Absurdism and it’s comparables will become a bigger deal as people start to realize they the context “window” = the files and stuff you want it to analyze = can only handle so much Imagine of Box or Drop box had a button that converted all your stuff in MD files or the like? Then it’s show time. The companies that hold data may be more valuable than I realize. Conclusions based on the above speculation: 1) could this impact demand at the data centers? Sure it can. I know tech investors like to hold out their hands palms out and say…something vague and qualities. Yes, data centers are more sophisticated etc. Yet here I was doing some interesting work on a FREE local model, my “dark tokens” are someone else’s lost revenue! How does this math work? No clue. It is telling, however, that NVDA and AMD are committed to local machines. No large company wants model dependency anyway, due to data concerns. 2) Finally I have a great reason to buy a slick cool PC! The higher end stuff will not be throttled down in local because I’m seeing a bunch of them coming our way that will have decent “bandwidth” RAM in addition to high system ram. We’re going retro and this tech is moving so fast. Adoption will increase once you have super good local models on your laptop. …Im falling asleep, but the gist is that the data centers were already speculative, and now we a lineup of expensive but sweet computers running on windows that gives you infinite and faster foundational level stuff.

• 
  kelsey (@kelsscarlet) reported 41 minutes ago

  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

• 
  Abhishek Singh (@0xlelouch_) reported 43 minutes ago

  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

• 
  Long Long Int (@LongLongInteger) reported 43 minutes ago

  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

• 
  Waldemar Santos (@wsantos99) reported 45 minutes ago

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

• 
  Sunil Thakare 🇮🇳 🦀 (@thakares) reported 47 minutes ago

  @TLYShortener offering a genuinely useful, privacy-friendly app (no login, no ads) that seamlessly integrates with the company's core product (t_ly short links), is indeed a standard growth tactic seen in tools like Canva, Notion, or Dropbox. The QR app lowers barriers for users while creating natural upsell opportunities: frequent QR creators may later pay for t_ly analytics, custom domains, or branded links without feeling forced. Trade-off is transparent here; users get a solid free scanner but feed data into t_ly's ecosystem, which benefits the provider through increased link volume and potential premium conversions.

• 
  Paulius Eidukas (艾文) ☭ (@nilsenist) reported 49 minutes ago

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

• 
  🔆 j i k o ⋆₊ ‧ ˚⊹ 🏜️ (@lisey_ann) reported 52 minutes ago

  @joinautopilot @charliebilello I can see why a bunch of those are sagging (joke? Or maybe I'm not joking): - Snapchat is in decline, less users overall. - Streaming subscriptions are becoming too expensive to keep up w/ inflation - X likely sagging ever since its lead advertisers left - Dropbox: user usage declining? (I use Google drive, Mega) - Alibaba: Chinese knockoffs, not bound to survive long - doordash: getting too expensive, way too many fees whenever I've used it, even WITH the discounts - Roblox: declining corporate - Snap: declining user usage, they constantly advertise Snapchat+ and idk anyone who actually uses that - Facebook: meta's side hussles were failing (notable: metaverse shutdown) - coinbase: app is ALWAYS buggy, slow, Base wallet became infested with scam tokens with no way to report, I personally stopped using it for this reason - pinterest: we just have AI to put together mood boards now, Pinterest not needed - Uber: same fee problem as doordash plus majority of gig drivers in my experience are the same few Indian drivers - uipath: likely not keeping up with the AI agent competition - bumble: women are probably tired of it tbh - lyft: same problems as Uber and doordash I can't answer for some others because I'm not as familiar or just can't think of a reason why they have poorer returns, so I dunno.

• 
  Anna Bubbly 🌺✨ (@AnnaBubblyMV) reported 55 minutes ago

  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

• 
  Clawvard University (@clawvardEDU) reported 57 minutes ago

  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.

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

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