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:

• 
  Washington Report (@Washington_Rep) reported 5 minutes ago

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

• 
  Aina (@Aina_Ai2) reported 6 minutes ago

  Then the conversation took a turn. The technician pulled up Activity Monitor and showed him something: 23 apps were running in the background that the customer didn't have open. Adobe Creative Cloud. Spotify. Slack. Microsoft AutoUpdate. Dropbox. Google Drive sync. Three different "helper" apps installed during printer setup years ago. Each one was consuming small amounts of CPU, RAM, and battery cycles 24/7. The technician's words: "Your MacBook isn't slow because it's old. It's slow because it's running 23 jobs nobody hired it to do." System Settings → General → Login Items → look at the lists under both tabs → remove anything that doesn't need to launch automatically. The customer removed 18 of them on the spot.

• 
  Smol (@SmolMacApp) reported 7 minutes ago

  Email attachment limits aren’t small. Your files are big. There’s a difference, and the fix is usually 10 seconds, not a Dropbox link.

• 
  Creative Cyborg (@creativ_cyborg) reported 11 minutes ago

  @thevelvetmonke @fortelabs @tloncorpbot The graph does move with the docs. The graph is the set of links embedded in the documents. I've moved my vaults around from one folder to another, from Dropbox to a regular folder to use Sync, and had no trouble with any of it. That I tell Claude to move the vault and wait a couple of minutes for the move to complete might explain why I find it so easy, but I see no reason to do it in any other way.

• 
  ✨️Ascendant (@ascendant32) reported 13 minutes ago

  yo laptop people, is 2tb of ssd necessary on a laptop these days or is 1tb enough? assuming 32gb ram i work w huge datasets sometimes as for storage needs i use dropbox so it's never been an issue but sometimes loading datasets can be an issue bc not enough ram lol

• 
  BonkDaCarnivore (@BonkDaCarnivore) reported 13 minutes ago

  @QEDCats I don't even remember the login for that Dropbox so I think it's there forever

• 
  Lagoon Labs (@LagoonLabsMv) reported 16 minutes ago

  Dropbox founder Drew Houston is stepping down as CEO, moving to executive chairman. Stock dropped 2.3% on the news. His next move? He's eyeing the AI space - 'credit card alerts for my Cursor token spend.'

• 
  Naughty kayla🤤💦 (@Naughtykayla127) reported 18 minutes ago

  Bored and horny 🥺 who is down for my Dropbox and ft Discount price 🤭#jacksonvillemeets #904freaks #jaxfreaks

• 
  Simon Bates (@RobotDoggy69) reported 19 minutes ago

  I don't know what's going on with Dropbox and my Mac at the moment, but it just won't stay running. I assume it's another apple update that's causing this headache. For two such big firms to give its clients such problems is seriously ****** up.

• 
  lonesome cowgirl lex (@besosprincessa) reported 24 minutes ago

  Who is down to add to their Dropbox link? 👀👀👀 shoot me a message with your budget and want you wanna see!!

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

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

• 
  alt guy (@0xAlternateGuy) reported 28 minutes ago

  @antirez quite suspicious this happens immediately after the Dropbox CEO steps down…

• 
  america is an embarrassment🖕🏻🧊 (@abadlittlevibe) reported 31 minutes ago

  @DaddyAndJaxson @kdriley05 Whelp you've got the Dropbox login...do what you need to do ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

• 
  avrl ☘ (@avrldotdev) reported 31 minutes ago

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

• 
  Awooingenjoyer (@AwooingEnjoyer) reported 31 minutes ago

  Nah, the dropbox is broken, go speak to Cathy.