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

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

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

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

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

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