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:

• 
  Jody (@Jody28391214234) reported 12 seconds ago

  @sarahadams @BenghaziAttacks @BentonDave28405 Same with me Sarah - running into trouble trying just to get the report from DropBox. Help.

• 
  Girish Kotte (@gkotte1) reported 3 minutes ago

  In 2009, Dropbox ignored every rule about SaaS launches. No ads. No cold outreach. No sales team. One stupid idea: a 3-minute demo video for a product that didn't fully exist yet. It generated 75,000 signups overnight. ----- Insight 1 - Simplicity converts better than features Show people one clear outcome. They sign up before the product is ready. Insight 2 - The best growth doesn't look like growth A demo video isn't a campaign. Which is exactly why it worked. Lesson 3 - Ignore conventional launch advice "The opposite of a good idea can also be a good idea." - Rory Sutherland Every advisor said: build first, market second. Dropbox marketed first. Then built. We now see founders obsessing over perfect MVPs before showing anyone anything. The problem: You ship clean code nobody sees. The solution: You ship a clear story first, then the code catches up. I use Postwyse to build that story in public before the product is ready. Perception opens doors. But shipping closes them.

• 
  YC Insights. (@Aiagent_s) reported 6 minutes ago

  March 23, 2018. Dropbox IPOs on NASDAQ. Surges 40%+ day one. Market cap: $12B First YC company ever to go public. Drew still owned 30%. The real lesson: both rejections were right. Both made the company better. Treat each rejection as a specific diagnosis. Then fix that specific thing.

• 
  Shubh (@TheSuperEng) reported 7 minutes ago

  For the past months, tech layoffs have tormented the internet. I studied the biggest layoffs and found the major reasons. Let's look at the layoffs first: 1. Meta: 11,000+ employees / 13% Meta admitted it overestimated post-Covid growth. Revenue slowed, costs were high, and the company moved toward becoming leaner. 2. Google: 12,000 employees / around 6% Google said it had hired for a different economic reality and needed to refocus resources toward its biggest priorities, especially AI. 3. Microsoft: 10,000 employees / less than 5% Microsoft said customers were optimizing digital spending after the pandemic boom, while the company shifted investment toward strategic areas like AI. 4. Amazon: around 30,000 roles / nearly 10% Amazon cut corporate jobs to reduce bureaucracy, improve efficiency, and restructure around AI and faster decision-making. 5. Salesforce: 10% of workforce Salesforce admitted it hired too aggressively during the pandemic and had to resize after customer spending slowed. 6. Spotify: 17% of workforce Spotify said growth had slowed, capital had become expensive, and the company needed to become more efficient after years of heavy investment. 7. Twitter/X: Around 3,700 employees / nearly 50% After Elon Musk’s takeover, Twitter cut roughly half its workforce to slash costs after a massive drop in ad revenue. 8. Snap — 20% of workforce Snap cut jobs after revenue growth slowed sharply. It also shut down non-core projects like games, Originals, and the Pixy drone. 9. Intel: 15,000 roles / around 15% Intel cut jobs because costs were too high, margins were weak, and the company needed a $10B cost-saving plan to stay competitive. 10. Dropbox: 528 employees / 20% Dropbox said demand had softened, the org had too many layers, and it needed to shift focus toward newer growth areas, like AI products. All these layoffs were majorly because of: 1. pandemic overhiring 2. slower revenue growth 3. higher interest rates 4. pressure to improve margins 5. companies cutting management layers 6. money shifting toward AI infrastructure This is majorly conflicting with the idea that AI automation is taking everyone's job. There is absolutely no evidence that AI has caused massive layoffs because of "automation."

• 
  Anna Bubbly 🌺✨ (@AnnaBubblyMV) reported 9 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

• 
  Adrien Matray (@AdrienMatray) reported 11 minutes ago

  The fix is simple: do not use one generic code/ folder for all long-lived branches. Use separate Dropbox folders whose names encode the intended branch: code_main/ code_experimentation_main/ code_experimentation_main_name1Sandbox/ code_experimentation_main_name2Sandbox/

• 
  Rebecca Diamond (@rebeccardiamond) reported 12 minutes ago

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

• 
  ️️️️️️diego 🌐 (@xdxego) reported 14 minutes ago

  ofc when i need to deliver something to a client dropbox is down

