GuideGetting started
What does a 99.9% or 99.99% uptime guarantee really mean?
- Reading time
- 6 min
- Last updated
- 1 Nov 2026
A 99.9% uptime guarantee allows about 43.8 minutes of downtime in an average month, or about 8.8 hours a year. A 99.99% guarantee allows about 4.4 minutes a month, or about 52.6 minutes a year. At FasterHost, cloud hosting, VPS and VDS carry 99.99%, and shared, WordPress and reseller hosting carry 99.9%. This guide explains what those figures cover, what they leave out, and what you get if a host misses them.
Uptime percentages in minutes
An uptime percentage is the share of time a service is available. The rest is the downtime it allows. An average month has about 30.44 days, or 43,830 minutes. A year has about 525,960.
- 99% ("two nines"): about 7.3 hours a month, or 3.7 days a year.
- 99.5%: about 3.7 hours a month, or 1.8 days a year.
- 99.9% ("three nines"): about 43.8 minutes a month, or 8.8 hours a year.
- 99.95%: about 21.9 minutes a month, or 4.4 hours a year.
- 99.99% ("four nines"): about 4.4 minutes a month, or 52.6 minutes a year.
Real months differ a little. A 30-day month has 43,200 minutes, so 99.9% allows 43.2 minutes of downtime and 99.99% allows 4.3. A 31-day month allows 44.6 and 4.5.
The period matters as much as the percentage. Our SLA measures uptime per calendar month, so at 99.9% the downtime allowed in any one month is 40 to 45 minutes, depending on its length. The same 99.9% measured over a whole year would allow a single outage of 8.8 hours.
99.9% or 99.99%: which plans carry which
The extra nine cuts the allowed downtime tenfold, from about 43.8 minutes a month to about 4.4. The FasterHost Service Level Agreement sets two levels:
- 99.99% on cloud hosting (from ₹149 a month), VPS (from ₹674) and VDS (from ₹3,333).
- 99.9% on shared hosting (from ₹49 a month), WordPress hosting (from ₹99) and reseller hosting (from ₹499).
Prices are per month, before GST at 18%. Both levels are monthly commitments for network and infrastructure uptime, backed by service credits.
A higher figure needs more redundancy behind it. Our cloud hosting runs on a high-availability cluster with storage replicated three times. A VPS sits on NVMe storage in RAID-10, and if its physical server fails, the VPS is restored from a snapshot.
What an uptime SLA covers, and what it does not
An uptime SLA counts downtime of the host's own infrastructure. Ours defines downtime as sustained unavailability attributable to FasterHost infrastructure, as recorded by our monitoring. It does not cover downtime caused by:
- Scheduled maintenance announced in advance. We announce it at least 48 hours ahead by email and on the status page, schedule it in low-traffic windows, and design it to be zero-downtime wherever possible.
- Your own applications, code or configuration. A broken plugin or a coding error that takes your site down is not host downtime.
- Events outside reasonable control (force majeure).
- Suspension for a breach of the Acceptable Use Policy, or for non-payment.
- Third-party services that FasterHost does not operate. Your domain registrar is one: FasterHost sells hosting only.
So your site can be down while the host's uptime is intact. Slow pages are not downtime either: the SLA measures availability, not speed. The full list is in section 5 of the SLA.
Service credits: what you get if the host misses
If monthly uptime falls below the committed level, you are eligible for a service credit, applied to a future invoice. The credit is a share of the monthly fee for the affected service. The SLA sets it by how far uptime fell:
- 99.9% to 99.99%: 10% credit
- 99.0% to 99.9%: 25% credit
- 95.0% to 99.0%: 50% credit
- Below 95.0%: 100% credit
Two limits apply. The credit in any month cannot exceed 100% of the monthly fee for the affected service. And service credits are the sole and exclusive remedy for a missed SLA. In other words, a credit is sized to your hosting fee, not to what an outage cost your business.
The SLA itself is the binding text. This guide quotes it; it does not replace it.
How to claim a service credit
A credit has to be claimed. In order:
- Note the dates and times your service was down.
- Email billing@fasterhost.in within 30 days of the incident, with your account details and those dates and times.
- Approved credits are applied to your next invoice.
If you run your own uptime monitor, keep its log. It gives you exact times for the claim.
How uptime is measured
Uptime is the percentage of minutes in a calendar month that the service is available. Our monitoring checks availability at one-minute intervals from multiple locations, not from a single point. The public status page shows real-time and historical uptime.
Uptime is not support speed
An uptime figure tells you how much of the month the service is available. It says nothing about how fast someone answers when you need help. That is a separate target.
We aim for a first reply in under 2 minutes on WhatsApp chat and under 30 minutes on tickets, 24/7. Cloud, VPS and VDS plans also have priority and emergency response targets. VDS 16 and above add a 15-minute response SLA and a named account manager.
What to check in any uptime guarantee
- The period. Is uptime measured per month or per year?
- What counts as downtime. Infrastructure only, or your site as a whole?
- The exclusions. Maintenance, notice periods, third parties.
- The credits. How big, by which bands, and capped at what?
- The claim. Who you write to, and the deadline.
- The evidence. How uptime is measured, and whether there is a public status page.
Common questions
→Read next
→Hosting for this
Plans that fit what you just read.
A GST invoice on every plan, and free SSL and free managed migration on the cPanel plans (shared, WordPress, cloud and reseller). On VPS and VDS, migration is free with managed support.
→Get started
Questions about uptime or credits? Ask us.
Free SSL and managed migration on cPanel plans, and engineers on WhatsApp chat, 24/7, with a first reply in under 2 minutes.