Web Hosting SLA Explained: Uptime Guarantees, Credits, and Exclusions
hosting SLAuptime guaranteeshosting service creditsweb hosting contractswebsite downtime

Web Hosting SLA Explained: Uptime Guarantees, Credits, and Exclusions

WWebhosting.live Editorial Team
2026-11-10
7 min read

Learn how hosting SLAs define uptime, exclusions, monitoring evidence, support commitments, and service-credit claims.

A web hosting SLA can look reassuring while leaving important questions unanswered. This guide explains how to read uptime commitments, identify exclusions, preserve outage evidence, compare provider policies, and request service credits without assuming that every period of downtime qualifies for compensation.

Overview

A web hosting service level agreement (SLA) is a contractual or policy document that describes the service a provider intends to deliver and the remedy available when defined targets are missed. In hosting, the most visible target is usually an uptime guarantee, but an SLA may also address support response times, network availability, maintenance, hardware replacement, backups, or incident handling.

The headline percentage is only one part of the agreement. You also need to know what the provider measures, which systems are covered, how downtime is calculated, what maintenance is excluded, and how quickly you must submit a claim. A guarantee may apply to network connectivity but not to application errors, DNS propagation, an expired domain, or a website that has exhausted its allocated resources.

Before comparing hosts, save the current SLA, acceptable use policy, terms of service, and support policy for the plan you are considering. Providers can revise policy pages, and a marketing page may summarize a commitment less precisely than the underlying agreement. Treat the SLA as an operational document: it should help you decide what to monitor and what to do during an incident.

What to track

Uptime calculation and scope

First, identify the service being measured. “Server uptime,” “network uptime,” “power uptime,” and “website availability” are not interchangeable. A provider may guarantee access to its infrastructure while excluding failures caused by your software, account configuration, traffic spikes, or a third-party service.

Record the measurement period as well. An SLA may calculate uptime monthly, quarterly, or according to another defined interval. A short outage can have a different contractual effect depending on whether the calculation resets each calendar month or uses a longer reporting period. Note whether the policy uses total minutes in the period, scheduled service windows, or another formula.

For your own records, calculate observed availability consistently:

Observed uptime percentage = (total minutes in the measurement period − qualifying downtime minutes) ÷ total minutes in the measurement period × 100

This calculation is useful for operational review, but it does not determine eligibility by itself. The SLA’s definitions control which minutes count as qualifying downtime.

Exclusions and qualifying events

Exclusions are often more important than the headline guarantee. Look for scheduled maintenance, emergency maintenance, force majeure events, attacks, upstream network failures, suspension for non-payment, account breaches, customer-caused configuration errors, and failures of software or services outside the provider’s control. Some policies also exclude periods when the customer has not followed required support or security procedures.

Do not assume that a planned maintenance notice makes every interruption irrelevant. Check how much notice is required, whether maintenance has a maximum duration, and whether emergency work is treated differently. Keep notices and status updates with your incident record.

Support response commitments

A support response target is not the same as a restoration target. “Initial response” may mean that a ticket was acknowledged, not that the underlying fault was fixed. Track the support channel, ticket number, time opened, time of first meaningful response, escalation time, and restoration time. If the provider offers priority support, confirm which plans qualify and what evidence is needed to use it.

Service credits and claim rules

Hosting service credits are usually a remedy applied to a future invoice rather than a cash refund, but the exact remedy depends on the current agreement. Check whether credits are automatic or must be requested, whether they are the sole remedy, whether there is a minimum outage threshold, and whether credits are capped. The claim window may be short, and the agreement may require monitoring data, support-ticket references, or an incident report.

Provider SLA comparison worksheet

Use this table when comparing providers or reviewing a renewal. It deliberately avoids filling in changing policy details: copy the exact wording and URL from each provider’s current plan-specific documents.

Provider or planCovered serviceUptime commitmentKey exclusionsCredit remedyClaim window and policy URL
Provider ARecord the covered infrastructure or serviceCopy the current SLA wordingList maintenance and customer-caused exclusionsRecord eligibility, cap, and credit formRecord deadline and direct policy link
Provider BRecord the covered infrastructure or serviceCopy the current SLA wordingList maintenance and customer-caused exclusionsRecord eligibility, cap, and credit formRecord deadline and direct policy link
Provider CRecord the covered infrastructure or serviceCopy the current SLA wordingList maintenance and customer-caused exclusionsRecord eligibility, cap, and credit formRecord deadline and direct policy link

