Dropbox is not working as expected for some users
Dropbox does not work as expected for some users. The Website, Desktop Application, Mobile Application, API, Paper, Passwords, Dash, Protect, Replay, DocSend, MCP Server, and Support Services are affected. Dropbox says it is investigating the issue.
State
Investigating
Started
Ongoing for
18 min
Worst impact
Major outage
Timeline
2 updatesInvestigating
18 min 100%
Updates
Times in UTCAs posted by Dropbox
We are continuing to investigate this issue. The outage is not caused by a cyberattack or by AI acting on its own. We’re sorry for the disruption.
We are currently investigating this issue.
Affected components
12Dropbox in the last 90 days
Full historyIncidents in 90 days
6
Days with an incident
8
Median duration
2 h 40 min
This incident
89% shorter than the median
Other Dropbox incidents
All incidentsDropbox·Sign in with Apple is not working as expected for some users
Sign in with Apple did not work for some Dropbox users on the Website, Desktop Application, and Mobile Application. Dropbox investigated the issue and later reported that it is resolved. The outage lasted 2 hours and 40 minutes.
Dropbox·Elevated Latency on help.dropbox.com
Dropbox reported elevated latency on help.dropbox.com. The Dropbox website was slow to load. Dropbox resolved the incident after 13 minutes.
Dropbox·Some customers are unable to access certain website routes and features.
This incident has been resolved.
Dropbox·Customer support via telephone may be unavailable for some users
This incident has been resolved.
Dropbox·Some Dropbox Protect features are not working correctly
This incident has been resolved.
Follow Dropbox
Your coding agent knows when Dropbox is down, and tells you when a failure is theirs, not yours. You can also get Dropbox incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dropbox" and tell me if Dropbox has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=dropbox/feed subscribe https://outages.live/feed.xml?providers=dropboxFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane