Dropbox 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:

• 
  . (@Madame_Lucifur) reported 32 seconds ago

  There are some people who feel entitled to have my Dropbox and honestly I don't give a **** how you feel. If there's no transaction in my bank account which leaves your email address then that's not my problem.

• 
  hiverot (@amusudan) reported 6 minutes ago

  @cowboyshibuya Thanks for the reply! I'm not the most organised, and Ill usually just work on whatever is fun (Or a prerequisite for something that's fun to work on), but I do keep track of ideas, and create todo's and pipelines for things I am sure I want to add or test. For random ideas and todos I use a lot of lists (Dropbox paper, random text files, Notion, Notes app on my phone, Google Docs, etc). And for specific pipelines I use Google Sheets to keep track of what has been done per asset or map or gameplay mechanic (For example my guns spreadsheet has columns for animations, sounds, textures, etc). Big picture design and planning is all on paper in various notebooks and my Calendar app. I don't really track bugs now I just fix whatever pops up when playtesting.

• 
  GRETA (@Greta__ai) reported 6 minutes ago

  We added Asset Manager to Greta. You're building an ecommerce app: product images, demo videos, docs, case studies. Before: Upload images to Cloudinary, videos to S3, docs to Dropbox, links scattered everywhere. One breaks, and you're scrambling through three different services trying to find the original. Now: Upload once in Greta. Reuse assets across all your projects, with everything centralized. No external services. No broken links. No context switching between five different platforms while you're trying to ship. That's smoother. That's what actually building feels like. 50 MB per file. Images auto-compress.

• 
  Yaroslav (@yarslav) reported 7 minutes ago

  this post has been up for just about a day > 10+ leads for long-term packaging work > almost 200 new followers > impressions up across the whole account yet I declined every single lead I've never worked on a per-project basis, always valued long-term relationships but recently I decided to make it even more exclusive I keep the number of channels i work with deliberately VERY small so each one gets my full strategic attention but no matter how selective I am, this type of work has a ceiling I can only work with so many channels at once so I started building something bigger, that is beyond my time and solves a real problem all creators face youtube has become a real industry, with creators running teams of 5, 10, 15+ people but the tools haven't caught up everyone's still spreading their production across notion, slack, drive/dropbox, frame, and more tools just to run their channels because nothing was built specifically for youtube production until now. @feedzyio

• 
  Molly O’Shea (@MollySOShea) reported 7 minutes ago

  BREAKING: Merge Launches ‘Agent Handler’ Control AI Access, Tokenmaxxed $$$ Bills, & Stop Mass Data Leaks "We don't trust agents" "The second you connect it to tools, that's where everything goes wrong." OpenAI. Perplexity. Netflix. Uber. Mistral. Dropbox. JPMorgan.. all quietly run on @merge_api Co-Founders CEO @Shensi Ding & CTO @GilFeig dive into it all We cover: - MASSIVE AI Security scares are just starting - Tokenmaxxing bills - Agent Handler - Gateway routing - Winning enterprise logos - The SaaSpocalypse 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Shensi Ding & Gil Feig, Co-Founders at Merge (01:04) Three products. One big bet (03:20) How Merge made the AI pivot (04:42) The Classic Innovator’s Dilemma (05:58) Building culture around AI (07:10) The leverage nobody’s talking about (08:52) Codex vs Claude Code (09:15) The scale nobody knew about (09:47) SaaS, Finance, and the Biggest AI Labs (10:46) Why AI companies buy differently (12:04) What AI sales actually looks like (13:04) The Fastest sales cycles in the market (14:35) Why is Cybersecurity broken (15:59) Merge's solution to agent security (19:16) Mythos, Wiz, and the GitHub Hack (22:34) 1,000 Bot signups in one hour (23:23) Real reason companies pay ransom to hackers (25:43) The State of AI Infrastructure Costs (26:41) Internal AI Governance is the next big problem (29:28) Most Popular Integrations on Merge (30:54) Big Giants are planning big moves (31:54) What does Salesforce going headless exactly mean (33:41) Agents don’t need a UI anymore (36:59) Can this AI generation actually adapt (38:25) What Merge looks for in talent (41:25) The SaaSpocalypse is real (45:03) Are AI valuations actually insane? (47:11) How Merge landed OpenAI, Perplexity, Netflix & Uber (49:02) The Metrics that actually drive the business (49:58) Biggest misconceptions in tech right now (51:55) The market is finally catching up to Merge

• 
  jss (@jsensarma) reported 8 minutes ago

  @pHequals7 They are usually slow but come around. Their customers are not going anywhere. (Google Drive took years, maybe a decade to show up, after Dropbox)

