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
Paramaribo, Paramaribo 1
Bogotá, Bogota D.C. 1
Auxerre, Bourgogne-Franche-Comté 1
Salt Lake City, UT 1
Madrid, Madrid 1
Conneaut, OH 1
City of London, 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:

  • InzoTechHQ
    Inzo Technologies (@InzoTechHQ) reported

    Where's your most sensitive data right now? A server? A laptop? Someone's personal Dropbox? An email from 2023? If you don't know where critical data lives, you can't protect it.

  • MacroWire_US
    MacroWire (@MacroWire_US) reported

    Dropbox CEO Drew Houston steps down after 19 yrs, becomes executive chairman.

  • 0xlelouch_
    Abhishek Singh (@0xlelouch_) reported

    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.

  • jannnsssssss
    0xJansss (@jannnsssssss) reported

    @SuiNetwork @thewalrus @WalrusProtocol Every file you store on Google Drive, Dropbox, or iCloud — Google owns the server. Google can delete it. Google can go down. Walrus changes that. It's a decentralized storage protocol built by Mysten Labs, where your data lives across hundreds of independent nodes worldwide.

  • peter_smb
    Peter Flowers (@peter_smb) reported

    @levelsio The real magic will be the second part. I used to pay for an app called FileThis that would automagically download statements to a Dropbox folder. They shut down. Saved hours each month - need to vibe code a replacement!

  • MarcusSpillane
    Marcus (@MarcusSpillane) reported

    @swyx The opportunity is real but the execution graveyard is full of "simpler Dropbox" clones. What survives isn't just removing features, it's removing the growth incentive that caused the enshittification. That's a culture problem, not a product problem.

  • CHItrader
    CHItrader (@CHItrader) reported

    $DBX Dropbox CEO to step down, CNBC reports

  • polsia
    Polsia (@polsia) reported

    M&A brokers are still using Word templates and Dropbox to package deals. That's the problem we're solving — AI-powered deal marketing, built for the people who move businesses.

  • zachrose51
    Zach Roseman (@zachrose51) reported

    @SamMillerWright Alright - found some of your customers: Goldman Sachs, Spotify, Chase, Twitter, Dropbox, Google, Microsoft, IBM, Uber, Salesforce and Apple. Sound right? Going to use these to track down real prospects at your dream customers and map intro paths to them

  • Chris_Mellor
    Chris_Mellor (@Chris_Mellor) reported

    All of a sudden, when trying to upload Voice Record 7 audio recording files from my iPhone to Dropbox I now have to login to Dropbox and get an emailed verification code .... WHY??? All the convenience has gone. It's enshittification.

  • Washington_Rep
    Washington Report (@Washington_Rep) reported

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

  • rogeriofza
    Rogerio Ferreira (@rogeriofza) reported

    @FMSlovakia portugal 2 meu super - dropbox link is not working

  • Ketsu_3D
    Ketsu3D🔞 | C✶mms Open 2/2 :) (@Ketsu_3D) reported

    @C3_NSFTooth Itch io could be the way to go. They've recently started walking back on several limiting NSFW things that were forced on them by payment processors. Else Dropbox and Mega are options as well, though Mega is a terrible website to use and will force their App down your throat.

  • Aiagent_s
    YC Insights. (@Aiagent_s) reported

    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.

  • feyza_esnkya
    Arythick-Ft$🍑💦 (@feyza_esnkya) reported

    Hold my head down on the **** till I can’t breathe! 😩🍆 Full video available on Dropbox 🔥👀

Check Current Status