Taking the Business Failure Out of Website Crashes

Mehdi Daoudi
Catchpoint
Learn more about Catchpoint

The headlines are filled with news of retail website failures and crashes – most recently with the launch of Obamacare and the continuing healthcare.gov crashes due to high visitor load. Some of this attention is due to the media's insatiable appetite for bad news, some of it is fueled by massive user dissatisfaction, but for the most part; websites are just simply failing more.

Load-driven performance issues aside, the causes of most failures are unavoidable. Malicious attacks are getting more sophisticated; natural disasters are taking out datacenters like we saw with Sandy. Attaining perfection is impossible, so human error will always be a factor, and as we heard at Yahoo, sometimes even a single squirrel can bring business to a halt.

Quite often however, sites go down because organizations are not sufficiently prepared to manage the risks that exist because of the complexity that surrounds their sites. Most websites are intricate ecosystems of different services, tools and platforms. More players than ever are involved in creating a rich, engaging and profitable experience.

Operations must worry not only about the health of the infrastructure and applications they own and manage, but also about those of their vendors, their vendors’ vendors and so on. Just one broken component in the delivery chain of a website can take down the entire service, as we have seen in the case of SPoF (single point of failure).

So with all of this in mind, companies need to accept that failure will happen and plan for it to alleviate and minimize its negative business and branding impacts. As Benjamin Franklin once said, "By failing to prepare, you are preparing to fail." By planning, you can get creative, as did the New York Times when it took to social media to keep pushing the news when its site went down in August.

Prevention and Readiness

So, how to plan?

1. Identify every situation that can make your business fail - Dig through every part of your infrastructure and applications and identify who your vendors are and what their impacts are to your service.

2. Monitor every aspect of your site's availability on a regular basis – Keep an eye on your partners’ servers to truly understand the availability of your site.

3. Do capacity testing on all of your servers - Test load balancers, front end, back end, edge servers, vendors – everything.

4. Design your strategy for each case of failure - Ensure you have a capacity plan for the worst case scenario and build it into your release cycle. A capacity plan is especially important before an event or promotion when you expect a lot of traffic to come to your site. Smart companies will stagger promotions to prevent drastic spikes in traffic.

As a backup plan, have a lightweight site ready and on hand if your business requires 100 percent uptime. Even if it's simply a bunch of Apache servers hosted in the cloud, have one ready. Absolutely no third parties or personalization, keep it bare-boned so it can be turned on during any and all types of downtime.

Creative Response to Failures

When you do fail, make it fun and give what could be a frustrated user a chuckle. This will provide a happy memory of your page even if they were unable to access it and will elicit a better chance of return.

A good error page is like a good airport bar. You are still stuck at the airport, but at least you are enjoying yourself.

Recovery

If you do experience a site crash:

1. Offer some incentive for your customers to come back and revisit the site once it's back up - Offer a "failure discount" to keep a customer from immediately going to a competing site to purchase the power drill they originally intended to buy from you.

2. Collect data during the outage - Monitor and understand what is going on to determine the root cause and analyze the events leading up to the downtime.

3. Ask questions - Have we experienced this before? Was my infrastructure at fault? Could this have been avoided? Understanding the failure allows you to adjust your disaster plans accordingly.

4. Share your post-mortem analysis both internally and externally - Let everyone learn what you learned; sharing knowledge is the best way to make the web better, stronger and faster for everyone.

Mehdi Daoudi is CEO and Co-Founder of Catchpoint

Related Links

Hot Topics

Related Vendors

The Latest

As AI Scales Across Enterprises, Breaking Points Emerge

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

Preparing Network Infrastructure for AI Starts with the Basics

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Agentic Operations Begin with Governed Middleware Access

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

The Network Data Problem Slowing Down Enterprise AIOps

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

The Governance Gap Behind AI's Infrastructure Problem

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

MEAN TIME TO INSIGHT Podcast - Episode 27: Observability Unification

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

5 Reasons Traditional VPNs Struggle in a Cloud-First World

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

What 1.8 Million Outages Say About Who Is Really On Call in August

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

Why Enterprises Are So Unhappy with Their IT Infrastructure

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

Agentic AI Just Became Your Newest Production Dependency. Are You Tracking It Like One?

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...

