outages.live
Live
DropboxMaintenance · 2026-11-11 01:00 UTC

Scheduled maintenance

MaintenanceOfficial update

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.

The latest update from Dropbox.

State

Scheduled

Starts

in 9 d

2026-11-11 01:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Dropbox

Scheduled2026-11-01 17:18 UTC

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.

Affected components

9
WebsiteDesktop ApplicationMobile ApplicationAPIPaperPasswordsDashProtect

Dropbox in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

6

Median duration

4 h 22 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

11 h 47 min
median 4 h 22 min
90 days agoToday

Other Dropbox incidents

All incidents

Dropbox·Some customers are unable to access certain website routes and features.

This incident has been resolved.

Resolvedresolved 53 d ago

Dropbox·Customer support via telephone may be unavailable for some users

This incident has been resolved.

Resolvedresolved 59 d ago

Dropbox·Some Dropbox Protect features are not working correctly

This incident has been resolved.

Resolvedresolved 67 d ago

Dropbox·Dropbox is not working as expected for some users

This incident has been resolved.

Resolvedresolved 72 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane