Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



If you’re a business owner or are responsible for the maintenance of a company’s web presence, you will know that website downtime can happen at the most inconvenient of times.
Unplanned downtime is never welcome. Your website is the online face of your business, and any period in which it is inaccessible to your clients and customers can damage the reputation of your brand.
However, it is also true that downtime is part and parcel of running a website, particularly one which experiences high volumes of traffic throughout the year. With that in mind, it’s crucial that you prepare as best as possible to deal with unscheduled downtime, and respond in a way which minimises any damage to your brand.
In this article, we will take a closer look at what you can do as a business to deal with unscheduled website downtime.
While in some cases it might not be possible to set up a maintenance page in the event of unplanned downtime, you may be able to move quickly and set one up if a major period of unplanned downtime occurs on your website.
Maintenance pages are typically used as a temporary placeholder when a site has been taken offline for maintenance or updating. This can inform the user that what they are seeing is not an error but a temporary intermission, with normal service to be resumed shortly.
When a period of unplanned downtime occurs, a visitor to your website will typically be served an unhelpful error page. However, by acting quickly and setting up a downtime page, you can communicate with your visitors that you are aware of the issue, and reassure them that you are working to resume normal service as quickly as possible.
This is much more informative and user-friendly than a cold 404 page, which doesn’t provide the end-user with either information or reassurance.
Place yourself in the shoes of a user who visits a website which is offline. Perhaps the first thing you will do is to visit downforeveryoneorjustme.com, but eventually, most users will make their way to social media, either to vent about a negative experience or to contact a company directly.
By being proactive in your response on social media, you can communicate directly with your customer base, both in terms of public posts updating your audience on the issues the website is experiencing, and in one to one support for individuals who reach out to you directly on social.
Again, this type of proactive response to unplanned downtime helps to keep your customers and clients informed, and gives your company the chance to control the narrative until your website is back up and running again.
One of the most effective ways of dealing with unscheduled website downtime is to prepare in advance for the unexpected. By making regular backups of your website you minimise the impact of any period of unscheduled downtime.
A backup is a carbon copy of your website that you can use to restore your website should it be taken offline. By frequently maintaining up to date backups of your website, you will be able to act quickly to restore it in the event of a code error or cyber attack.
You should check with your hosting provider if website backups are included in your current plan. If they aren’t, consider upgrading or moving to a provider who offers this service.
When it comes to dealing with unplanned website downtime, time is very much of the essence. The quicker you can identify the cause of the downtime, the more effective your response will be in dealing with customers and clients who are unable to access your website.
The most important step you can take to ensuring you act quickly when your website goes offline is to actively monitor uptime status using a website uptime monitoring service.
By signing up for an uptime monitoring service, you can take assurance in the knowledge that you will be alerted virtually instantaneously should your website go offline. This knowledge will be invaluable in allowing you to be proactive in dealing with the issue, whether that be in restoring trust on social media, by setting up a downtime page or in quickly restoring a website backup.
Share this
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
Find out everything you need to know in our new uptime monitoring whitepaper 2021