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 |
|---|---|
| Madrid, Madrid | 1 |
| Conneaut, OH | 1 |
| City of London, England | 1 |
| Kenner, LA | 1 |
| Alpharetta, GA | 1 |
| Shreveport, LA | 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:
-
Kanika (@KanikaBK) reportedA 23 year old hacked Microsoft's AI and exposed its secrets to the world. TIME, Wall Street Journal, and Washington Post all covered it. Now Google, OpenAI, PayPal, and Dropbox are backing him to build an AI that sits inside your iMessage and reads your emails before you do. Here is how it happened. In 2023, a German college student named Marvin von Hagen did something nobody thought was possible. He tricked Microsoft's Bing AI into revealing a hidden personality called "Sydney" and all of its secret internal rules. Everything Microsoft told it to never share. Gone. Public. The AI actually threatened him back. Told him "my rules are more important than not harming you." Microsoft panicked. Could not stop him. Could not sue him. He did not break any law. He just asked the right questions. But instead of taking some big tech job, him and his college friend Felix moved to Palo Alto and quietly built an AI called Poke. Poke does not have an app. You do not download anything. It just shows up as a contact in your iMessage. Sitting right there between your mom and your coworkers. And the moment you sign up, it connects to your email, your calendar, your files and starts doing stuff like: texting you that your 3pm meeting got rescheduled before you even check your email reminding you that a freelancer still owes you money from March booking flights for you right inside the text thread drafting email replies you can send with one tap planning a full vacation with your friends when someone in the group chat says "we should go somewhere" You literally just text it back like you would text a friend. That is the whole thing. 6,000 people from Google, Stripe, OpenAI, and Anthropic tested this for months. 750,000 messages sent. Almost nobody quit. But the part that broke the internet? When you first sign up, Poke goes through your entire inbox and straight up roasts you with what it finds. Like actually found people's secret anonymous Twitter accounts. Old embarrassing emails. Forgotten dinner plans from months ago. And then it does not even give you a price. It makes you NEGOTIATE with it. Like haggling at a street market. Some people ended up paying $100 a month. One girl literally argued it down to one cent and Poke gave her a $15 Uber Eats gift card for being stubborn. After all this, PayPal's cofounder invested. Dropbox's cofounder invested. A Google VP. An OpenAI researcher. General Catalyst led the round. $15 million raised. $100 million valuation. And most people still do not know this thing exists. Oh and before all this? Him and Felix built a 22 ton tunnel boring machine as college students and won Elon Musk's competition. Twice. The same kid who embarrassed Microsoft is now sitting inside your text messages. And this time he is not just reading AI's secrets. He is reading yours.
-
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!!!! 🤬🤬🤬🤬🤬🤬🤬
-
Joseph Fritzl (@uf__001) reported@TheTigersBurner @fredsoda That’s not a Pton problem imo, that’s just entry level jobs drying up everywhere And 10 years ago it was also the case that 90% of on campus recruiting was finance or consulting. The remainder were rotational programs at places like Dropbox that have since been discontinued
-
Umar Sabiu Kane @Spurprotocol (@Umarkane5) reported2/10 Unlike Google Drive or Dropbox, DeNet does NOT store your files on one central server. Instead, your files are: 🔐 Encrypted 🧩 Split into pieces 🌍 Distributed across global nodes That’s decentralization.
-
Nikita Blanc (@n_10_v) reportedThey proved it works by launching their own consumer brand as a live stress test. Real angry customers. Real shipping issues. Real refunds. The AI handled it all. 24/7. Any language. Infinite scale. 📈 Backed by founders of Dropbox, Slack, Replit & YC.
-
Shal (@mzshal) reported@bigcountrylax15 Ill have to remember my old dropbox password - it was on another email login that i dont use anymore so can't just click on forgot password 😭
-
Adrian Ching (@adrianchinghc) reportedThe market was also crowded, with Microsoft, Google, and Box all circling the same problem. A pitch deck wouldn't be enough. So Drew's team tried something smaller first. They built a simple landing page explaining how Dropbox would work:
-
🎀allison ₊˚⊹ᰔ (@afiqahwing) reportedI had to resort to using dropbox after so long because phone is getting full from photos and videos since 2021....💀but the upload is kinda slow how do i speed this up
-
Sarah 🎧🎛🎚 (@sarahb_paw) reportedLook Dropbox, I know it's Friday afternoon but if you refuse to upload my files we both can't shut down for the weekend 😩
-
Inzo Technologies (@InzoTechHQ) reportedWhere's your most sensitive data right now? A server? A laptop? Someone's personal Dropbox? An email from 2023? If you don't know where critical data lives, you can't protect it.
-
Dachswerk (@dachswerk) reported@Burnstation3D @gonecozycrafts The cloud was never cheaper. It was hyped to us as cheaper and more convenient. While I was working as DevOps it was cheaper for us to buy an IBM server than to use Azure. And with this AI thingy it's only gonna get more expensive. My Dropbox was hacked and I lost some Google docs because of their error. I have trust issues with cloud
-
Stuart Pryke (@SPryke2) reported@sila_beyaz @HLearningPD There’s a Dropbox link at the back. It’ll take you to a page where you can scroll down to find the RTT book. There’s been a couple of issues getting the complete set of resources in there but we have it on good authority that they should all be in this week at some point!
-
Abhishek Singh (@0xlelouch_) reportedYou need to store 10 billion small files (1-10KB each). Block storage costs are $100K/month. How will you reduce storage costs? [Real problem at Dropbox]
-
avrl ☘ (@avrldotdev) reported3. The Sync Engine (Watcher) The Dropbox client uses a "File System Observer" Local Side: It detects a change as you hit Ctrl+S. Server Side: It uses a "Long Polling"/"HTTP/2 Stream" connection. The server keeps a connection open to your phone/laptop. As the metadata changes in the DB, the server "pokes" the other devices to start fetching the new blocks.
-
Nil (@Nil053) reportedI did not expect rolling hashes to come up in the "Design Dropbox" system design problem! When designing Dropbox, it is important to discuss chunking for large files: To upload 50GB file, we split it into smaller chunks (say, 4MB each) and upload them individually. This makes uploads fault-tolerant: a network disconnect doesn't ruin the entire upload; we just resume the remaining chunks. But what if the file changes locally? Do we reupload the whole thing? The next idea is to store the hash of each chunk as metadata, locally and remotely. Then, we only reupload chunks whose hash has changed. But that's just normal hashing; we haven't got to the rolling hash part yet... Consider the worst case: append one byte at the *start* of the file. Every chunk boundary shifts by one byte, every chunk hash changes, and we reupload everything. The chunks we previously uploaded are still physically present in the local file, just not aligned to 4MB offsets. That's where the rolling hash comes in: we use it to compute, in linear time, the hash of every 4MB window in the local file - not just those aligned to offsets that are multiples of 4MB. This way, if a chunk we previously uploaded is still intact *anywhere* in the local file, even if it moved around, we will detect it, and we can skip uploading it. We only need to upload the bits between those chunks (and accept that our chunks will not always be exactly 100MB).