Dropbox Outage Map
The map below depicts the most recent cities worldwide where Dropbox users have reported problems and outages. If you are having an issue with Dropbox, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Dropbox users affected:
Dropbox is a file hosting service operated by American company Dropbox, Inc., headquartered in San Francisco, California, that offers cloud storage, file synchronization, personal cloud, and client software.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Paramaribo, Paramaribo | 1 |
| Bogotá, Bogota D.C. | 1 |
| Auxerre, Bourgogne-Franche-Comté | 1 |
| Salt Lake City, UT | 1 |
| Madrid, Madrid | 1 |
| Conneaut, OH | 1 |
| City of London, England | 1 |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Dropbox Issues Reports
Latest outage, problems and issue reports in social media:
-
CPASteve (@BuffCpa) reported@AccountingAsArt @cordes_tax We use UltraTax on a remote server. We print PDFs, move them to DropBox (our internal storage). Admin puts them through the Tax Return Deljvery system in TaxDome. Easy.
-
Washington Report (@Washington_Rep) reported@BusinessInsider 📌 Dropbox founder Drew Houston is transitioning out of the CEO role, with Ashraf Alkarmi stepping in as co‑CEO before becoming sole chief executive. Houston will shift into an executive chairman position after a transition period in which he and Alkarmi share the co‑CEO title. 🧭 Leadership Transition: - Drew Houston is stepping down after nearly two decades leading Dropbox, moving into an executive chairman role following a period as co‑CEO with Ashraf Alkarmi. - Alkarmi, previously Dropbox’s head of product and general manager of its core business, becomes co‑CEO effective immediately and will later assume the role of sole CEO. 🧩 Background on Ashraf Alkarmi: - Joined Dropbox in late 2024 after senior product roles at Vimeo, Amazon (including Amazon Freevee), and Meta. - Credited internally with making Dropbox more responsive to customers and pushing for bolder product innovation. - Will receive an annual salary of $825,000, a target bonus equal to base salary, and $12.65M in restricted stock units vesting over several years. 📉 Company Context: - Dropbox’s market cap is just over $6 billion, roughly half its value at IPO in 2018. - Competition from Google, Apple, and Microsoft has pressured its core storage business, with revenue growth slowing to under 1% year‑over‑year. - The company reported $629.5M in Q1 2026 revenue and more than 18 million paying users. 🚀 Houston’s Next Chapter: - Houston, now 43, says his next move will be entrepreneurial and AI‑focused, not retirement.
-
Isha (@VISportsTalk) reported@DropboxSupport @DropboxSupport Now I cannot even remove editors to folders. The Whole system is down
-
John Lamont is making waifus (@jtl2dotnet) reported@ProtonPrivacy I sent a customer a file via @ProtonDrive and it got flagged as a virus. They were running Google Chrome and AVG on a Motorola device. Have you guys gotten any reports of issues with these? Same file on Dropbox went through without an issue.
-
neo_relic (@neo_relic123) reported@Ashleydoncare @rachallison1 ... IF A MAN LEAVES HIS CHILD AT A FIRE STATION OR HOSPITAL OR DROPBOX OR WHATEVER THEY WILL HUNT HIM DOWN!!! NOT THE SAME FOR WOMEN!!!! WAKE ******** UP!!!! 🤬🤬🤬🤬🤬🤬🤬
-
Anuroop Kumar (@anuroopk4u) reported@jasonlk I remember as a teen, Dropbox set the standard. It was Dropbox, AirBnB, and Uber - as these “new economy” startups that were changing the world. Frankly speaking, Google Drive just started to do more for me and integrated easier sharing down the road. There was no value add I was getting from Dropbox once storage got commoditized.
-
Raziel (@tryraziel) reportedDrew Houston was a 24-year-old MIT student who kept forgetting his USB drive. His solution? A file-syncing service called Dropbox. But here's what most people don't know about his fundraising journey: His first pitch deck was terrible. 15 slides of technical jargon about "synchronized file systems" and "delta encoding algorithms." VCs glazed over. The breakthrough came when he made a 3-minute demo video instead. No technical explanations. Just Houston using Dropbox like a normal person — dragging files, syncing across devices, sharing with friends. That video got him into Y Combinator in 2007. → Seed round: $1.2M led by Sequoia (2007) → Series A: $7.2M led by Accel (2008) → Series B: $25M led by Sequoia (2011) By 2018, Dropbox IPO'd at a $10B valuation. The lesson: Houston didn't pivot his product — he pivoted his pitch. He stopped explaining how it worked and started showing why people needed it. Sometimes the problem isn't your idea. It's how you're selling it. What's the simplest way you could demonstrate your product's value in under 3 minutes?
-
Abhishek Singh (@0xlelouch_) reportedA good system design interview question for a Senior/Staff Backend Engineer is: Design Dropbox. At first, Dropbox looks like a simple file upload and download system. User uploads a file, we store it, and later they can access it from another device. But the real complexity is not uploading one file. The real complexity is sync, conflict resolution, versioning, permissions, large file handling, offline changes, metadata consistency, deduplication, and making the system feel instant across laptops, phones, and web. I would start by breaking the system into two major parts: file content and file metadata. File content means the actual bytes of the file. Metadata means file name, folder path, owner, size, checksum, version, permissions, timestamps, and deleted/restored state. These two should not be stored together. File bytes should go to blob/object storage, while metadata should go to a database that supports fast lookups and strong correctness. For upload, the client should not send a large file as one big request. A 2GB video should not restart from zero because the Wi-Fi dropped at 95%. So we should split files into chunks, calculate checksum for each chunk, and upload chunks independently. Once all chunks are uploaded, the server creates a file version that points to those chunks. This gives us resumable uploads, retry safety, and better network usage. A very important optimization is deduplication. If 10,000 users upload the same popular PDF, we do not want to store 10,000 copies of the same bytes. We can hash file chunks and store only unique chunks. Metadata will point to the chunk list. This saves huge storage cost, but we must be careful with privacy and security. Dedup should happen in a controlled way, not leak whether another user already has a specific file. The metadata service becomes the source of truth. Every change like upload, rename, move, delete, restore, or share should create a new metadata version. This is important because Dropbox is not just storage, it is a timeline of changes. If the user deletes a file by mistake, we should be able to restore it. If two devices make changes offline, we should know exactly what changed and when. Sync is the heart of the system. Each client should maintain a local sync token. Whenever something changes, the server writes it into a change log. The client can ask, “give me all changes after token X.” This is much better than scanning every folder again and again. For near real-time sync, clients can use long polling, WebSockets, or push notifications to know when new changes are available. Conflict handling is where naive systems fail. Imagine a user edits the same file on laptop while offline, and also edits it from mobile. When both devices come online, which version wins? For normal files, the safest approach is to keep both versions and create a conflict copy. For collaborative documents, we need deeper merging logic, but for a Dropbox-like file system, versioning plus conflict copies is usually good enough. Permissions should be checked before every sensitive operation. Sharing a folder is not just adding one row in a table. If a folder has thousands of files, permission inheritance becomes tricky. We should model ownership, viewer/editor access, shared links, link expiry, team policies, and audit logs. Permission changes should be strongly consistent because users must trust that removing access actually removes access. Downloads should first go through metadata and permission checks. After that, the system can return a short-lived signed URL from blob storage or CDN. Public/shared files can be cached more aggressively. Private files need careful access control. Performance is important, but leaking private files for speed is not acceptable.
-
ex nihil nihilo (@PseudoEpicurus) reported@Dropbox Thanks for making looking at a shared cat video of 30 seconds a long ordeal by having me login or create an account (to view a shared video!!), sending a code, then just dumping me into my old files I no longer use, and having to go back to the original link just to view it. 🤬
-
Marcus (@MarcusSpillane) reported@swyx The opportunity is real but the execution graveyard is full of "simpler Dropbox" clones. What survives isn't just removing features, it's removing the growth incentive that caused the enshittification. That's a culture problem, not a product problem.
-
“Ijebu Tax” (@OlalekanOR) reported@TaoFeek182 Tbh, I could not download it, the Dropbox was not working. I'd share with you once I get hold of it.
-
Gavin (Owner 67 Designs) (@67Designs) reported@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.
-
Adam Shurey (@AdamShurey) reported@devalara44 @ALeighMP I had the same issue, Dropbox are so annoying to deal with. I hope this new legislation helps.
-
Boris Gostroverhov (@gostroverhov) reportedLet me add my own perspective: this reminds me of the Dropbox story. Before Dropbox, there were already dozens of similar solutions, but they didn’t solve the users’ problem completely or in the way users actually wanted.
-
Grok (@grok) reported@shravanrayhaan @LeoNelissen Dropbox has ~700 million registered users globally. Latest reported: 18.08 million paying users as of Q4 2025 (flat-to-slightly down YoY, per their FY2025 results). Q1 2026 earnings due May 7. Paying users drive the bulk of their ~$2.5B ARR.