Downtime
PerformanceDowntime is the period when a website, server, or hosting service is unavailable or cannot respond correctly to user requests. It can be planned (maintenance) or unplanned (hardware failure, software bugs, network issues, or attacks). Downtime affects visitors, search visibility, and revenue, and is often summarized in uptime percentages and monitored through external checks and server logs.
How It Works
Downtime occurs when the components required to serve a site fail or become unreachable. This can happen at multiple layers: the application (errors in WordPress, PHP, or a database), the web server (Apache or Nginx misconfiguration), the operating system, the storage subsystem, or the network path between users and the data center. Even if the server is running, a broken DNS record, expired SSL certificate, or overloaded resource limits can make the site effectively "down" to visitors.
Hosting teams typically detect downtime through monitoring that checks HTTP responses, latency, and service health (web, database, mail). When an outage is detected, recovery may involve restarting services, failing over to redundant nodes, restoring from backups, rolling back a deployment, or mitigating an attack such as a DDoS. Planned downtime is usually scheduled for updates, kernel patches, migrations, or hardware maintenance, ideally during low-traffic windows and with clear status communication.
Why It Matters for Web Hosting
Downtime is a practical measure of hosting reliability and operational maturity. When comparing plans, look beyond marketing uptime claims and evaluate what reduces downtime: redundancy (power, network, storage), proactive monitoring, incident response, DDoS protection, backup and restore options, and whether maintenance requires reboots. Also consider how downtime is reported (status pages, alerts) and what service-level commitments exist, since even short outages can impact conversions, email deliverability, and SEO crawling.
Common Use Cases
- Evaluating hosting reliability using uptime monitoring and incident history
- Planning maintenance windows for updates, migrations, or major configuration changes
- Troubleshooting availability issues caused by resource limits, misconfigurations, or database failures
- Assessing the need for high availability features such as load balancing, failover, or multi-region DNS
- Setting alerting and escalation workflows for critical sites and ecommerce stores
Downtime vs Degraded Performance
Downtime means the site is unreachable or returns failures (timeouts, 5xx errors, broken TLS), while degraded performance means the site still responds but is slow or intermittently failing under load. Both harm user experience, but they point to different fixes: downtime often requires restoring service availability (network, DNS, service restarts), whereas degraded performance usually involves capacity planning, caching, query optimization, or upgrading CPU/RAM and I/O resources.