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:

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

  • Augustuskiefer
    PATRICK (@Augustuskiefer) reported

    @DropboxSupport We did not. The issue resolved around 12:45 cst

  • MacroWire_US
    MacroWire (@MacroWire_US) reported

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

  • Lzmrtn66
    Lazaro M. (@Lzmrtn66) reported

    @Dropbox I'm having trouble regaining access to my Dropbox account. I have access to the registered email. I request a password change, you send the password, I log in with the password, then you say you'll send an SMS to my cell phone, but that SMS never arrives.

  • 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!

  • AdrienMatray
    Adrien Matray (@AdrienMatray) reported

    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/

  • AwooingEnjoyer
    Awooingenjoyer (@AwooingEnjoyer) reported

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

  • LagoonLabsMv
    Lagoon Labs (@LagoonLabsMv) reported

    Dropbox is doubling down on virtual-first while everyone else pushes return to office - their people chief says hybrid is the worst of all worlds.

  • CtrlAltDwayne
    Dwayne (@CtrlAltDwayne) reported

    @swyx Brb, creating a YouTube clone. The software part is easy, it's the infrastructure for a lot of these that's the problem. Once you scale a Dropbox, Zoom or YouTube clone you start burning money fast undoubtedly.

  • jmbase
    Jesse Meyers (@jmbase) reported

    @VISportsTalk @Dropbox I was able to get the web interface to load by switching to a VPN. Before that it was showing a 500 error. Desktop app on Mac is still not connecting. Dropbox status page doesn’t show any issues.

  • QuixoticMoose
    QuixoticMoose (@QuixoticMoose) reported

    Bricks & Minifigs LEGO Drama: Unredacted Police Footage Raises Serious Questions About Cop-Business Ties Hey everyone, it's been a wild ride since my last piece on the Bricks and Minifigs mess. What started as a story about a family trying to sell their massive Star Wars LEGO collection has turned into something much uglier. With the unredacted bodycam and dashcam footage from American Fork Police now out there, we are seeing a side of this that looks a lot like police getting way too cozy with the business they were supposed to investigate fairly. The Footage Drop That Blew It Open Just recently, someone got hold of a big batch of unredacted videos from the American Fork PD. It was apparently an accidental public Dropbox link, but once it was out, it spread fast. These are the full versions of the interactions that were shown in heavily edited form before. And man, they paint a pretty concerning picture. In the clips, you see Bricks and Minifigs people like store owner Joshua Johnson and CEO Ammon McNeff talking to officers. They throw out some heavy claims against Reckless Ben. Things like extortion, death threats, collusion with the Mansells, and even making up documents. The police seem to eat it up without much pushback right there on camera. It feels like they are taking the company's word as solid fact. Signs of Too Close for Comfort One part that stands out is when an officer mentions personal connections. He talks about being friends with the Airbnb host where Reckless Ben and his crew were staying before that swatting mess. The officer even sounds like he is bragging about it on bodycam. That kind of casual chat makes you wonder if private relationships played into how aggressively they went after Ben. There is also talk between American Fork officers and other departments, including LAPD. It looks like McNeff and his team were pushing multiple police forces to go after Reckless Ben. The footage shows officers coordinating in ways that feel more like helping a business protect itself than handling a neutral investigation. The arrest of Reckless Ben gets shown in more detail too. What some saw as a traffic stop turns into a long vehicle search over supposed drugs that never seemed to pan out. Critics are calling the whole thing disproportionate, like the police were there to send a message rather than enforce clear laws. The earlier redacted videos hid a lot of this flow, but now we can see it all. The Community Reaction and the Mormon Angle LEGO fans and true crime watchers online have been tearing this apart. Threads on Reddit and YouTube breakdowns are full of people saying it looks like the department acted as private security for Bricks and Minifigs. Some point to the shared LDS Church ties between officers, Johnson, McNeff, and others as a possible reason for the protective vibe. I am not saying it is a full conspiracy, but the optics are not great in a tight knit place like American Fork. Public trust in the police handling here has taken a real hit. The department put out statements defending their actions as responses to stalking complaints at Johnson's home. They say redactions were about protecting victims. But the full unredacted stuff has many questioning if that was the whole truth. Where Does This Leave the Mansells? Remember, at the heart of it all is still that elderly collector and his son who lost track of most of their $200,000 collection during the franchise handover. Bricks and Minifigs maintains they only inherited a tiny bit of inventory and that the original deal was not properly done. Lawsuits are moving forward, but the missing sets and money have not been explained to the Mansells' satisfaction. Reckless Ben's videos brought massive attention to their situation, including a GoFundMe that has helped with legal costs. His style is aggressive, sure, but the new footage makes it look like the pushback from the other side involved more than just legal channels. This scandal shows how fast a hobby dispute can drag in law enforcement and how important real transparency is. If police really did favor one business over a fair process, that is a big problem no matter what side you are on. The LEGO community thrives on trust and good deals. Right now, a lot of us are watching closely to see if the courts sort out the missing bricks and whether anyone holds the police accountable for how they handled this. It is not over yet, but these videos have definitely shifted the conversation. What do you think? Drop your takes below.

  • ascendant32
    ✨️Ascendant (@ascendant32) reported

    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

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

  • monamouroui
    Sara (@monamouroui) reported

    @SlmnMANUTD @WindowsLatest I didn't care about updating to the latest build. I cared about how Windows 11's AI deleted my Dropbox files from not only my desktop, but Dropbox itself! I managed to find them in DropBox's web Deleted Files folder and recover them. On top of this Windows decided to move all of my files that were on my hard drive to One Drive without my permission. And in the process of doing so created multiple subfolders D: OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/OneDrive/My Documents/etc I brought it over the BestBuy to repair the OS because there were other problems, so I cannot tell you how many layers I had to click through to get to my actual documents. I was able to recover the apps that we affected by the update (ScanSnap, Adobe Illustrator, Acrobat, etc) doing a System Restore. But that didn't help with my files.

  • Peace_Grenade81
    The Redeemed Artist (@Peace_Grenade81) reported

    If this app was a phone I would have thrown it across the room by now. Breakups when I use voice to text. It's broken integration with Dropbox so I can't post my memes. And this has been going on for a long time. When will this be fixed?

Check Current Status