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

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

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

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...