Dropbox's help.dropbox.com slowed down for 17 minutes on 12 November 2026. Dropbox logged it as elevated latency on the Website component, and the fault sat with their infrastructure, not yours.
Started
22:20 UTC
Duration
Lasted 17m
Source
IsDown
Next time
Dropbox is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Website
What happened?
At 22:20 UTC, Dropbox opened an incident titled "Elevated Latency on help.dropbox.com". Their own text said customers may experience slower-than-usual page loads and search results when accessing Help Center content and self-service support resources. The affected component was listed simply as Website, with no other part of Dropbox's service named. Thirteen minutes later, at 22:33 UTC, Dropbox marked the incident resolved with a single line: "This incident has been resolved." No cause was given at any point in either update. That is the entirety of the public record for this incident, two updates, one opening and one closing, with nothing in between explaining what changed or why it cleared. No user reports were filed during the window, so there is no outside account to weigh against Dropbox's own. Over the past 90 days Dropbox has logged six incidents with a median duration of 1 hour 28 minutes, which makes this 17-minute incident shorter than typical for them. Across all time Dropbox has recorded 246 incidents, averaging 3.2 per month, so a brief latency blip on a help subdomain is a small entry in a long log rather than an unusual event.
Learning
This incident affected help.dropbox.com, a support and documentation surface, not the core file sync or storage service that most products built on Dropbox actually depend on. UptimeRobot's own 30-day figures show one incident resolved with a median duration of 17 minutes, matching what Dropbox itself reported, so there is no conflict between an external check and the vendor's account here. The layer that failed was Dropbox's help content delivery, something that sits outside the reach of any check you run against your own application, because your endpoints never touch help.dropbox.com and would show green the entire time regardless of what was happening there. That is the general shape of this kind of failure: a slowdown in a component you never query directly, visible only if something is watching the provider's own surfaces. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.