Dropbox: SLA evidence report

2026-08-24 to 2026-09-23 · measured by RealUptime from independent regions · generated Sep 23, 2026, 9:49 AM UTC

Dropbox: SLA evidence report

Measured downtime
0m
Across 0 outages in this window.
Window
2026-08-24 to 2026-09-23
UTC, 30 days.
No outages measured for Dropbox in this window.

What we probed

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

Estimate an SLA credit

Enter what you pay Dropbox for this period and their own stated SLA target. This estimates a credit from the measured downtime above. It is one common way to reason about an SLA credit, not Dropbox's own contract terms, and it is not a legal determination. RealUptime is not counsel.

Based on 0 measured downtime minutes across this report's window.

Methodology

Every outage above is a period our probes measured Dropbox as down from enough of the regions we check it from to count as a real outage, not a single unreliable reading (see how we tell the difference). Measured downtime is the wall-clock time inside the window an outage's regions were failing; regions failing together still count as one outage, not one per region.

Dropbox's claim at the time comes from their own public status feed, polled on our own schedule, and is shown separately from what we measured. We never change our own reading based on what a vendor claims, and their claim never becomes our reading.

This is one external observation from RealUptime's own regions, not Dropbox's own SLA measurement, which is usually defined against their own instrumentation and may cover a different scope than what we probe. The credit estimate above is a starting point for a conversation with Dropbox, not a legal determination, and RealUptime is not counsel.