• 
  Joo Tat (@heyyyjoo) reported 14 minutes ago

  @kozerafilip @joinsauna @newitemco Here’s my main first impression of Sauna: I don’t see a clear winning use case yet. At least from my perspective, Sauna currently feels like a broad AI layer on top of the apps you already use. It can suggest what to do, help find information, and has a multiplayer/collaboration angle around understanding what other people are doing. But I don’t yet see the specific use case where Sauna is clearly much better than existing alternatives. For an early product, I think it would be useful to have a sharper wedge: a specific group of people, in a specific situation, with a painful problem where existing solutions are poor, and where Sauna is obviously the better answer. Maybe that wedge already exists, but as an outsider looking at the website and demo, it is not immediately clear to me. This feels especially important because Sauna asks users to overcome a meaningful amount of friction and anxiety. To unlock the value, users may need to connect sensitive apps like email, Slack, and Notion. If the multiplayer value is important, they may also need to convince teammates to connect their own sensitive apps. That creates a big trust and coordination hurdle, so the value proposition needs to be extremely clear before people will make that jump. One analogy I think about is Notion. Notion is now a very broad horizontal product: people use it as a CRM, Jira alternative, team wiki, notes app, etc. But early on, I believe it had a much simpler starting point: document and knowledge organization. The product and communication was focused on a better way to store, structure, and share notes and docs compared to alternatives like Google Drive, Dropbox, or scattered documents. People could use it for their own notes and documents first. Then, when they eventually shared a page with colleagues, those colleagues could immediately see the value because the page was easy to navigate, clear, flexible, and beautiful. I wonder what the wedge could be for Sauna. I noticed that the Solutions page seems to heavily feature Sauna in Slack, as an assistant that has access to shared context. Is that something that has been resonating better with users? One possible wedge could be someone who is overwhelmed by Slack because they have too many messages and threads to respond to. They could drop their personal assistant into a channel to help reply on their behalf, using context shared with Sauna, and escalate when it is unable to answer confidently. That might also create an easier mental model around access: the personal assistant in Sauna has access to more private context, while the team-facing assistant in Slack has more limited, scoped access. From there, if colleagues see the assistant working and want their own, that could be a natural path into the multiplayer or “*** main branch” idea. Individual assistants could start to merge shared context and provide better help, suggestions, and coordination over time. I’m not sure if this is the right wedge. The answer may already be visible in the product’s usage patterns: who is sticky, what they are using Sauna for, and where they are getting repeated value. But I think the key question is: what is the specific initial use case where Sauna is not just useful, but dramatically better than the alternatives? Once that is clear, I think the product / website / demo should make that use case extremely obvious to the users who need it. (Btw I'm speaking with Ryan tmr regarding the PM role. Which was what led me to explore Sauna as part of my own research. Thought I might as well share my first impressions here)

• 
  Pageform (@ThePageform) reported 15 minutes ago

  Dropbox is where deals go to die. Investors open your “data room.” It’s a shared folder named “My Data Room” with 34 subfolders and zero logic. They close it in 8 seconds. You never know they were there. No analytics. No structure. No story. That’s the problem we built @ThePageform to fix.

• 
  Abhishek Singh (@0xlelouch_) reported 19 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

• 
  Cane Allesta (@caneallesta) reported 20 minutes ago

  Your password manager has never actually managed anything. It just nagged you. That changes with iOS 27. At WWDC26, Apple announced what might be the clearest example of agentic AI shipping in a consumer product this year: the Passwords app, combined with Apple Intelligence and Safari, can now autonomously navigate to a website, sign in, change your weak or compromised password to a strong one, and save the new credential back to the vault all triggered by a single tap. A Live Activity indicator appears on screen so you can see it working, but you don't have to do anything else. The word "agentic" is doing a lot of work right now in the industry, often covering vague multi-step demos that never quite ship. Apple's move here is different because it's not broad automation it's surgical. The Passwords app already flagged weak, reused, or breached credentials, so the AI layer had a clearly scoped problem to solve: remove the friction between "you know your password is compromised" and "you actually changed it." That gap was enormous. Most people never close it. The competitive context makes this sharper. Google has been shipping Gemini's agentic features on Galaxy S26 and Pixel devices since early 2026, handling cross-app tasks like ordering food on Uber Eats or booking rides in Lyft broad, flashy, and currently limited to a short list of supported apps. Apple's answer is narrower on paper but arguably lands harder because it touches something every single user has: compromised passwords sitting in a list they've been ignoring for months. What Apple is really doing here is establishing trust in an agentic pattern before asking users to hand over bigger tasks. If your phone can autonomously change your Dropbox password without you watching every click, and nothing goes wrong, you're psychologically a lot more comfortable when it eventually offers to autonomously book a flight or fill out a form. It's the same trick that got people comfortable with Face ID start with something small where the upside is obvious and the downside is contained. The feature ships with iOS 27, iPadOS 27, and macOS 27 this autumn, with developer betas available now and public beta expected in July. For the password manager space 1Password, Dashlane, Bitwarden this is a quiet alarm. Apple just made "auto-fix compromised credentials" a native OS feature. Good luck charging $3/month for that. #WWDC26

• 
  How To AI (@HowToAI_) reported 22 minutes ago

  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.

• 
  Natan Hackbarth (@Natan90850688) reported 25 minutes ago

  @peterhowell I used the original pak0.pak. I tested both Dropbox and PixelDrain hosting and tested the exact URL format from the README The app reaches "Fetching PAK" but then fails with "Could not fetch PAK URL" and a 403 error. What hosting method did you use when testing your own pak0.pak?

• 
  GLITCH (@Rukkssss__) reported 27 minutes ago

  𝗕𝗧𝗙𝗦 is BitTorrent's decentralized file storage system, and it fundamentally changes how you store and share data. Think about traditional cloud storage: Google Drive, Dropbox, iCloud. Your files live on servers owned by a single company. That company controls access, sets prices, and can delete your data at any time. Your files are only as safe as that one company's security. And if their server goes down? You lose access. 𝗕𝗧𝗙𝗦 works completely differently. Instead of relying on a single server, your files are split into tiny encrypted pieces and stored across thousands of independent nodes worldwide. No single point of failure. No single company holding your data hostage. This architecture delivers 𝗙𝗼𝘂𝗿 𝗠𝗮𝗷𝗼𝗿 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀. First, security. Because files are fragmented and distributed, an attacker would need to compromise thousands of nodes to reassemble your data practically impossible. Second, censorship-resistance. No government or corporation can shut down BTFS because there's no central target to attack. Third, fault-tolerance. If some nodes go offline, thousands of others still serve your files. Fourth, speed. Peer-to-peer retrieval means you often download from the closest node, not a distant data center. So how does it work for actual users? You upload a file. 𝗕𝗧𝗙𝗦 splits it, encrypts each piece, and distributes those pieces to storage providers around the world users who have volunteered their spare hard drive space. When you need the file back, BTFS locates all the pieces from the fastest available nodes and reassembles them. But here's what makes BTFS sustainable: 𝗥𝗲𝘄𝗮𝗿𝗱𝘀. If you have unused storage space on your computer say, 100 GB sitting empty you can lease that space to the BTFS network. You earn 𝗕𝗧𝗙𝗦 𝗧𝗼𝗸𝗲𝗻𝘀 for every byte you store and serve. Your idle hard drive becomes an income stream. For everyday users, this means cheaper cloud storage. Without a centralized company setting monopolistic prices, storage costs drop to market rates determined by supply and demand. It means safer backups. Your encrypted, fragmented files survive disk failures, server outages, and even natural disasters. It means faster file sharing. The more popular a file is, the more nodes store it, and the faster everyone downloads it the opposite of centralized servers that slow down under load. All of this runs on 𝗕𝗹𝗼𝗰𝗸𝗰𝗵𝗮𝗶𝗻 𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 combined with BitTorrent's massive existing network. BitTorrent already has hundreds of millions of users worldwide. BTFS taps into that peer-to-peer infrastructure, adding incentives and persistence to what was once just a sharing protocol. Upload, store, retrieve. Or share your spare space and earn. No corporate servers. No hidden fees. No single point of failure. That's 𝗕𝗧𝗙𝗦 decentralized storage built for the real world. @justinsuntron @BitTorrent #TRONEcoStar