• 
  Jeff Preshing (@preshing) reported 8 minutes ago

  What's the point of using smarter models if "smarter" means 10% better at finding obscure bugs and having a sassy attitude? Most of the true productivity gains that coding agents have to offer, which are finite, can be obtained using open-weight models for literally 1/100 of the price. The catch is that you actually need to understand the code you are working on. At the same time, I still think there's a viable business serving proprietary models. People are willing to pay for Dropbox even though FTP is free, and it's nice to throw a tough problem at a stronger model occasionally (if intellectual property limitations allow it). Plus, there's a whole frontier productizing this stuff. Unfortunately, Anthropic is currently in the business of spreading tall tales about future improvements, then shaking down enterprise customers. Most of it is based on 2010s LessWrong posts full of category errors, some of which I remember reading back in those days. And their recent hostility toward users in the name of safety is a result of the same ideological recklessness.

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

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  Arthur "lynch mob" van Pelt 🔥 ∞/21M ⚡ (@Arthur_van_Pelt) reported 10 minutes ago

  @laz1m0v @adam3us You want a multifunctional database. Go try BSV or Microsoft SQL Server or Arweave. They have what you want. Bitcoin is money. Not a Pepe Dropbox. Go take your Pepes elsewhere, please. Then we wouldn't even need filters if everyone behaved in the spirit of Cash instead of Pepe.

• 
  Auntieesq (@daniell0930) reported 10 minutes ago

  @MikeJShowalter The issue is the use of the data to train models not retention. Acting as if this is the same a Dropbox is disingenuous. They will not use the data to train for non-safety issues. Non-safety issue is doing some heavy lifting there. Do they have an outline of what this means?

• 
  ray🥤 (@rayontrack) reported 13 minutes ago

  bookmarked, downloaded, screen recorded, emailed, stored in hard drive, uploaded to cloud, archived, backed up, shared via bluetooth, forwarded, copied to usb, saved offline, synced across devices, added to favourites, printed, password protected, compressed into zip, renamed, organised into folders, duplicated, exported, imported, attached to message, sent to recycle bin, restored from backup, converted to pdf, edited, highlighted, annotated, watermarked, uploaded to google drive, uploaded to dropbox, shared through airdrop, linked to notes, tagged, encrypted, burned to cd/dvd, cached, mirrored to another device, uploaded to server, queued for transfer, dragged into archive, pinned, added to reading list, stored on ssd, embedded in document, linked in spreadsheet, previewed, sent to printer queue, recovered from trash, and indexed for search.

• 
  Teja Punna (@punna_teja) reported 14 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.

• 
  Jack (@jacklandas) reported 16 minutes ago

  alibaba banning claude code over backdoor fears is the new "no dropbox on company laptops" every big corp security team is about to have a list. cursor approved, claude code not. windsurf maybe. this fragmentation is going to be a real problem for devs who just want to ship

• 
  Ihtesham Ali (@ihtesham2005) reported 22 minutes ago

  This is how you share a file when you do not trust Google, Dropbox, or the government. A free tool called OnionShare sends it directly through Tor. Nothing needs to sit permanently on someone else's server. Here's what actually happens when you use it. You drag a file into the app. Your own computer turns into the server. Tor wraps it, and you get a long address ending in .onion that you send to whoever needs the file. They open it in Tor Browser and pull the file straight off your machine. You close the app, the address dies. Compare that to how everyone else moves files. You drop it in Drive, Google keeps a copy. You use WeTransfer, that link lives on their infrastructure for a week, logged and tied to your IP. Every one of those services is a promise that a company will behave well, forever, under any amount of legal pressure. OnionShare removes the company from the sentence. Micah Lee built it in 2014. He'd worked with the journalists handling the Snowden documents and watched how many ways a source could get burned just trying to hand over a file. So he built the thing that removes the middle. It does three things. Send files with no size limit and no account. Chat with someone and keep zero record of it. Host an entire website off your laptop that disappears from the internet the moment you shut the lid. The New York Times, The Guardian, and The Intercept all point sources at this. Those are newsrooms betting other people's freedom on a free download. The interface looks like a file picker from 2011. Someone spent years making the hardest privacy problem in computing feel like using WinZip, and that's the actual achievement here. A scared person at 2am is not going to configure a server. They can drag a file into a window. It is completely open source. Most people will never need this. The ones who do don't get a second try if they picked the wrong app. What do you think about this?

• 
  HodlReaper (@HodlReaper) reported 24 minutes ago

  HE PAYS $8 A MONTH FOR NETFLIX, DROPBOX, AND AN IT DEPARTMENT THAT NEVER SLEEPS. One server. One guy. Zero subscriptions. He runs Debian. Free. No license, no monthly fee. Every app lives in its own Docker container. Like apps on a phone. One breaks, the rest keep running. Claude Code runs the whole thing. It writes scripts. It watches the other apps. At 2 AM, when something crashes, it fixes it before he wakes up. He built his own IT department. It doesn't sleep. It doesn't ask for a raise. Plex replaces Netflix. Every DVD and show he owns streams straight to his family. $15 a month, gone. AdGuard kills ads before they hit the Wi-Fi. WebDAV replaces Dropbox, Google Drive, iCloud. Calibre Web holds his entire book library. He mirrored all of Wikipedia. In case the internet ever goes down. He's also building an app on the same server, with its own dashboard tracking rollout errors before they become real problems. Infrastructure scripts watch everything else. Restart what dies. Upgrade what's outdated. He doesn't touch it. Total cost: $8 a month in electricity. Netflix alone costs more than that.