Service level agreement (SLA)
Last updated: 18 November 2026
This page sets out the service level of BookMyHost and explains how we measure availability. It adds no new conditions: the commitment and your remedy are the ones in section 2 of our Terms of service, repeated here word for word. If the two ever differ, the Terms of service apply.
1. The commitment
Service level: we target 99.9% monthly network and host availability per service, excluding scheduled maintenance (announced in advance where practicable) and events outside our reasonable control. Your sole remedy for missing the target is a service credit of one day's fees for that service per full hour of qualifying downtime, capped at 50% of that service's monthly fee, claimed within 30 days.
In short:
- Target: 99.9% availability in each calendar month, for each service separately.
- Credit: one day's fees for the affected service for every full hour of qualifying downtime.
- Cap: at most 50% of that service's monthly fee in a month.
- Claim: within 30 days.
- Not counted: scheduled maintenance (announced in advance where practicable) and events outside our reasonable control.
99.9% in a 30-day month allows about 43 minutes of downtime.
2. How we measure availability
We monitor our public services from 4 independent probe locations: Noida, Chennai, Mumbai and Canada. Each probe is a separate server on a separate network, so a fault at one site cannot make the others report an outage.
- Every minute, each probe checks each public service: the website, the customer panel sign-in, the API, the gateway of each region, DNS, the S3 object storage endpoint, the app hosting edge and mail.
- The 3-of-4 rule: a minute counts as down for a service only when at least 3 of the 4 probes see that service fail in that minute. A failure seen by one or two probes is a problem on the path from that probe, not an outage of the service, and is not counted.
- A probe that is itself offline counts as not failing, and our team is alerted to fix it.
- Qualifying downtime is the total of the minutes counted as down under the 3-of-4 rule, less scheduled maintenance and events outside our reasonable control.
For your own server, the probes measure the platform it runs on (the region's network and gateway). Downtime of an individual server caused by a host or network fault on our side is taken from our host and network records for that server.
3. Public status page
The current state of each service, past incidents and scheduled maintenance are published at status.bookmyhost.com. It shows the same 3-of-4 result that we use for service credits.
Monthly uptime for each service, by calendar month in IST, is published in the Monthly uptime table on the same page, calculated with the same 3-of-4 rule. Minutes for which we have no monitoring record are shown separately as "no data" and are never counted as available.
4. How to claim a service credit
- Write to support@bookmyhost.com (or open a support ticket) within 30 days.
- Name the affected service and the date and times of the downtime (IST), and attach your own monitoring results if you have them.
- We check the claim against our monitoring records and confirm the qualifying downtime and the credit.
If your own monitoring saw an outage that ours did not, send us your results: we review them against our records.
Service credits are added to your account wallet and used for future services.
Terms of service → Privacy policy → Refund & cancellation policy → Delete your account →


