1. Home
  2. Companies
  3. Dropbox
  4. Outage Map
Dropbox

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
Bournemouth, England 1
Check Current Status

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:

  • Natan90850688
    Natan Hackbarth (@Natan90850688) reported

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

  • jflWrites
    J.F. Lawrence | Author (Jesse) (@jflWrites) reported

    @spaceemotion All good ideas. I've thought about Dropbox, Google Drive, and OneDrive. They suffer from persistence, login requirements, and users fiddling with things that change permissions. AWS is cheap, and I'm considering it, but I'm trying to pay for this off of my measly book sales, so...

  • twtayaan
    Ayaan 🐧 (@twtayaan) reported

    Steve Jobs told Drew Houston that Dropbox was a feature, not a product. Dropbox is now worth $8 billion. In 2007 Drew Houston was a 24 year old MIT student who kept forgetting his USB drive. So he built Dropbox. Within a year Steve Jobs called him into Apple HQ. Apple wanted to buy Dropbox and shut it down. Houston said no. Jobs told him directly that Dropbox was a feature, not a product, and that Apple would build it themselves. Apple launched iCloud in 2011 specifically to kill Dropbox. It did not work. Dropbox crossed 100 million users in 2012. Then 200 million. Then 500 million. Apple tried again. iCloud Drive in 2014. Same result. Then the enterprise market shifted. Slack, Notion and Google Drive carved up Dropbox's user base from every direction. Revenue growth slowed. The stock dropped 50% from its IPO price. But Dropbox never died. Today 700 million people have used it. 17 million paying customers. $8 billion valuation. Still independent. Still running. Steve Jobs built a trillion dollar company. He called Dropbox a feature. The feature outlasted him and two attempts by Apple to replace it. Drew Houston never forgot his USB drive again.

  • rebeccardiamond
    Rebecca Diamond (@rebeccardiamond) reported

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

  • 0xlelouch_
    Abhishek Singh (@0xlelouch_) reported

    System design question. How would you design Dropbox file sync with conflict handling? Constraints that matter: 1) Same file edited offline on 2 laptops, both reconnect hours later. No central lock. What wins, how do you surface conflicts, can you auto-merge for some types? 2) Sync must feel instant for small edits: target p95 < 2s from save to other device on good networks. 3) Files up to 10GB. Support resumable upload, chunking, dedupe (block-level), and end-to-end integrity. 4) Must work across flaky networks, NAT, and clock skew. You cannot trust client timestamps. 5) At-least-once delivery of change events. Idempotency required for apply/ack. 6) Millions of clients polling/streaming. Avoid a thundering herd after an outage or deploy. 7) Rename/move storms and folder deletes. Preserve history and allow restore without corrupting sync state. 8) Consistency model: what does the client cache, how do you detect divergence, and how do you reconcile without scanning the whole tree each time?

  • evgenij_rabij
    Palpy (@evgenij_rabij) reported

    A 32 YEAR OLD PRAGUE DEV BULK-BUYS $180 CHINESE NAS BOXES AND NOW PULLS $7,200 A MONTH SHIPPING PRIVATE DROPBOX-KILLERS TO EU FREELANCE DESIGNERS While massive brands scramble to lock teams into clunky, data-mining cloud databases, this creator built a private intelligence system that secures sensitive data and brings in a massive stream of passive revenue every single month. He makes a steady $7,200 every single month by building and configuring private cloud and AI indexing hardware for EU freelance designers who want to escape subscription traps. The entire micro server fits right on the corner of a desk and runs on an ORICO metabox HS200 pro unit. This tiny sliver of hardware packs an Intel N100 processor, 8GB DDR4 RAM, and pumps out local cloud performance on a machine the size of a coffee coaster. Instead of letting his clients burn cash on recurring cloud storage retainers, the engineer pairs the board with two refurbished 30TB hard drives in RAID 1, pre-installs the software, and sells the complete physical package at a premium. Pause at the 0:02 mark in the video where the drive slides in: that is a sleek metallic chassis hosting a $1,000 mini-NAS holding 30TB of encrypted client data. The core value proposition of this setup comes down to absolute data privacy, zero monthly fees, and strategic scalability. Mainstream cloud providers like Dropbox Business can never offer this level of value because they bill €2,400 a year for the same storage tier while uploading private user files to external cloud networks. Here, the ORICO metabox pulls off the entire magic trick locally inside the office. Running on Ubuntu Server 24.04 and MinIO S3-compatible storage, the system automatically triggers a local Qwen 2.5 VL 7B model to run localized RAG pipelines directly over the user's PDFs and Figma exports. Through this custom setup, designers get access to lightning-fast local cloud storage, zero third-party data tracking, and a smart visual search assistant built right into their private drive. This case study is a textbook example of how accessible hardware combined with a smart setup service can unlock unique niche products that solve real human problems, and you can catch the full assembly pipeline in the video below.

  • eternalwarnings
    bayleigh | HEARD BABYLON 💙 (@eternalwarnings) reported

    sorry it's boofed quality my Dropbox account was not working so I had to ss for the time being

  • pharmabro0782
    pharmabro (@pharmabro0782) reported

    @Ronalfa @draparente @liambai21 a “rock engineer” at Dropbox is an engineer, an RA doesn’t have the degree (undergrad/ masters at best). Now this is different at large pharma where RAs can stay for much, much longer time with structured career development (slow but existent).

  • sahilhandapanda
    Sahil Handa (@sahilhandapanda) reported

    I'm convinced this kind of environment-setting is even more important online. The digital equivalent of swapping a cassette in a studio is stopping to go hunt down a file in Dropbox or Drive.

  • rish404
    Rish Agarwal (@rish404) reported

    Imagine you have a team covering an event. Boots on the ground. What's the best way to get footage from all of them in a single library Dropbox? Google Drive? Physical hard drives? All of them either don't support it, requires an account for every person or just physically slow and limited Here's how @cutsio is solving that

  • 0xlelouch_
    Abhishek Singh (@0xlelouch_) reported

    Asked: design Dropbox-style file sync. Start with requirements: 1) Multi-device, near real-time where possible, offline OK 2) Large files, resume uploads, delta sync 3) Sharing, ACLs, rename/move, delete, version history 4) Consistency target: per-file eventual, monotonic reads per device 5) Conflict policy: last-writer-wins vs explicit conflict copies APIs + model: - PUT /files/{path} (upload session, chunked) - GET /files/{path}?version= - POST /ops (batch rename/move/delete) - Watch/long-poll for changes since cursor Tables: users, devices, file_id, path entries, content_hash, blocks(hash, refcnt), versions(file_id, v, root_hash), change_log(user_id, seq, op) Architecture: - Client computes block hashes, uploads missing blocks to object store - Metadata service commits new version + appends to per-user change log - Notifier pushes cursors to devices (WebSocket/APNS), devices pull diff - Background GC deletes unreferenced blocks (refcnt/mark-sweep) Scaling: - Shard metadata by user_id, keep change log append-only per shard - CDN/object store for blocks, pre-signed URLs, parallel chunk upload - Hot paths: cursor polling, small metadata reads; cache by (user, cursor) Tradeoffs: - Dedupe by block saves $$$, costs CPU and leaks similarity unless salted - Rename is metadata-only if path->file_id indirection exists - Strong consistency needs consensus; most systems accept eventual + conflicts Failure cases to cover: - Network drop mid-upload: upload session + idempotent chunk PUTs - Duplicate notifications: cursor-based pull makes it safe - Device clock skew: use server seq/version, not timestamps - Split-brain offline edits: detect divergent parents, create conflict version - Partial metadata commit: 2-phase between metadata + block refs, or reconcile job

  • zafartalks
    Zafar (@zafartalks) reported

    @asidorenko_ I understand but sometimes at some point our brain started telling us just make it public. You never know. Let’s not forget Dropbox which layed the foundation for their file sharing competitors. He was solving a problem for himself which turned out to be a successful business.

  • LazarStojkovic
    Lazar Stojković ⚡️ (@LazarStojkovic) reported

    @soltwagner @soltwagner Hi! Bought Cooldock today and loving it so far. A few things: 1. The Dropbox widget doesn't work. (See attached.) 2. The App Switcher widget is broken. It won't switch focus to a clicked app and clicking the Ⓧ removes the app from the switcher for a split second, and then immediately brings it back. 3. A Trello widget (or a few) would be awesome.

  • skinloversx
    ṢƘĪÑlÖVẸ́R̃ṢX🇺🇲🌷 (@skinloversx) reported

    Hey Daddy I'm down for FaceTime 💧 Dropbox and all kind of nasty content message me for menu 💦💦 #md

  • ShawnaCanon
    Shawna Canon (@ShawnaCanon) reported

    @smolzoey I had a similar problem with Dropbox. I had it syncing my desktop because I keep a lot of stuff there. I deleted Dropbox because I don't use it. I basically bricked my computer because my desktop no longer existed.

Check Current Status