Skip to main content

Today's Top WAN Issues and How to Solve Them - Part 1

The top pain points associated with Internet-based WANs
Jay Botelho

Enterprise wide-area networks (WANs) have undergone an incredible transformation over the past several years. More often than not, they're hybrid, offering multiple connection paths between WANs. This provides many benefits but also makes them more challenging to manage than ever before. Managed WAN services, such as MPLS, continue to play a significant role in enterprise networks, but the Internet has become a feasible WAN connectivity option that is typically less costly than MPLS and is actually essential in the case of direct cloud connectivity.

As a result, many enterprises adopt custom hybrid networks or full-blown SD-WAN implementations, combining managed WAN services and Internet to address various business requirements. A whopping 98% of enterprises are currently engaged in SD-WAN deployments. Nearly 40% (37%) of enterprises have fully implemented SD-WAN implementations in 2021, compared to just 28% two years ago. However, by their very nature, hybrid enterprise networks are complex and difficult to visualize, troubleshoot and optimize.

So, based on fascinating insights from new EMA research, let's examine today's top WAN challenges and what you need to know to address them.

In Part 1 of this series, we'll explore the top pain points associated with Internet-based WANs specifically:

1. Managing Multiple ISP Relationships

Nearly one-third of organizations struggle with the complexity of juggling multiple ISP relationships to procure and manage connectivity. In which scenario is each ISP most effective? Is splitting traffic between them the right move? If so, what's the best way to determine the allocation? These are just some of the questions that undoubtedly come up. Beyond that, you must also manage SLAs, monitor for outages or slowdowns, reroute traffic as needed and more.

For example, let's say you split traffic between two ISPs — on for web traffic and the other for all web-hosted productivity apps (email, Salesforce, etc.). This works well until one ISP goes down, in which case you'd need to reroute all traffic to the other. That's when traffic prioritization issues cascade into poor connectivity that'll degrade user experiences and hurt your business. These types of circumstances are why you must be capable of properly visualizing, classifying and prioritizing traffic across all ISPs at all times.

2. Security Risks

Roughly 30% of IT professionals see security risks as a top ongoing challenge when it comes to their Internet-based WAN. You have little control over security once traffic hits the public Internet, and are often forced to rely on users to follow security best practices. As more users are working remotely, access from the public Internet and connections from it to your hosted services and applications are more exposed to security threats.

This path can allow adversaries to avoid most of the security controls IT departments often rely upon, such as firewall rules, IDS/IPS, etc., making corporate data protection subject to individual employees' security practices (or lack thereof). Employees may lack high-quality IDS/IPS on their home networks, making them more vulnerable to phishing attempts and various malware attacks. In most cases, the lack of close IT control puts corporate data directly in jeopardy.

3. Overall Application Performance

Maintaining application performance is a top issue for 28% of organizations this year. You can't effectively manage application performance without traffic prioritization, which is virtually impossible to enforce once traffic hits the public Internet. With a hub/spoke architecture, you can contract for a big pipe, and average a large number of users across that pipe to ensure consistent performance and a reasonable cost per user. But as we drive towards more and more remote users and locations, it is more difficult to manage all of these remote Internet connections, and guarantee performance.

For example, imagine a video production studio that needs to transfer massive, 100GB+ files regularly. Even when the employees are working at the office, and assuming a 1Gbps Internet connection, transferring a 100GB file could consume the network for over 13 minutes. We also know most remote offices and home networks have 100 — 300Mbps Internet connections, so it's easy to see how a single large transfer could bottleneck a poorly managed network. As networks become more complex and distributed, performance management can be incredibly troublesome and even out of your control in certain circumstances.

4. Inconsistent Quality Across Multiple ISPs

Nearly one in four organizations see inconsistent quality across multiple ISPs as a significant challenge for their business. This is because each ISP uses its own technologies and rolls out updates at its own speed. And IPSs don't treat all areas equally; they're focused on servicing the broadest population possible with minimum investment. This can lead to underserved geographies and poor quality for organizations operating within them.

In a given city, ISPs may provide more bandwidth to business parks than residential areas and the maximum bandwidth available to you may depend on the zip code in which you and your employees operate. The maximum available connection speeds and the demand in the particular neighborhood can both limit bandwidth. As users, and therefore the network, become increasingly distributed, controlling user experiences will become extremely challenging.

Read Start with Part 2 of this series, in which we'll outline today's most high-profile SD-WAN deployment challenges, as well as best practices you can use to identify, evaluate and overcome the various issues associated with modern WANs.

Go to: Today's Top WAN Issues and How to Solve Them - Part 2

