Dropbox Down: How Much Does Dropbox Actually Lose When Its Service Goes Down for an Hour?

The short answer is that no public figure exists showing exactly what an hour of downtime costs Dropbox specifically, since the company has never disclosed that number. But using Dropbox's own reported financial data alongside broader industry research on the cost of IT outages, it's possible to build a reasonably grounded estimate — with an important caveat: for a subscription business like Dropbox, "revenue lost during an outage" and "money that actually disappears" are two very different things.

Start with the raw math

Dropbox reported $2.52 billion in revenue for fiscal 2025, according to the company's own annual report filed with the SEC. Dividing that by the 8,760 hours in a year works out to roughly $287,700 in revenue flowing through the company, on average, during any given hour.

That figure is often the starting point analysts use when estimating downtime costs for any company. But it's a crude proxy, and treating it as Dropbox's actual "loss" during an outage would be misleading for one central reason: Dropbox is a subscription business.

Why subscription revenue doesn't just vanish

Unlike an e-commerce retailer, where a website outage during a sales event can mean transactions that simply never happen, Dropbox's revenue comes almost entirely from recurring monthly and annual subscriptions. A paying Dropbox user doesn't stop being billed because the service went down for an hour — their subscription renews on schedule regardless. So the $287,700-per-hour figure represents revenue that continues flowing to Dropbox even during an outage, not revenue that gets erased by one.

This distinction matters enough that industry analysts specifically flag it. One 2026 industry cost-of-downtime analysis put it directly: "SaaS downtime costs primarily through churn and SLA breach penalties — the [small] direct [monthly recurring revenue] loss from a four-hour outage is rarely the real number once trust effects are modeled." In other words, the immediate, hour-by-hour "loss" for a subscription company is close to zero in accounting terms. The real cost shows up later, and in different forms.

Where the real costs actually come from

For a company like Dropbox, an hour of downtime is more likely to translate into cost through a few specific channels:

Service-level agreement credits. Cloud services typically promise a minimum level of uptime — often 99.9% or higher — to paying business and enterprise customers. When that threshold is breached, affected customers are usually entitled to service credits, which function as a direct, contractually obligated refund of part of their subscription fee. Dropbox has not published its specific SLA credit formula publicly, but this is standard practice across the cloud storage industry.

Customer churn. According to industry research on SaaS outages, a single major disruption can measurably increase monthly customer cancellation rates, with some estimates putting the increase in the range of 2% to 5% following a significant incident. For a company the size of Dropbox, even a small uptick in churn translates into a meaningfully larger revenue impact than the outage hour itself, since it affects future recurring billing rather than the hour in question.

Support and engineering costs. Handling a spike in customer support tickets, plus the engineering time spent diagnosing and fixing the underlying issue, carries a real labor cost, though this tends to be modest relative to the other factors for a company of Dropbox's scale.

Reputational and trust effects. These are the hardest to quantify but often cited as the most consequential long-term cost, particularly for a company whose core value proposition is reliably storing and syncing people's files.

What broader industry benchmarks suggest

Independent research firms have tried to quantify downtime costs across companies more broadly, and their figures vary widely depending on company size and industry. According to ITIC's 2024 Hourly Cost of Downtime Survey, more than 90% of mid-size and large enterprises now report that a single hour of downtime costs their organization more than $300,000, with 41% of enterprises reporting hourly costs between $1 million and $5 million. A separate widely cited benchmark from Gartner, dating to 2014 but still commonly referenced, put the cross-industry average at $5,600 per minute, or roughly $336,000 per hour. More recent research from Splunk and Oxford Economics, published as part of their "Hidden Costs of Downtime" analysis, estimated the 2026 average downtime cost across company sizes at approximately $15,000 per minute, or $900,000 per hour, with aggregate annual downtime losses across the world's 2,000 largest companies reaching roughly $600 billion.

Notably, those figures are generally drawn from companies across all industries, including manufacturing and financial services, sectors where an hour of downtime can halt physical production lines or trigger regulatory reporting obligations, both of which carry costs that simply don't apply to a cloud storage company like Dropbox. A B2B SaaS platform, by contrast, tends to sit toward the lower end of industry cost estimates specifically because its core cost driver is churn and reputational damage rather than immediate, hard transactional losses.

Putting it together for Dropbox specifically

Applying Dropbox's own revenue-per-hour figure of roughly $287,700 as a rough proxy, and layering on the SaaS-specific caveat that direct revenue loss is minimal for subscription businesses, a reasonable estimate is that the immediate, quantifiable cost of a one-hour Dropbox outage — SLA credits plus support overhead — likely falls well below that headline revenue figure, possibly in the tens of thousands of dollars for a single hour, rather than hundreds of thousands. The larger financial risk comes not from the hour itself, but from whether the outage is severe or frequent enough to meaningfully affect customer retention over the following weeks and months.

Dropbox has experienced a handful of confirmed outages in recent years, including a roughly two-hour global disruption in May 2025 that generated a sharp spike in user complaints before the company restored service. The company has not published a post-incident cost estimate for that event or any other specific outage, which is typical practice across the cloud software industry — companies rarely disclose exact financial figures tied to individual downtime incidents, both because the numbers are commercially sensitive and because, as the analysis above suggests, isolating a clean dollar figure for a single hour of downtime is inherently difficult for a subscription-based business.