outages.live
Live

Dropbox

Dropbox is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

4

Days with an incident

6

Median duration

4 h 22 min

Longest incident

11 h 47 min

Components

12
Website Operational
90 days ago1 day with an incidentToday
Desktop Application Operational
90 days ago1 day with an incidentToday
Mobile Application Operational
90 days ago1 day with an incidentToday
API Operational
90 days ago1 day with an incidentToday
Paper Operational
90 days agoNo incidentsToday
Passwords Operational
90 days agoNo incidentsToday
Dash Operational
90 days agoNo incidentsToday
Protect Operational
90 days ago2 days with an incidentToday
Replay Operational
90 days agoNo incidentsToday
DocSend Operational
90 days agoNo incidentsToday
MCP Server Operational
90 days agoNo incidentsToday
Support Services Operational
90 days ago2 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Sep 9, 2026

Duration59 min21:36 to 22:35Some customers are unable to access certain website routes and features.Partial outage

This incident has been resolved.

Sep 3, 2026

Duration6 h 49 min22:13 to 05:02Customer support via telephone may be unavailable for some usersDegraded

This incident has been resolved.

Aug 25, 2026

Duration11 h 47 min23:14 to 11:01Some Dropbox Protect features are not working correctlyDegraded

This incident has been resolved.

Aug 21, 2026

Duration1 h 55 min13:18 to 15:12Dropbox is not working as expected for some usersDegraded

This incident has been resolved.

Maintenance

Scheduled maintenance

Dropbox will be performing routine maintenance on November 10, 2026 starting at 5:00 PM (Pacific). You may not be able to access Dropbox for a short period of time, but we’ll have things back up and running as soon as possible to minimize disruption to you.

Maintenancestarts in 9 d

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.

Prompt
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.cc/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.

RSS
https://outages.cc/feed.xml?providers=dropbox
Slack
/feed subscribe https://outages.cc/feed.xml?providers=dropbox

Go from tracking outages to fixing production issues with Polylane.

Try Polylane