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
Unfortunately, website outages are common and can occur at very inopportune times. In the US, the National Hurricane Data Center’s website went down this October due to DNS errors just as Hurricane Matthew approached the coast of Florida. Amazon, BT, BBC, Google and Microsoft all had website crashes in recent years, and the recent DDoS attack on Dyn caused website outages at many large international companies, including PayPal and Twitter. The question is not “if” your website will go down, the question is “when.” Here are a few lessons learned from major outages that can help you reduce the possibility of an outage and help you cope when your site does go down.
Anticipate potential problems
It may be a cliché, but it’s good advice: “The best offence is a good defense.” Be proactive, and defend against potential website crashes by evaluating your network and systems before problems occur. Determine what could cause failure at critical points and determine where you need to build in system redundancy. Practice how to restore critical systems before they go down so you’ll be ready to take quick action if a real failure occurs.
Monitor your website traffic. If it’s steadily growing, be sure you have the capacity to handle future growth. Traffic growth can be unpredictable. A favorable review of your company and its services could cause a spike in traffic, and your site could go down if you’re not equipped to handle it.
Communicate with your customers
If your website is down for any length of time, use social media and email to keep your customers informed. Be realistic and honest with them – they will appreciate it, and you’ll get some goodwill out of a difficult situation. Let them know why the site crashed, what steps you are taking to get it back online and how long you think it’s going to take. If it’s taking longer than you anticipated, give your customers an updated report. An uniformed customer becomes an unhappy customer, and an unhappy customer becomes an ex-customer.
Let your customers know when your site is back online and thank them for their patience. If possible, offer your customers something of value to compensate them for their inconvenience. For example, if you provide a paid subscription service, offer your customers the service for free for a short time. Again, your objective is to make your customers happy and retain them.
Don’t try to fix problems on the fly
When your site goes down, you want to get back online as quickly as possible. However, a quick fix may not be a stable fix, and your site may crash again. Roll back to a previous, trusted version of your site while you diagnose what caused your website outage, and take the time to test a fix properly before you implement it.
Monitor your website performance
Always remember that everything is impermanent. Despite your best planning efforts, problems can occur and cause your website to go down. That is why you should monitor your website’s performance to know promptly if your website is down allowing immediate corrective action to get you back online.
Perhaps the best lesson is the most obvious – have a plan and react quickly to implement it when you have a website outage.
StatusCake Team
Share this
More from StatusCake
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026