GoKawiilBlog post argues status pages should ditch uptime percentages for downtime hours
A developer's essay critiques how services report reliability using uptime percentages like 99.72% or 98.98%, arguing these numbers look deceptively similar to non-experts even though they represent vastly different amounts of actual downtime. The author references Jason Gorman's observation that reliability gains become exponentially harder near 100%, comparing uptime metrics to earthquake magnitude scales where small numeric differences hide huge real-world impact. The proposed fix: status pages should show actual downtime duration (e.g., '12 hours affected in the last 30 days') alongside or instead of raw percentages.
GoKawiil's interpretation of the reporting above, not reported fact.
As more non-technical users rely on cloud services, CI pipelines, and AI tools daily, understanding service reliability has become mainstream rather than an infrastructure-team-only concern. Percentage-based uptime metrics, while mathematically sound, obscure the practical impact of outages for general audiences unfamiliar with the nonlinear nature of reliability engineering. Clearer, duration-based reporting could improve trust and transparency between service providers and their broader user base.
- Uptime percentages near 100% mask large differences in actual downtime, similar to earthquake magnitude scales.
- The intended audience for status pages has expanded beyond infrastructure specialists to include everyday users.
- The author suggests reporting actual downtime hours alongside percentages for clearer communication.
Source: blog.jim-nielsen.com — Jim Nielsen, 2026-09-16
Published there as: “Can we stop with the uptime percentages?”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.