99.999% uptime is our service commitment.
99.999% uptime equates to less than six minutes of downtime per year. If a site experiences more than five minutes of downtime in a calendar year, service is credited one full day for every five minutes our service is offline.
This is not a theoretical target or an internal metric. It is a concrete service commitment with a defined remedy.
What uptime means here
Uptime is not a single server staying healthy. It is the ability for a site to continue serving traffic even when parts of the system fail.
That requires:
- Redundancy
- Isolation
- Continuous monitoring
- Automated recovery
Uptime and sizing
Uptime and capacity are related, but they are not the same thing.
If a site consistently exceeds its available capacity, performance degrades — not availability. The site remains online, but requests may slow down or queue.
That distinction matters.
Sizing is addressed during evaluation and adjusted as your site grows. When more capacity is required, add it in place without downtime or migration.
Failure is expected. Outages are not.
The system assumes failure will happen and is structured so it does not become downtime.
When an issue is detected:
- Unhealthy components are taken out of rotation
- Traffic is routed to healthy environments
- Recovery happens immediately in the background
Sites remain available while problems are addressed.
Real-time automated failover
When an issue is detected, failover happens automatically — no manual intervention, no support ticket, no waiting. The sequence is fast and invisible to visitors.
Geographic distribution protects against localized failures that a single data center cannot survive on its own.
No single point of failure
Each site runs in an isolated environment.
Issues on one site do not affect others. Availability does not depend on shared servers or shared capacity.
WordPress workloads are dynamic
Real WordPress sites include:
- Logged-in users
- Carts and checkout flows
- Frequent content updates
- APIs and integrations
- Traffic patterns that change without notice
Uptime here accounts for that reality. Resources are reserved per site so normal activity does not introduce instability.
Scaling without downtime
As a site grows, capacity scales vertically.
When performance matters, doubling capacity is the only change that actually moves the needle — and it happens in place.
When something goes wrong
If uptime is impacted: