More than one number
A percentage alone does not tell the whole story. Customers also care about incident scope, communication speed, and how partial outages are treated.
Service levels
An SLA should explain reliability, communication, and recovery discipline
Searchzilla’s service-level page is designed to help customers understand how availability is treated in practice, how maintenance is communicated, and how incidents are handled when production services are affected.
Status transparencyOperational notices and incident updates matter as much as percentages
Clear precedenceService-level commitments sit alongside platform terms and support policies
Purpose
What an SLA is for
A service level agreement gives customers a structured way to understand reliability commitments for the services they purchase. It helps define the target operating standard for covered services, clarifies the role of planned maintenance, and sets expectations around service credits or remediation where those terms apply.
The best SLA pages are straightforward. They explain what is covered, how availability is evaluated, and how service-level commitments relate to the broader terms of service. That approach is widely used by major infrastructure providers because it reduces confusion during procurement and during real incidents.
Commitment areas
Availability in context
Planned work with notice
Responsible maintenance protects long-term stability. The important issue is whether notices are clear and whether maintenance windows are managed professionally.
Updates that help customers act
Status communication should help customers understand what is affected, what is being checked, and when the next update will arrive.
Operational discipline under pressure
Backups, failover planning, and restoration procedures matter because no platform avoids every incident forever.
Structure
Sample service-level outline
| Area | Customer expectation | Searchzilla approach |
|---|---|---|
| Covered services | Clarity on which products are included | Service-level commitments are tied to the infrastructure class or managed service purchased |
| Planned maintenance | Advance notice and realistic timing | Maintenance is communicated through standard customer channels and status updates where applicable |
| Incident handling | Fast acknowledgement and useful updates | Operational notices focus on scope, next steps, and recovery progress |
| Relationship to terms | No ambiguity on legal order | Service-specific commitments sit alongside the broader platform terms and apply to the covered services they describe |
This format follows the pattern commonly used by infrastructure providers: the SLA explains the service-level framework, references the platform’s broader agreement structure, and focuses on conditions customers can actually use during planning and operations.
Practical use
How customers should use this page
Review before launch
Use the SLA during procurement so internal teams understand coverage expectations before workloads go live.
Compare with your own requirements
Map the service levels to your recovery objectives, support model, and customer commitments.
Pair it with support and status pages
An SLA is most useful when read together with operational support information and public status communication practices.