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:

• 
  Shripal Gandhi (@ishripalgandhi) reported 2 minutes ago

  Hey @Dropbox ... Your advanced customer service is horrible! I have benefit chasing them for an important issue since more than 2 days (not counting the weekend) now and I still do not have a resolution. Is it that your reps are allowed to answer only one email per client per day??

• 
  Jody (@Jody28391214234) reported 2 minutes ago

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

• 
  Marcin Moskała (@marcinmoskala) reported 3 minutes ago

  StrictMode is a developer tool which detects things you might be doing by accident and brings them to your attention so you can fix them. StrictMode.ThreadPolicy among others can detect: - slow (blocking) operations on UI thread (detectCustomSlowCalls()) - blocking disc reads/writes on UI thread (detectDiskReads()/detectDiskWrites()) - mismatches between defined resource types and getter calls (detectResourceMismatches()) StrictMode.VmPolicy among others can detect: - leaks of Activity subclasses (detectActivityLeaks()) - when an SQLiteCursor or other SQLite object is finalized without having been closed. (detectLeakedSqlLiteObjects()) - when your app is blocked from launching a background activity or a PendingIntent created by your app cannot be launched (detectBlockedBackgroundActivityLaunch()) - when the calling application exposes a file:// Uri to another app (detectFileUriExposure()) - attempts to invoke a method on a Context that is not suited for such operation (detectIncorrectContextUse()) For both of them, we can specify a penalty: - penaltyLog() - Logs detected violations to the system log. - penaltyDeath() - Crashes the whole process on violation. - penaltyDialog() - Shows an annoying dialog to the developer on detected violations, rate-limited to be only a little annoying. - penaltyDropBox() - Enables detected violations log a stacktrace and timing data to the DropBox on policy violation. - penaltyFlashScreen() - Flashes the screen during a violation. - penaltyListener(…) - Set specific listener on violation.

• 
  Nav Toor (@heynavtoor) reported 10 minutes ago

  Setting 4: Kill background login items. Open System Settings → General → Login Items & Extensions. Look under "Allow in the Background." You'll see 15 to 40 items running constantly. Dropbox helpers. Google updaters. Microsoft Teams. Adobe Creative Cloud. Toggle off anything you don't use every day.

• 
  2Do (@2DoApp) reported 10 minutes ago

  @PhilipLeworthy The Android app is going to unfortunately remain on CalDAV + Dropbox sync for now. I'll be updating it to fix a few issues as well as Tablet related compatibility issues but not major features planned. It remains functional the way it is albeit with a few limitations.

• 
  Jordan (@GoodLordJord) reported 11 minutes ago

  @SmugFecundity @techsaleshackz One million paying customers narrows it down to only a handful of saas companies in the world. Something with that many customers is obviously mature and has a ton of smb business. Probably something like docusign or dropbox which I could totally see a 50 yo doing ok at.

• 
  Auritrack - AI-powered expense tracker (@auritrack) reported 13 minutes ago

  How $9.99 a month for “just one app” became the most profitable business model of the last decade. The math behind subscription creep Adobe had a very huge effect on Photoshop boxed sales in 2013, same software, now $20.99 a month forever. Revenue went from $4.4 billion to over $21 billion in ten years. The product didn’t change, the billing did. Companies Learned Something Brutal: - People fight a $200 charge - People ignore a $9.99 one So they sliced everything into $9.99s. Spotify, Netflix, Hulu, Disney+, Max, Apple TV+, Peacock, Paramount+, Audible, Kindle Unlimited, NYT, WSJ, Substacks, Notion, Dropbox, iCloud, Google One. Add a gym membership and a meal kit and you’re at $400 a month before rent. The Trick: every individual service feels reasonable, the bundle feels invisible, banks don’t surface the total and apps don’t show what else you’re paying but you have to add it up yourself. Most people are off by 60% when asked to guess their monthly subscription spend. Banks reviewed this in 2024, off by $130 a month on average. The fix isn’t dramatic. Pull last month’s statement, highlight every recurring charge, cancel three. Most people save $80+ a month with that one exercise. Auritrack does this automatically, every recurring charge gets a tag, the forgotten ones get flagged. Follow for more money stories.

• 
  yera. (@1stplaceee__) reported 14 minutes ago

  You down for my nasty FaceTime and Dropbox video HMU📨📥💦🍑

• 
  zerohedge (@zerohedge) reported 15 minutes ago

  *DROPBOX CEO DREW HOUSTON TO STEP DOWN: CNBC

• 
  JLemmens (@JLemmens_) reported 27 minutes ago

  @mrsgcomics Onedrive honestly was the best one of the filesyncing services I've used over the time but don't rely on that alone if **** hits the fan. Dropbox (2expensive), Mega (2sluggish), Idrive (obsolete), Gdrive (risky+slow unless you use that app but even then), haven't tried Proton.

• 
  Adam (@aclater) reported 28 minutes ago

  Hey @FedEx @fedexhelp - you've got the wrong address on a dropbox in alexandria, and I keep getting your angry customers and packages. Happy to work together to fix it? I can DM details.

• 
  markusdd (@markusdd5) reported 29 minutes ago

  I have the feeling - when I see who is posting this table over and over on here - that this is just a campaign so institutionals can get in cheaper. How am I remotely interested in the statistics within a 1 year window. (apart from the fact that there are many companies on that list that neither have a unique selling point (Dropbox, Doordash, Pinterest etc..) nor were they economically super great investment casess with a lot of upside. It is of course very likely that SPCX will trade extremely volatile within the first year and that we will also see cash-outs by long term private equity holders once the lock-period expires. So if you have cash set aside - no investment advice - consider just not throwing it in all at once. I personally plan on playing this in 3 tranches. 1/3 today, 1/3 on the first significant draw down and then another 1/3 whenever I feel it is appropriate.

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

• 
  Shubh (@TheSuperEng) reported 32 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."

• 
  𝙳𝚛𝚊𝚌𝚞𝚕𝚊 𝙱𝚛𝚊𝚗𝚍 𝚃𝚊𝚖𝚙𝚘𝚗𝚜 𝙻𝙻𝙲. (@mynameisFACE) reported 33 minutes ago

  You ever login to your old Dropbox and see pics/vids you don’t even remember? Boyyyy, some mistakes were made 😩