SECURITY Signal 453 3 feeds carried it
Status pages should report hours affected, not just uptime percentages
↗
A blog post argues that uptime percentages are misleading for non-experts and suggests showing affected time in hours over a period.
For engineers who rely on third-party services, understanding real downtime is crucial, and the current metric hides the impact. The proposal would make status pages more accessible to a broader audience, helping everyone gauge service reliability at a glance.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The article cites Jason Gorman's point that each additional nine of reliability is as hard to achieve as the previous one.
The author notes that status pages are now read by a broader audience, not just infrastructure people.
The suggested alternative is to state hours affected in the last 30 days alongside the percentage.
THE CLUSTER