Skip to main content

Understanding "Last Mile" WFH Connectivity

Paul Davenport
AppNeta

The mass rush to work-from-home (WFH) that took place back in the spring was a shock to the system for many enterprise networks. But with summer closing out and the prospects of a near-term return to office-centric workflows looking increasingly slim, enterprise IT teams that haven't gotten comfortable with their "new normal" need to start making changes fast.

But getting familiar with network connections your team doesn't own or control can be tricky for enterprise IT who are accustomed to managing a primarily branch-office footprint. These teams are relying on connectivity beyond the traditional network edge to give their users access to network resources and the apps they need to stay productive.

Unlike commercial connectivity, these residential connections — aka the "last mile" links between residential workstations and the network edge — aren't backed by ISP SLAs that guarantee upload and download speeds. Instead, this access is delivered "best effort," meaning any number of factors could impact how much network capacity is actually delivered out to a residential work station.

To begin with, residential connections don't enjoy nearly the network speeds of the office, putting workers at a disadvantage where performance is involved before random variances in last-mile delivery come into play.

But what may be surprising is just how this variance plays out over a widely-distributed enterprise footprint.

To help get ahead of issues impacting WFH users, teams need to first understand what they're working with when it comes to the new stakeholders involved in connecting end users with corporate network resources. This includes gaining a true understanding of the performance of ISPs, for instance, responsible for that last mile connectivity at each home location, as well as ensuring that the amount of capacity delivered to an individual user's home is adequate for the job.

When we at AppNeta closed our Boston and Vancouver offices back in March, we conducted an initial survey of our own WFH network connections — a practice we recommend every systems team does to help gain a baseline of expectations for network performance out to critical team members. We found that not only are most users' residential ISP offerings far off the capacity levels they're used to experiencing in-office, they're not even getting the full download and upload speeds that they've contracted for.



Compounded with the stress on the user's home network from non-business apps used by others throughout the household, this misalignment between expected and delivered capacity can sink worker productivity across teams.

This last mile, potentially between the enterprise network edge and a user's residential workstation, but more likely with the residential ISP, is where the bulk of performance issues arise in the WFH era, as reported by our own network management team and our enterprise customers. And while IT teams may not own, manage, or really control those residential last miles, they can still gain visibility into how that connection is performing to help resolve issues before they ripple across departments.

Teams need to understand what these variances are going to be so that even if they can't regain those lost seconds of dwell time because of the limitations on that last-mile connectivity, they at least have the data to baseline end-user expectations and inform improvements (and expected results) going forward. That means not only getting to the root of the problem (and proving innocence) fast, but also having the data handy to seek out resolution with the appropriate stakeholders.

Paul Davenport is Marketing Communications Manager at AppNeta

Hot Topics

The Latest

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

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

Understanding "Last Mile" WFH Connectivity

Paul Davenport
AppNeta

The mass rush to work-from-home (WFH) that took place back in the spring was a shock to the system for many enterprise networks. But with summer closing out and the prospects of a near-term return to office-centric workflows looking increasingly slim, enterprise IT teams that haven't gotten comfortable with their "new normal" need to start making changes fast.

But getting familiar with network connections your team doesn't own or control can be tricky for enterprise IT who are accustomed to managing a primarily branch-office footprint. These teams are relying on connectivity beyond the traditional network edge to give their users access to network resources and the apps they need to stay productive.

Unlike commercial connectivity, these residential connections — aka the "last mile" links between residential workstations and the network edge — aren't backed by ISP SLAs that guarantee upload and download speeds. Instead, this access is delivered "best effort," meaning any number of factors could impact how much network capacity is actually delivered out to a residential work station.

To begin with, residential connections don't enjoy nearly the network speeds of the office, putting workers at a disadvantage where performance is involved before random variances in last-mile delivery come into play.

But what may be surprising is just how this variance plays out over a widely-distributed enterprise footprint.

To help get ahead of issues impacting WFH users, teams need to first understand what they're working with when it comes to the new stakeholders involved in connecting end users with corporate network resources. This includes gaining a true understanding of the performance of ISPs, for instance, responsible for that last mile connectivity at each home location, as well as ensuring that the amount of capacity delivered to an individual user's home is adequate for the job.

When we at AppNeta closed our Boston and Vancouver offices back in March, we conducted an initial survey of our own WFH network connections — a practice we recommend every systems team does to help gain a baseline of expectations for network performance out to critical team members. We found that not only are most users' residential ISP offerings far off the capacity levels they're used to experiencing in-office, they're not even getting the full download and upload speeds that they've contracted for.



Compounded with the stress on the user's home network from non-business apps used by others throughout the household, this misalignment between expected and delivered capacity can sink worker productivity across teams.

This last mile, potentially between the enterprise network edge and a user's residential workstation, but more likely with the residential ISP, is where the bulk of performance issues arise in the WFH era, as reported by our own network management team and our enterprise customers. And while IT teams may not own, manage, or really control those residential last miles, they can still gain visibility into how that connection is performing to help resolve issues before they ripple across departments.

Teams need to understand what these variances are going to be so that even if they can't regain those lost seconds of dwell time because of the limitations on that last-mile connectivity, they at least have the data to baseline end-user expectations and inform improvements (and expected results) going forward. That means not only getting to the root of the problem (and proving innocence) fast, but also having the data handy to seek out resolution with the appropriate stakeholders.

Paul Davenport is Marketing Communications Manager at AppNeta

Hot Topics

The Latest

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

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...