Hot Topics

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Today's Top WAN Issues and How to Solve Them - Part 1

The top pain points associated with Internet-based WANs
Jay Botelho

Enterprise wide-area networks (WANs) have undergone an incredible transformation over the past several years. More often than not, they're hybrid, offering multiple connection paths between WANs. This provides many benefits but also makes them more challenging to manage than ever before. Managed WAN services, such as MPLS, continue to play a significant role in enterprise networks, but the Internet has become a feasible WAN connectivity option that is typically less costly than MPLS and is actually essential in the case of direct cloud connectivity.

As a result, many enterprises adopt custom hybrid networks or full-blown SD-WAN implementations, combining managed WAN services and Internet to address various business requirements. A whopping 98% of enterprises are currently engaged in SD-WAN deployments. Nearly 40% (37%) of enterprises have fully implemented SD-WAN implementations in 2021, compared to just 28% two years ago. However, by their very nature, hybrid enterprise networks are complex and difficult to visualize, troubleshoot and optimize.

So, based on fascinating insights from new EMA research, let's examine today's top WAN challenges and what you need to know to address them.

In Part 1 of this series, we'll explore the top pain points associated with Internet-based WANs specifically:

1. Managing Multiple ISP Relationships

Nearly one-third of organizations struggle with the complexity of juggling multiple ISP relationships to procure and manage connectivity. In which scenario is each ISP most effective? Is splitting traffic between them the right move? If so, what's the best way to determine the allocation? These are just some of the questions that undoubtedly come up. Beyond that, you must also manage SLAs, monitor for outages or slowdowns, reroute traffic as needed and more.

For example, let's say you split traffic between two ISPs — on for web traffic and the other for all web-hosted productivity apps (email, Salesforce, etc.). This works well until one ISP goes down, in which case you'd need to reroute all traffic to the other. That's when traffic prioritization issues cascade into poor connectivity that'll degrade user experiences and hurt your business. These types of circumstances are why you must be capable of properly visualizing, classifying and prioritizing traffic across all ISPs at all times.

2. Security Risks

Roughly 30% of IT professionals see security risks as a top ongoing challenge when it comes to their Internet-based WAN. You have little control over security once traffic hits the public Internet, and are often forced to rely on users to follow security best practices. As more users are working remotely, access from the public Internet and connections from it to your hosted services and applications are more exposed to security threats.

This path can allow adversaries to avoid most of the security controls IT departments often rely upon, such as firewall rules, IDS/IPS, etc., making corporate data protection subject to individual employees' security practices (or lack thereof). Employees may lack high-quality IDS/IPS on their home networks, making them more vulnerable to phishing attempts and various malware attacks. In most cases, the lack of close IT control puts corporate data directly in jeopardy.

3. Overall Application Performance

Maintaining application performance is a top issue for 28% of organizations this year. You can't effectively manage application performance without traffic prioritization, which is virtually impossible to enforce once traffic hits the public Internet. With a hub/spoke architecture, you can contract for a big pipe, and average a large number of users across that pipe to ensure consistent performance and a reasonable cost per user. But as we drive towards more and more remote users and locations, it is more difficult to manage all of these remote Internet connections, and guarantee performance.

For example, imagine a video production studio that needs to transfer massive, 100GB+ files regularly. Even when the employees are working at the office, and assuming a 1Gbps Internet connection, transferring a 100GB file could consume the network for over 13 minutes. We also know most remote offices and home networks have 100 — 300Mbps Internet connections, so it's easy to see how a single large transfer could bottleneck a poorly managed network. As networks become more complex and distributed, performance management can be incredibly troublesome and even out of your control in certain circumstances.

4. Inconsistent Quality Across Multiple ISPs

Nearly one in four organizations see inconsistent quality across multiple ISPs as a significant challenge for their business. This is because each ISP uses its own technologies and rolls out updates at its own speed. And IPSs don't treat all areas equally; they're focused on servicing the broadest population possible with minimum investment. This can lead to underserved geographies and poor quality for organizations operating within them.

In a given city, ISPs may provide more bandwidth to business parks than residential areas and the maximum bandwidth available to you may depend on the zip code in which you and your employees operate. The maximum available connection speeds and the demand in the particular neighborhood can both limit bandwidth. As users, and therefore the network, become increasingly distributed, controlling user experiences will become extremely challenging.

Read Start with Part 2 of this series, in which we'll outline today's most high-profile SD-WAN deployment challenges, as well as best practices you can use to identify, evaluate and overcome the various issues associated with modern WANs.

Go to: Today's Top WAN Issues and How to Solve Them - Part 2

Hot Topics

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...