Taking the Business Failure Out of Website Crashes

Mehdi Daoudi
Catchpoint
Learn more about Catchpoint

The headlines are filled with news of retail website failures and crashes – most recently with the launch of Obamacare and the continuing healthcare.gov crashes due to high visitor load. Some of this attention is due to the media's insatiable appetite for bad news, some of it is fueled by massive user dissatisfaction, but for the most part; websites are just simply failing more.

Load-driven performance issues aside, the causes of most failures are unavoidable. Malicious attacks are getting more sophisticated; natural disasters are taking out datacenters like we saw with Sandy. Attaining perfection is impossible, so human error will always be a factor, and as we heard at Yahoo, sometimes even a single squirrel can bring business to a halt.

Quite often however, sites go down because organizations are not sufficiently prepared to manage the risks that exist because of the complexity that surrounds their sites. Most websites are intricate ecosystems of different services, tools and platforms. More players than ever are involved in creating a rich, engaging and profitable experience.

Operations must worry not only about the health of the infrastructure and applications they own and manage, but also about those of their vendors, their vendors’ vendors and so on. Just one broken component in the delivery chain of a website can take down the entire service, as we have seen in the case of SPoF (single point of failure).

So with all of this in mind, companies need to accept that failure will happen and plan for it to alleviate and minimize its negative business and branding impacts. As Benjamin Franklin once said, "By failing to prepare, you are preparing to fail." By planning, you can get creative, as did the New York Times when it took to social media to keep pushing the news when its site went down in August.

Prevention and Readiness

So, how to plan?

1. Identify every situation that can make your business fail - Dig through every part of your infrastructure and applications and identify who your vendors are and what their impacts are to your service.

2. Monitor every aspect of your site's availability on a regular basis – Keep an eye on your partners’ servers to truly understand the availability of your site.

3. Do capacity testing on all of your servers - Test load balancers, front end, back end, edge servers, vendors – everything.

4. Design your strategy for each case of failure - Ensure you have a capacity plan for the worst case scenario and build it into your release cycle. A capacity plan is especially important before an event or promotion when you expect a lot of traffic to come to your site. Smart companies will stagger promotions to prevent drastic spikes in traffic.

As a backup plan, have a lightweight site ready and on hand if your business requires 100 percent uptime. Even if it's simply a bunch of Apache servers hosted in the cloud, have one ready. Absolutely no third parties or personalization, keep it bare-boned so it can be turned on during any and all types of downtime.

Creative Response to Failures

When you do fail, make it fun and give what could be a frustrated user a chuckle. This will provide a happy memory of your page even if they were unable to access it and will elicit a better chance of return.

A good error page is like a good airport bar. You are still stuck at the airport, but at least you are enjoying yourself.

Recovery

If you do experience a site crash:

1. Offer some incentive for your customers to come back and revisit the site once it's back up - Offer a "failure discount" to keep a customer from immediately going to a competing site to purchase the power drill they originally intended to buy from you.

2. Collect data during the outage - Monitor and understand what is going on to determine the root cause and analyze the events leading up to the downtime.

3. Ask questions - Have we experienced this before? Was my infrastructure at fault? Could this have been avoided? Understanding the failure allows you to adjust your disaster plans accordingly.

4. Share your post-mortem analysis both internally and externally - Let everyone learn what you learned; sharing knowledge is the best way to make the web better, stronger and faster for everyone.

Mehdi Daoudi is CEO and Co-Founder of Catchpoint

Related Links

Hot Topics

Related Vendors

The Latest

As AI Scales Across Enterprises, Breaking Points Emerge

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

Preparing Network Infrastructure for AI Starts with the Basics

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Agentic Operations Begin with Governed Middleware Access

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

The Network Data Problem Slowing Down Enterprise AIOps

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

The Governance Gap Behind AI's Infrastructure Problem

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

MEAN TIME TO INSIGHT Podcast - Episode 27: Observability Unification

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

5 Reasons Traditional VPNs Struggle in a Cloud-First World

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

What 1.8 Million Outages Say About Who Is Really On Call in August

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

Why Enterprises Are So Unhappy with Their IT Infrastructure

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

Agentic AI Just Became Your Newest Production Dependency. Are You Tracking It Like One?

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...