What Is Website Downtime?
Website downtime is any period when your website is unavailable or not functioning for visitors, whether it shows an error, fails to load, or times out. It is the opposite of uptime, the percentage of time a site is reachable. Downtime can stem from server crashes, hosting outages, expired domains, traffic spikes, failed deployments, DDoS attacks, or expired SSL certificates. For a business, downtime means lost sales, missed leads, damaged trust, and weaker search signals, which is why uptime is a core measure of hosting quality.
- What it is
- Any time a site is unreachable or broken for visitors
- Measured as
- The inverse of uptime, quoted as a percentage such as 99.9%
- 99.9% uptime allows
- About 8.7 hours of downtime per year (industry standard math)
- Common causes
- Server crashes, host outages, expired domains, traffic spikes, or attacks
- Business impact
- Lost sales and leads, weakened trust, and reduced crawlability for SEO (Google Search Central)
What counts as downtime #
Website downtime is any stretch of time when your site does not do its job for visitors, whether it shows an error page, refuses to load, times out, or loads but with a broken checkout or login. It is measured against uptime, the share of time a site is available, usually expressed as a percentage like 99.9 percent. The distinction matters because a site can be technically online yet effectively down: if the homepage loads but the payment step fails, customers still cannot buy, so it is downtime in practical terms. Causes range from server crashes and host outages to expired domains, overwhelming traffic, botched updates, and security attacks. Because every minute offline can cost sales and erode trust, uptime is one of the clearest measures of hosting quality. Businesses that depend on their site for revenue treat downtime as an operational risk to be monitored and minimized, which is a central promise of our /services/managed-hosting page rather than an afterthought.
How uptime percentages translate to real hours #
Hosting providers advertise uptime figures, but the numbers only make sense once you convert them into hours a year. Small differences in the decimal matter far more than they look, because each additional nine cuts allowable downtime roughly tenfold. Knowing the real hours behind a promise helps you judge whether a service level is adequate for your business.
Uptime % Approx. downtime per year
99.0% ~3 days 15 hours
99.9% ~8 hours 46 minutes
99.99% ~52 minutes
99.999% ~5 minutesThe real cost of downtime for a business #
Downtime is not just a technical inconvenience; it is lost money and trust. When an online store is unreachable, every order that would have happened simply does not, and the customer often buys from a competitor instead of waiting. For service businesses, a down site means missed calls, unsubmitted contact forms, and quote requests that never arrive. Beyond the immediate lost transactions, repeated outages erode confidence: visitors who hit an error page wonder whether the business is still operating, and some never return. There is a reputational cost too, especially if the outage coincides with an ad campaign driving paid traffic to a dead page, wasting the ad spend entirely. Search engines also notice, since crawlers that repeatedly find a site unavailable may crawl it less and users bounce, weakening performance signals. Because the damage compounds across sales, reputation, and marketing, protecting uptime with proactive monitoring and maintenance, as bundled on our /services/care-plans page, pays for itself the first time it prevents a costly outage.
Common causes of downtime #
Downtime rarely has a single villain; it comes from several recurring sources. Server crashes and hosting provider outages are the classic causes, whether from hardware failure, a data-center incident, or an oversold shared plan running out of resources. Expired domain registrations silently take sites offline because DNS stops resolving. Traffic spikes, from a viral post to a marketing push, can overwhelm underpowered hosting. Failed deployments and broken updates, such as a bad plugin or a botched code release, can crash a working site in seconds. Security events like DDoS attacks flood a server until it cannot serve legitimate visitors, and a compromised site may be taken down by the host. Expired SSL certificates break secure connections and scare browsers into blocking access. DNS misconfiguration after a move rounds out the list. Many of these are preventable with maintenance and monitoring, and when one does strike, fast recovery is exactly what our /services/website-rescue page is built to deliver under pressure.
Planned versus unplanned downtime #
Not all downtime is an emergency. Planned downtime is scheduled and controlled: you take the site offline deliberately to deploy a major update, migrate hosts, or perform maintenance, ideally during low-traffic hours and behind a proper maintenance page. Done well, it is brief, announced, and returns the correct status code so search engines understand it is temporary. Unplanned downtime is the dangerous kind, striking without warning from a crash, attack, or expired domain, often at the worst possible moment. The goal is to shrink unplanned outages toward zero while keeping planned ones short and transparent. Techniques like staging environments, where changes are tested before going live, and blue-green deployments reduce the risk that an update becomes an unplanned outage. Careful change management is part of professional maintenance, and testing updates safely before they touch the live site is a core habit our /services/wordpress-development page builds into ongoing work, so that a routine plugin update never turns into an accidental, revenue-losing outage discovered only when customers complain.
How to detect downtime quickly #
You cannot fix what you do not know about, and the worst way to learn your site is down is from an angry customer. Uptime monitoring solves this by checking your site at regular intervals from multiple locations and alerting you the moment it stops responding, so you often know before visitors do. Good monitoring checks not just the homepage but critical paths like checkout or login, and it distinguishes a local glitch from a true outage by testing from outside your own network. For an on-demand check, our /tools/website-down-checker reports whether a site is reachable from an independent vantage point, which is invaluable when you are unsure whether the problem is your connection or the server. Alerting speed matters because the cost of downtime accumulates every minute, so a system that pages you within a minute of an outage is far more useful than one that emails an hour later. Fast detection turns a potential multi-hour outage into a short, contained incident.
Reducing and preventing downtime #
Preventing downtime is mostly about removing single points of failure and staying ahead of problems. Start with reliable, appropriately sized hosting so normal traffic never exhausts resources, and add redundancy or a CDN so one component failing does not take the whole site down. Keep domains and SSL certificates on auto-renewal so they cannot silently expire. Test every update in a staging environment before it reaches production, and keep tested backups so you can restore fast if something breaks. Harden the site against attacks with a firewall and up-to-date software, since a security incident is a common route to an outage, work covered on our /services/website-security page. Finally, monitor continuously so you catch trouble early. None of these steps is exotic; together they turn uptime from a hope into a managed outcome. Bundling monitoring, updates, backups, and renewals into a maintained plan, as our /services/managed-hosting page does, is how serious businesses keep their sites reliably online.
Backups and fast recovery #
Downtime is not only about prevention; how fast you recover determines the real cost. Two sites can suffer the same crash, but the one with tested backups and a rehearsed recovery plan is back in minutes while the other spends a day rebuilding. Keep regular, automated backups of both files and database, store copies off the server so a host failure cannot take them down too, and, crucially, test that you can actually restore from them, since an untested backup is only a hope. Document the recovery steps so anyone on your team can follow them under pressure. For a botched update, the ability to roll back instantly to the last good state turns a potential outage into a brief hiccup. This recovery discipline sits alongside monitoring and prevention in a maintained setup, which is why backups and restore testing are built into the ongoing care on our /services/care-plans page rather than left as an emergency scramble improvised in the moment something finally breaks.
Setting a realistic uptime goal #
Chasing 100 percent uptime is unrealistic, because even the largest providers experience occasional incidents; the aim is to make downtime rare, short, and quickly recovered. For most small businesses, an effective target is 99.9 percent, which allows under nine hours of downtime a year, paired with monitoring that shrinks each incident to minutes. Sites where every minute offline carries heavy cost, such as busy stores, justify investing toward 99.99 percent through redundancy and stronger infrastructure. The right goal balances the cost of higher reliability against the revenue and reputation at stake, so a hobby blog and a high-volume shop should not aim for the same number. Review your host's actual track record rather than only its advertised figure, and hold it accountable with independent monitoring. If you are unsure how reliable your current setup really is or where its weak points lie, a /free-website-audit will surface the hosting, domain, and security risks most likely to cause your next outage before it happens.
FAQ
What is website downtime in simple terms?
It is any period when your website is unavailable or not working for visitors, whether it shows an error, will not load, or times out. It is the opposite of uptime, the percentage of time a site is reachable. Even a site that loads but has a broken checkout counts as downtime in practical, revenue terms.
How much downtime is acceptable?
For most small businesses, aiming for 99.9 percent uptime, which allows under nine hours offline per year, is a reasonable goal when paired with monitoring that keeps each incident short. Busy online stores where every minute costs money may invest toward 99.99 percent, about 52 minutes a year, through redundancy and stronger hosting.
What causes a website to go down?
Common causes include server crashes, hosting provider outages, expired domain registrations, traffic spikes that overwhelm the server, failed updates or deployments, DDoS attacks, and expired SSL certificates. Many are preventable with proper hosting, monitoring, auto-renewals, and testing updates in staging before they reach the live site.
How do I know if my website is down?
Use uptime monitoring that checks your site from multiple locations and alerts you the moment it stops responding, often before customers notice. For an on-demand check, an external tool confirms whether the site is reachable from outside your own network, which distinguishes a true outage from a local internet or browser problem on your device.
Does downtime hurt my Google ranking?
Brief, occasional downtime is unlikely to hurt rankings, but frequent or prolonged outages can. If search crawlers repeatedly find the site unavailable, they may crawl it less, and users who hit errors bounce, weakening performance signals. Reliable hosting and fast recovery protect both your visitors and your search visibility over time.
How can I prevent website downtime?
Use reliable, right-sized hosting, keep domains and SSL certificates on auto-renewal, test updates in staging before going live, maintain tested backups, harden the site against attacks, and add continuous uptime monitoring. Bundling these into a maintained hosting plan turns uptime from a hope into a managed, dependable outcome rather than a recurring gamble.
How Local Web Advisor checks this for you
Is your own website getting hosting & domains right?
Our free AI audit scans your site and tells you — in plain English — exactly what to fix for hosting & domains and seven other areas, with the business impact and the fix for each. No login needed to start.
Run my free website audit →Was this helpful?