Skip to main content

Down Goes the Internet (Again) – Part Two: 4 Strategies to Ensure Website Performance

Start with Part One of this article: Down Goes the Internet (Again) – Are You Ready?

In this era of unprecedented complexity, it's virtually impossible for a modern website to eliminate all the risk associated with using third parties. However, there are proactive strategies an organization can implement to better manage and minimize their risk. These include:

1. Proactively monitor speed and availability

Proactively monitor the speed and availability of websites, web applications and mobile sites from the true end-user perspective.

Today, there are so many elements out there on the web that stand between your data center and your users, including not just third-party services, but content delivery networks (CDNs), local and regional ISPs, mobile carrier networks and browsers, for example. Measuring performance from your data center alone is insufficient – unless, of course, your users live in your data center, which is highly unlikely.

The true browser-based perspective is the only place where you can accurately gauge your user's experience at the end of an extremely long and complicated technology path known as the application delivery chain. Today's new generation application performance management (APM) solutions are based on this true user perspective.

2. Monitor all transactions

Monitor all transactions, 24x7 along the complete application delivery chain. Sampling is not a sufficient means of gauging performance, of course, because a major performance issue may very well occur outside your testing interval – think of the Amazon EC2 outage that impacted Netflix on Christmas day last year!

Due to the unpredictability of major service outages, you need to be monitoring all transactions around the clock, to identify all performance aberrations and their root causes – both within and beyond the firewall – quickly and accurately, and get ahead of them.

3. Baseline and uphold performance-focused SLAs

Service-level agreements (SLAs) promising a certain level of availability on the part of a third-party service provider mean very little when it comes to performance.

For example, just because your cloud service provider's servers are up and running does not mean your users are experiencing an acceptable level of speed and reliability. Remember, third party services of all types are serving thousands of customers like you around the globe, and a spike in another customer's traffic may impact you.

With little insight into third party service providers' capacity planning decisions, you need to monitor performance levels yourself to ensure they don't drop off, and validate these against performance-focused SLAs. To get a sense of how a third party service provider may be impacting your overall performance, it can be helpful to compare your site's speed and availability before the third party service is added, to afterwards.

4. Utilize industry resources

Utilize industry resources to better assess if the source of a performance problem lies with you or one of your third-party service providers, as well as the likely performance impact on your customers.

These services may not prevent third party service outages from happening, but they can help companies better understand the source of performance problems so they can get in front of them more confidently and efficiently.

Conclusion

The reality is: the delivery chain underlying the services we often take for granted is so tenuous, that it's a marvel they don't break down more often. While outages may be inevitable, this does not make them any less costly or damaging to a company's reputation and revenues.

For example, on August 19, Amazon's North American retail site went down for about 49 minutes, with visitors greeted with the word “oops.” No explanation was given, but one estimate by Forbes put the cost to Amazon at nearly $2 million in sales.

But it's not just the “big guys” like Amazon that you need to focus on. The fact is that little storms are happening on the internet all the time, and you need to be prepared for them. When it comes to surviving and thriving in the age of increasing web complexity, an ounce of prevention can be worth a pound of cure. By taking advantage of several relatively simple and inexpensive approaches, organizations can better exploit all that third party services have to offer, while reducing the inherent risks.

Klaus Enzenhofer is Technology Strategist for Compuware APM’s Center of Excellence.

Down Goes the Internet (Again) – Part One: Are You Ready?

The Latest

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 ...

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? ...

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 ...

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 ...

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 ...

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 ... 

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 ...

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 ...

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 ...

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 ...

Down Goes the Internet (Again) – Part Two: 4 Strategies to Ensure Website Performance

Start with Part One of this article: Down Goes the Internet (Again) – Are You Ready?

In this era of unprecedented complexity, it's virtually impossible for a modern website to eliminate all the risk associated with using third parties. However, there are proactive strategies an organization can implement to better manage and minimize their risk. These include:

1. Proactively monitor speed and availability

Proactively monitor the speed and availability of websites, web applications and mobile sites from the true end-user perspective.

Today, there are so many elements out there on the web that stand between your data center and your users, including not just third-party services, but content delivery networks (CDNs), local and regional ISPs, mobile carrier networks and browsers, for example. Measuring performance from your data center alone is insufficient – unless, of course, your users live in your data center, which is highly unlikely.

The true browser-based perspective is the only place where you can accurately gauge your user's experience at the end of an extremely long and complicated technology path known as the application delivery chain. Today's new generation application performance management (APM) solutions are based on this true user perspective.

2. Monitor all transactions

Monitor all transactions, 24x7 along the complete application delivery chain. Sampling is not a sufficient means of gauging performance, of course, because a major performance issue may very well occur outside your testing interval – think of the Amazon EC2 outage that impacted Netflix on Christmas day last year!

Due to the unpredictability of major service outages, you need to be monitoring all transactions around the clock, to identify all performance aberrations and their root causes – both within and beyond the firewall – quickly and accurately, and get ahead of them.

3. Baseline and uphold performance-focused SLAs

Service-level agreements (SLAs) promising a certain level of availability on the part of a third-party service provider mean very little when it comes to performance.

For example, just because your cloud service provider's servers are up and running does not mean your users are experiencing an acceptable level of speed and reliability. Remember, third party services of all types are serving thousands of customers like you around the globe, and a spike in another customer's traffic may impact you.

With little insight into third party service providers' capacity planning decisions, you need to monitor performance levels yourself to ensure they don't drop off, and validate these against performance-focused SLAs. To get a sense of how a third party service provider may be impacting your overall performance, it can be helpful to compare your site's speed and availability before the third party service is added, to afterwards.

4. Utilize industry resources

Utilize industry resources to better assess if the source of a performance problem lies with you or one of your third-party service providers, as well as the likely performance impact on your customers.

These services may not prevent third party service outages from happening, but they can help companies better understand the source of performance problems so they can get in front of them more confidently and efficiently.

Conclusion

The reality is: the delivery chain underlying the services we often take for granted is so tenuous, that it's a marvel they don't break down more often. While outages may be inevitable, this does not make them any less costly or damaging to a company's reputation and revenues.

For example, on August 19, Amazon's North American retail site went down for about 49 minutes, with visitors greeted with the word “oops.” No explanation was given, but one estimate by Forbes put the cost to Amazon at nearly $2 million in sales.

But it's not just the “big guys” like Amazon that you need to focus on. The fact is that little storms are happening on the internet all the time, and you need to be prepared for them. When it comes to surviving and thriving in the age of increasing web complexity, an ounce of prevention can be worth a pound of cure. By taking advantage of several relatively simple and inexpensive approaches, organizations can better exploit all that third party services have to offer, while reducing the inherent risks.

Klaus Enzenhofer is Technology Strategist for Compuware APM’s Center of Excellence.

Down Goes the Internet (Again) – Part One: Are You Ready?

The Latest

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 ...

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? ...

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 ...

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 ...

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 ...

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 ... 

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 ...

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 ...

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 ...

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 ...