Verifying five nines is hard in itself. A monitor checking every 5 minutes can miss a 3-minute outage completely, and that outage alone is more than half the yearly budget. Hyperping checks as often as every 30 seconds, with shorter intervals on the Business plan, from up to 18 regions, and records the start and end of each confirmed outage, so the uptime number reflects every incident rather than the ones a slow check happened to catch.
Each level has its own page with daily, weekly, and monthly figures: three nines, four nines, five nines, and six nines.
At 26 seconds a month, no human is fast enough to be part of the recovery. Everything has to fail over on its own:
The jump from four nines to five usually costs far more than the jump from three to four, for 47 minutes a year of difference.
Probably not. Most SaaS products and websites are well served by 99.9% to 99.95%. Your users' own internet connections, Wi-Fi, and mobile networks fail more often than that, so they can't tell 99.99% from 99.999%. Spend the extra effort on faster recovery and better communication during incidents, which users do notice.
Five nines makes sense where a few minutes of outage has real consequences beyond lost sales: emergency services, payment networks, and the infrastructure other companies build their own SLAs on.
5 minutes 15 seconds per year, or 5.26 minutes. Per 30-day month it's about 26 seconds, and per day less than a second.
Few offer it as an SLA across a whole service. Cloud providers reach it on narrowly defined components, often only for multi-region setups. Read the definition of downtime in the SLA: five nines on a single storage API is very different from five nines on an entire product.
High availability is the design approach (redundancy and automatic failover). Five nines is one target that design can aim for. Many high-availability systems target 99.99%.