For context on measuring availability rather than relying only on contractual language, see our web hosting performance test guide and the ongoing speed and uptime monitoring workflow.

Cadence and checkpoints

Review the SLA before buying, at each renewal, and after any material change to your hosting plan. A monthly or quarterly review is appropriate for business-critical sites, while a small personal site may need only a quarterly check and an incident-based review.

Before purchase or migration

  • Download or archive the current SLA and related terms.
  • Confirm that the guarantee applies to your exact plan, region, and service type.
  • Check whether the policy covers shared hosting, managed WordPress, VPS, cloud, or dedicated infrastructure differently.
  • Confirm the claim deadline, evidence requirements, credit cap, and remedy type.
  • Set up external monitoring before moving production traffic.

During routine operations

Run availability checks from more than one location where practical, and monitor HTTP status, DNS resolution, TLS certificate validity, response time, and application health separately. A successful ping does not prove that a checkout, login, API, or database-backed page works. Keep monitoring timestamps in a system that can export data rather than relying only on browser history.

During an outage

Record the first failed check, the last successful check, affected URLs, locations, error messages, traceroute or DNS observations where relevant, provider status updates, and every support interaction. Avoid repeatedly changing configuration while the cause is unknown; those changes can complicate diagnosis and may fall within customer-caused exclusions. For a step-by-step incident workflow, use our web hosting outage response checklist.

How to interpret changes

A single failed monitor does not automatically establish provider downtime. Compare checks from multiple locations, test both the origin and the public hostname, and determine whether the issue is local, DNS-related, application-specific, or infrastructure-wide. A pattern across independent monitors is stronger evidence than one alert.

Separate availability from performance. A page that eventually loads may count as available under an SLA while still being too slow for customers. Track response time, error rate, and key transaction success independently, then use the SLA to determine which of those measurements, if any, has contractual significance.

When a provider changes its policy, compare the old and new versions line by line. Pay particular attention to a narrower definition of downtime, additional maintenance exclusions, a shorter claim period, a lower credit cap, or a change from automatic remedies to customer-requested credits. Save the effective date and apply the version that governs the relevant incident, subject to the provider’s terms.

Service-credit request template

Subject: SLA service-credit request for [account or service] — [measurement period]

Hello [provider support or billing team],

I am requesting a review under the SLA for [plan/service] for the period [start date and time] to [end date and time]. Our independent monitoring recorded service disruption from approximately [start] to [end], affecting [hostname, service, or region]. The related support ticket is [ticket number].

Attached are timestamped monitoring results, relevant error logs, provider status notices, and a timeline of the incident. Please confirm whether this event qualifies under the current SLA, identify any excluded interval, and apply the eligible service credit according to the agreement. Please also confirm the decision and any required next step in writing.

Regards,
[name and account details]

When to revisit

Revisit this guide and your provider comparison monthly or quarterly, and immediately after an outage, renewal notice, plan migration, infrastructure change, or SLA update. Put a calendar reminder at least once before the claim window expires for each billing period. At that checkpoint, verify the policy URL, uptime wording, exclusions, support commitments, credit rules, and monitoring coverage.

Before renewing, ask whether the SLA still matches the site’s risk. A brochure’s uptime percentage may matter less than clear exclusions, useful support escalation, reliable monitoring evidence, and a remedy you can actually claim. If the policy has become less suitable, compare alternatives using the same worksheet. For broader plan decisions, see shared hosting versus VPS, managed versus unmanaged VPS hosting, and our guide to true renewal pricing.

Your practical next step is to save the current SLA, create an external uptime monitor, and make a one-page incident log with the claim deadline at the top. That preparation turns a vague uptime promise into a measurable process for protecting availability and pursuing an eligible service credit.

Related Topics

#hosting SLA#uptime guarantees#hosting service credits#web hosting contracts#website downtime
W

Webhosting.live Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.