<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/can-we-stop-with-the-uptime-percentages--xbneqib9r" -->

---
title: Can We Stop With the Uptime Percentages? | daily.dev
description: An opinion piece arguing that uptime percentages (like 99.72% or 98.98%) are a poor interface for communicating service reliability to a broad audience, since...
canonical: https://daily.dev/posts/can-we-stop-with-the-uptime-percentages--xbneqib9r
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Can We Stop With the Uptime Percentages? | daily.dev
og:description: An opinion piece arguing that uptime percentages (like 99.72% or 98.98%) are a poor interface for communicating service reliability to a broad audience, since...
og:url: https://daily.dev/posts/can-we-stop-with-the-uptime-percentages--xbneqib9r
og:image: https://api.daily.dev/og/posts/xbNeqiB9r.png
og:image:alt: Can We Stop With the Uptime Percentages?
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Can We Stop With the Uptime Percentages?

**[Lobsters](https://daily.dev/sources/lobsters)** · 2 min read · 0 upvotes · 0 comments

## Summary

An opinion piece arguing that uptime percentages (like 99.72% or 98.98%) are a poor interface for communicating service reliability to a broad audience, since the difference near 100% is nonlinear and hard to intuit outside infrastructure circles. The author, prompted by a quote noting each additional nine of reliability is as hard to achieve as the last, suggests status pages should instead report concrete downtime, e.g. '12 hours affected in the last 30 days,' which is easier for non-experts to grasp than a percentage.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.jim-nielsen.com/2026/stop-with-the-uptime-percentage>

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 7 comments across hackernews, lobsters (as of 2026-09-04).

**TL;DR:** Commenters largely agree percentages hide important context, but push back that the real fix is showing the shape of downtime (long outages vs. brief blips) and clarifying what's actually measured, not just converting to hours.

**Sentiment:** 15% positive · 65% mixed · 20% skeptical

**The case for**

- Concrete downtime translations (e.g., minutes affected) are seen as more intuitive than raw percentages.
- One suggested using an odds-ratio or unbounded reliability scale instead of percentages.

**The pushback**

- Two services with the same percentage can have very different downtime patterns (many tiny blips vs. one long outage), which raw hour counts also fail to capture.
- Uptime numbers hide crucial methodology details like measurement intervals, timeout thresholds, and excluded maintenance windows.
- Most general users won't visit status pages anyway and instead just search whether a service is down.
- Brief, frequent downtime (e.g., seconds per minute) may already be an unnoticed norm for many services, undercutting the premise that clearer numbers matter much.

**By community**

- lobsters (mixed): People agree the framing problem is real but argue over whether the fix should be showing downtime distribution/context rather than just converting percentages to hours.

**Hottest debate:** Whether concrete downtime figures actually solve the problem, or whether the real issue is missing context about how uptime is measured and how downtime is distributed over time.

**Open questions**

- What additional context (measurement methodology, maintenance exclusions, downtime distribution) should status pages surface alongside any headline number?
- Do general users even consult status pages, or do they rely on search engines/agents instead?

**Highlights**

> When clicking, I expected a different point, to be honest: one hour of complete downtime per day and rock solid outside, and one day of downtime per month are quite close in percentages, but quite different in behaviour. Not to mention two seconds of downtime every minute and no long downtime for years!
> — [k749gtnc9l3w on lobsters · 5 points, 1 comments](https://lobste.rs/s/uyc8ai/can_we_stop_with_uptime_percentages#c_vriqji)

> The author doesn't suggest throwing out statistics, but adding contextual information. Necessary context, as it turns out: what does "99.99% uptime over the last year" mean? Obviously uptime is measured by a round trip database query through the application from an external service  once every five minutes, so network outages that don't happen on the path between that service  and the datacenter can't even appear.  There's a performance component, of course: if the query doesn't return with the right answer ("OK") within 30 seconds, that's counted as a fail.  Obviously the uptime measurement excludes planned maintenance windows, right? Says so in the SLA. There's a maintenance window every weekend from 1am Saturday through 11pm Sunday; since it usually isn't taken and almost every user is in the same time zone and doesn't work on weekends, nobody notices. And so on: context  turns out to be mportant.
> — [dsr on lobsters · 1 points](https://lobste.rs/s/uyc8ai/can_we_stop_with_uptime_percentages#c_v0kbbu)

> Statistics can be a reasonable way to summarize large amounts of data, so I'm not sure we should just throw them out. For example, 99.99% uptime over the last year does give you an indication of reliability and it is better than 99.9%. You can obviously improve the stats with a breakdown of planned downtime, downtime outside of service hours, discounted for impacted users, etc. > But the audience for status pages isn’t just infra people anymore. It’s increasingly everybody. I don't think the general audience cares about reliability, and I'm not sure if they will even attempt to find the status page in most cases. Instead they will ask their search engine or agent "is x down". If they end up on the status page, they will probably look at the red lines and the "Ongoing Incidents" heading.
> — [manfred on lobsters · 2 points, 1 comments](https://lobste.rs/s/uyc8ai/can_we_stop_with_uptime_percentages#c_huy1hw)

> We could try using the odds formula `p/(100-p)`. So at 98.7% uptime there's a 98.6/(100-98.6) ≈ 1/70 chance of downtime. Alternatively translate it from a scale of 0-100% uptime to a scale of 0-∞ "reliability".
> — [l0b0 on lobsters · 1 points](https://lobste.rs/s/uyc8ai/can_we_stop_with_uptime_percentages#c_xqwpzu)

> An awful lot of IT services in most companies could run with 2 seconds of downtime per minute for years without anyone knowing. For anything which has retries and human-noticeable latencies in the first place, it might already be the normal, accepted case.
> — [dsr on lobsters · 1 points](https://lobste.rs/s/uyc8ai/can_we_stop_with_uptime_percentages#c_z1knzl)

**Source threads**

- [hackernews](https://news.ycombinator.com/item?id=49561542) · 3 points · 0 comments
- [lobsters](https://lobste.rs/s/uyc8ai/can_we_stop_with_uptime_percentages) · 24 points · 7 comments

## Similar posts on daily.dev

- [In defense of GitHub's poor uptime](https://daily.dev/posts/in-defense-of-github-s-poor-uptime-vkonu35xl) · Lobsters · 9 upvotes · 3 comments
- [The Real Cost of Website Downtime \(And How to Estimate Yours\)](https://daily.dev/posts/the-real-cost-of-website-downtime-and-how-to-estimate-yours--03v4ap8f9) · Medium · 0 upvotes · 0 comments
- [What does 99.9% uptime mean for inference?](https://daily.dev/posts/what-does-99-9-uptime-mean-for-inference--srexan4si) · Together AI · 0 upvotes · 0 comments

---

Tags: [#github](https://daily.dev/tags/github), [#observability](https://daily.dev/tags/observability)

[View this post on daily.dev](https://daily.dev/posts/can-we-stop-with-the-uptime-percentages--xbneqib9r)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Can We Stop With the Uptime Percentages?","url":"https://daily.dev/posts/can-we-stop-with-the-uptime-percentages--xbneqib9r","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/can-we-stop-with-the-uptime-percentages--xbneqib9r"},"datePublished":"2026-09-04T07:48:11.260Z","dateModified":"2026-09-04T11:21:05.801Z","description":"An opinion piece arguing that uptime percentages (like 99.72% or 98.98%) are a poor interface for communicating service reliability to a broad audience, since...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/fde5b62249309171f6731e6a9aeec349?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/fde5b62249309171f6731e6a9aeec349?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/can-we-stop-with-the-uptime-percentages--xbneqib9r","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,observability","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"Can We Stop With the Uptime Percentages?"}]}
```

