Skip to content

Outage tracker / Dropbox

Is Dropbox down?

I'm having a problem

Vendor reports no incidentWhat Dropbox reports

Dropbox reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:31 UTC.

Dropbox's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Dropbox pass from all 10 regions we check.

As of Nov 5, 2026, 3:42 PM UTC, RealUptime's checks of Dropbox passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when Dropbox reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Dropbox's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 5, 2026, 3:42 PM UTC
US-East222 msChecks passing
US-West2186 msChecks passing
Europe1105 msChecks passing
Asia-Pacific2958 msChecks passing
US-Central914 msChecks passing
Canada1573 msChecks passing
UK333 msChecks passing
Southeast Asia1514 msChecks passing
Australia717 msChecks passing
South America2801 msChecks passing
their status pagetheir claim, not our reading

Dropbox reports: All systems operational (“All Systems Operational”)

from Dropbox's own status page, checked Nov 5, 2026, 3:13 PM UTC

Dropbox's own component breakdown, as they publish it

  • WebsiteOperational
  • Desktop ApplicationOperational
  • Mobile ApplicationOperational
  • APIOperational
  • PaperOperational
  • PasswordsOperational
  • DashOperational
  • ProtectOperational
  • ReplayOperational
  • DocSendOperational
  • MCP ServerOperational
  • Support ServicesOperational

These are Dropbox's components, named and scored by Dropbox. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Dropbox's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Dropbox response time, by region

US-East
1.5sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 794ms2026-10-08 UTC: p95 832ms2026-10-09 UTC: p95 689ms2026-10-10 UTC: p95 591ms2026-10-11 UTC: p95 559ms2026-10-12 UTC: p95 626ms2026-10-13 UTC: p95 657ms2026-10-14 UTC: p95 579ms2026-10-15 UTC: p95 721ms2026-10-16 UTC: p95 702ms2026-10-17 UTC: p95 884ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
US-West
2.3sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 970ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 972ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Europe
2.1sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 633ms2026-10-08 UTC: p95 722ms2026-10-09 UTC: p95 755ms2026-10-10 UTC: p95 659ms2026-10-11 UTC: p95 665ms2026-10-12 UTC: p95 692ms2026-10-13 UTC: p95 466ms2026-10-14 UTC: p95 556ms2026-10-15 UTC: p95 552ms2026-10-16 UTC: p95 291ms2026-10-17 UTC: p95 862ms2026-10-18 UTC: p95 980ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 874ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Asia-Pacific
3.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 3.0s2026-10-23 UTC: p95 3.5s2026-10-24 UTC: p95 3.6s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 3.6s2026-10-27 UTC: p95 3.1s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 3.9s2026-11-04 UTC: p95 3.7s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
US-Central
1.1sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 877ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Canada
1.6sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 456ms2026-10-08 UTC: p95 490ms2026-10-09 UTC: p95 500ms2026-10-10 UTC: p95 504ms2026-10-11 UTC: p95 505ms2026-10-12 UTC: p95 628ms2026-10-13 UTC: p95 808ms2026-10-14 UTC: p95 696ms2026-10-15 UTC: p95 570ms2026-10-16 UTC: p95 684ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
UK
974msp95 · latest
2.5s1.3s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 507ms2026-10-08 UTC: p95 575ms2026-10-09 UTC: p95 602ms2026-10-10 UTC: p95 510ms2026-10-11 UTC: p95 480ms2026-10-12 UTC: p95 512ms2026-10-13 UTC: p95 346ms2026-10-14 UTC: p95 294ms2026-10-15 UTC: p95 295ms2026-10-16 UTC: p95 352ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 985ms2026-10-20 UTC: p95 964ms2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 974ms
Oct 7Oct 21Nov 5
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 3.6s2026-10-23 UTC: p95 3.1s2026-10-24 UTC: p95 3.0s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 3.2s2026-10-27 UTC: p95 3.1s2026-10-28 UTC: p95 3.3s2026-10-29 UTC: p95 3.0s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 2.7s2026-11-01 UTC: p95 3.1s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Australia
2.3sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 738ms2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.7s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 3.0s2026-10-26 UTC: p95 3.1s2026-10-27 UTC: p95 3.0s2026-10-28 UTC: p95 3.3s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.3s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
South America
2.7sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 3.0s2026-10-23 UTC: p95 7.4s2026-10-24 UTC: p95 3.7s2026-10-25 UTC: p95 3.8s2026-10-26 UTC: p95 3.9s2026-10-27 UTC: p95 3.5s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 3.1s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 3.2s2026-11-03 UTC: p95 3.6s2026-11-04 UTC: p95 3.9s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
Why some readings show as awaiting data. 1 of 20 readings for Dropbox came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Dropbox's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Dropbox

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Dropbox. It cannot diagnose Dropbox's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 222msstatus code: 400checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Dropbox normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 2186msstatus code: 400checked: Nov 5, 2026, 3:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Dropbox normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 914msstatus code: 400checked: Nov 5, 2026, 3:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Dropbox normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1573msstatus code: 400checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Dropbox normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2801msstatus code: 400checked: Nov 5, 2026, 3:34 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Dropbox normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1105msstatus code: 400checked: Nov 5, 2026, 3:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Dropbox normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 333msstatus code: 400checked: Nov 5, 2026, 3:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Dropbox normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2958msstatus code: 400checked: Nov 5, 2026, 3:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Dropbox normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1514msstatus code: 400checked: Nov 5, 2026, 3:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Dropbox normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 717msstatus code: 400checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Dropbox normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Dropbox, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Dropbox yet, which is not evidence that nothing is wrong.

Recent probe events

Some customers are unable to access certain website routes and features., 59mdeclared on their status page2026-09-09
Paper sharing may not be working as expecteddeclared on their status page2026-09-03
Customer support via telephone may be unavailable for some users, 6h 49mdeclared on their status page2026-09-03
Some Dropbox Protect features are not working correctly, 11h 47mdeclared on their status page2026-08-25
Dropbox is not working as expected for some users, 1h 55mdeclared on their status page2026-08-21
Dropbox is not working as expected for some users, 25mdeclared on their status page2026-07-23
Shared content downloads are degraded, 93h 11mdeclared on their status page2026-06-08
Opening a video or audio file might not be working for users, 2h 26mdeclared on their status page2026-05-27

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Dropbox since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Dropbox covering any window you pick, with our check readings and Dropbox's own claim at the time, side by side.

Full check history for Dropbox: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Dropbox uptime by RealUptime's checksLive, from this page's own readings.
[![Dropbox uptime by RealUptime's checks](https://realuptime.io/outages/dropbox/badge.svg?days=30)](https://realuptime.io/outages/dropbox)
<a href="https://realuptime.io/outages/dropbox"><img src="https://realuptime.io/outages/dropbox/badge.svg?days=30" alt="Dropbox uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Dropbox down?", https://realuptime.io/outages/dropbox. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://api.dropboxapi.com/2/users/get_current_account
secondary
https://status.dropbox.com/

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: api.dropboxapi.com

RealUptime is not affiliated with Dropbox; the name identifies what we checked, and nothing here speaks for Dropbox's own team. We send a single web request to Dropbox from 10 regions on our own schedule and time the response. We do not see inside Dropbox's systems, do not use an account or real transaction, and are not the same signal Dropbox's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Dropbox is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.