Skip to content

Outage tracker / Dropbox

Is Dropbox down?

I'm having a problem

Operationalchecked moments ago

We reached Dropbox from all 10 regions we check.

As of Sep 23, 2026, 9:09 AM UTC, Dropbox answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Dropbox (since Aug 8, 2026).

Dropbox reports an active incident: "Paper sharing may not be working as expected" (minor incident, since Sep 3, 2026, 10:32 PM UTC). That is their claim, not our measurement: our probes are currently reaching Dropbox, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 23, 2026, 9:09 AM UTC
US-East380 msOperational
US-West1073 msOperational
Europe420 msOperational
Asia-Pacific1086 msOperational
US-Central960 msOperational
Canada316 msOperational
UK680 msOperational
Southeast Asia1429 msOperational
Australia542 msOperational
South America605 msOperational
their status pagetheir claim, not our reading

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

from Dropbox's own status page, checked Sep 23, 2026, 8:53 AM UTC

Dropbox reports an active incident: Paper sharing may not be working as expected (minor incident, since Sep 3, 2026, 10:32 PM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.

Our probes and Dropbox's own status page agree: both show Dropbox as reachable right now.

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
792msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 600ms2026-08-26 UTC: p95 595ms2026-08-27 UTC: p95 490ms2026-08-28 UTC: p95 572ms2026-08-29 UTC: p95 637ms2026-08-30 UTC: p95 526ms2026-08-31 UTC: p95 600ms2026-09-01 UTC: p95 621ms2026-09-02 UTC: p95 642ms2026-09-03 UTC: p95 833ms2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 773ms2026-09-06 UTC: p95 659ms2026-09-07 UTC: p95 676ms2026-09-08 UTC: p95 703ms2026-09-09 UTC: p95 711ms2026-09-10 UTC: p95 487ms2026-09-11 UTC: p95 588ms2026-09-12 UTC: p95 370ms2026-09-13 UTC: p95 367ms2026-09-14 UTC: p95 408ms2026-09-15 UTC: p95 490ms2026-09-16 UTC: p95 546ms2026-09-17 UTC: p95 613ms2026-09-18 UTC: p95 539ms2026-09-19 UTC: p95 467ms2026-09-20 UTC: p95 367ms2026-09-21 UTC: p95 455ms2026-09-22 UTC: p95 487ms2026-09-23 UTC: p95 792ms
Aug 25Sep 8Sep 23
US-West
1.0sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 484ms2026-08-26 UTC: p95 377ms2026-08-27 UTC: p95 714ms2026-08-28 UTC: p95 943ms2026-08-29 UTC: p95 855ms2026-08-30 UTC: p95 794ms2026-08-31 UTC: p95 947ms2026-09-01 UTC: p95 807ms2026-09-02 UTC: p95 990ms2026-09-03 UTC: p95 989ms2026-09-04 UTC: p95 817ms2026-09-05 UTC: p95 929ms2026-09-06 UTC: p95 954ms2026-09-07 UTC: p95 883ms2026-09-08 UTC: p95 806ms2026-09-09 UTC: p95 666ms2026-09-10 UTC: p95 692ms2026-09-11 UTC: p95 817ms2026-09-12 UTC: p95 621ms2026-09-13 UTC: p95 598ms2026-09-14 UTC: p95 710ms2026-09-15 UTC: p95 823ms2026-09-16 UTC: p95 943ms2026-09-17 UTC: p95 954ms2026-09-18 UTC: p95 951ms2026-09-19 UTC: p95 873ms2026-09-20 UTC: p95 868ms2026-09-21 UTC: p95 885ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.0s
Aug 25Sep 8Sep 23
Europe
571msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 556ms2026-08-26 UTC: p95 477ms2026-08-27 UTC: p95 527ms2026-08-28 UTC: p95 485ms2026-08-29 UTC: p95 533ms2026-08-30 UTC: p95 600ms2026-08-31 UTC: p95 625ms2026-09-01 UTC: p95 576ms2026-09-02 UTC: p95 734ms2026-09-03 UTC: p95 676ms2026-09-04 UTC: p95 812ms2026-09-05 UTC: p95 645ms2026-09-06 UTC: p95 492ms2026-09-07 UTC: p95 497ms2026-09-08 UTC: p95 580ms2026-09-09 UTC: p95 670ms2026-09-10 UTC: p95 455ms2026-09-11 UTC: p95 468ms2026-09-12 UTC: p95 497ms2026-09-13 UTC: p95 474ms2026-09-14 UTC: p95 646ms2026-09-15 UTC: p95 568ms2026-09-16 UTC: p95 549ms2026-09-17 UTC: p95 600ms2026-09-18 UTC: p95 541ms2026-09-19 UTC: p95 519ms2026-09-20 UTC: p95 594ms2026-09-21 UTC: p95 646ms2026-09-22 UTC: p95 545ms2026-09-23 UTC: p95 571ms
Aug 25Sep 8Sep 23
Asia-Pacific
1.3sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.8s2026-08-26 UTC: p95 1.8s2026-08-27 UTC: p95 1.6s2026-08-28 UTC: p95 1.6s2026-08-29 UTC: p95 1.7s2026-08-30 UTC: p95 1.9s2026-08-31 UTC: p95 1.9s2026-09-01 UTC: p95 1.8s2026-09-02 UTC: p95 1.8s2026-09-03 UTC: p95 2.0s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.5s2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 950ms2026-09-20 UTC: p95 920ms2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s
Aug 25Sep 8Sep 23
US-Central
774msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 426ms2026-09-04 UTC: p95 266ms2026-09-05 UTC: p95 271ms2026-09-06 UTC: p95 265ms2026-09-07 UTC: p95 390ms2026-09-08 UTC: p95 428ms2026-09-09 UTC: p95 464ms2026-09-10 UTC: p95 317ms2026-09-11 UTC: p95 343ms2026-09-12 UTC: p95 435ms2026-09-13 UTC: p95 594ms2026-09-14 UTC: p95 705ms2026-09-15 UTC: p95 715ms2026-09-16 UTC: p95 570ms2026-09-17 UTC: p95 613ms2026-09-18 UTC: p95 601ms2026-09-19 UTC: p95 493ms2026-09-20 UTC: p95 522ms2026-09-21 UTC: p95 461ms2026-09-22 UTC: p95 568ms2026-09-23 UTC: p95 774ms
Aug 25Sep 8Sep 23
Canada
458msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 771ms2026-09-04 UTC: p95 265ms2026-09-05 UTC: p95 248ms2026-09-06 UTC: p95 282ms2026-09-07 UTC: p95 265ms2026-09-08 UTC: p95 326ms2026-09-09 UTC: p95 522ms2026-09-10 UTC: p95 347ms2026-09-11 UTC: p95 736ms2026-09-12 UTC: p95 874ms2026-09-13 UTC: p95 965ms2026-09-14 UTC: p95 629ms2026-09-15 UTC: p95 878ms2026-09-16 UTC: p95 460ms2026-09-17 UTC: p95 388ms2026-09-18 UTC: p95 358ms2026-09-19 UTC: p95 367ms2026-09-20 UTC: p95 322ms2026-09-21 UTC: p95 471ms2026-09-22 UTC: p95 484ms2026-09-23 UTC: p95 458ms
Aug 25Sep 8Sep 23
UK
669msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 565ms2026-09-04 UTC: p95 862ms2026-09-05 UTC: p95 551ms2026-09-06 UTC: p95 414ms2026-09-07 UTC: p95 514ms2026-09-08 UTC: p95 441ms2026-09-09 UTC: p95 428ms2026-09-10 UTC: p95 449ms2026-09-11 UTC: p95 407ms2026-09-12 UTC: p95 447ms2026-09-13 UTC: p95 498ms2026-09-14 UTC: p95 414ms2026-09-15 UTC: p95 462ms2026-09-16 UTC: p95 503ms2026-09-17 UTC: p95 704ms2026-09-18 UTC: p95 565ms2026-09-19 UTC: p95 630ms2026-09-20 UTC: p95 491ms2026-09-21 UTC: p95 540ms2026-09-22 UTC: p95 616ms2026-09-23 UTC: p95 669ms
Aug 25Sep 8Sep 23
Southeast Asia
1.8sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 1.5s2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 1.8s
Aug 25Sep 8Sep 23
Australia
1.4sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.7s2026-09-04 UTC: p95 2.2s2026-09-05 UTC: p95 1.6s2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 919ms2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.4s
Aug 25Sep 8Sep 23
South America
1.3sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.5s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.3s2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.3s
Aug 25Sep 8Sep 23

Is it Dropbox, or is it you?

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 380msstatus code: 400checked: Sep 23, 2026, 9:00 AM 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
      Operationallatency: 1073msstatus code: 400checked: Sep 23, 2026, 9:05 AM 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
      Operationallatency: 960msstatus code: 400checked: Sep 23, 2026, 9:09 AM 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
      Operationallatency: 316msstatus code: 400checked: Sep 23, 2026, 9:09 AM 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
    Operationallatency: 605msstatus code: 400checked: Sep 23, 2026, 9:07 AM 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 420msstatus code: 400checked: Sep 23, 2026, 9:07 AM 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
      Operationallatency: 680msstatus code: 400checked: Sep 23, 2026, 8:52 AM 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1086msstatus code: 400checked: Sep 23, 2026, 9:05 AM 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
      Operationallatency: 1429msstatus code: 400checked: Sep 23, 2026, 9:01 AM 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
      Operationallatency: 542msstatus code: 400checked: Sep 23, 2026, 9:08 AM 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 outages

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

measured 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 measurements and Dropbox's own claim at the time, side by side.

Full availability history for Dropbox: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Dropbox, and again when they can reach it again. That is our own measurement from ten regions, not Dropbox's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Dropbox uptime measured by RealUptimeLive, from this page's own readings.
[![Dropbox uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Dropbox's SLA implies, from our measurement

At or above your target

We measured none of downtime for Dropbox over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Dropbox's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.dropboxapi.com/2/users/get_current_account
secondary
https://status.dropbox.com/
RealUptime is not affiliated with Dropbox; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.