Operations | Monitoring | ITSM | DevOps | Cloud

Poor voice call quality isn't just annoying, it's a productivity killer. Dropped calls mid-negotiation, garbled audio on client meetings, and one-sided conversations where half the words don't make it through: these aren't random technical glitches. They're symptoms of network performance problems that haven't been identified, measured, or fixed. And when your business runs on VoIP, Microsoft Teams, or any cloud-based communication platform, unmeasured voice quality is a liability.

Your apps are slow. Users are complaining. You're staring at a dashboard trying to figure out what broke and when. Sound familiar? This is the reality of reactive network monitoring. By the time someone opens a ticket, the issue has already been affecting performance for minutes, sometimes hours. A network health check flips that script. Instead of chasing problems after the fact, you're catching them before users ever notice.

In 2016, before Obkio existed, we ran a market audit. We interviewed banks, manufacturing companies, and service providers, and asked them one simple question: Why aren't you using a Network Performance Monitoring solution? The answer was unanimous: the tools were too complex, and nobody had the internal resources to run them full-time. If that was true for enterprises with dedicated networking staff, it was even more true for smaller businesses with generalist IT teams.

It's 2 AM. The Network Is Down. Where Do You Start? You get the call. Users can't connect. VoIP is choppy. Something is broken somewhere between your office and the cloud. You open your monitoring dashboard and it says something is wrong, but not where. Not why. Not since when? So you do what IT teams have done for decades. You open a terminal, run a traceroute, SSH into the router, pull up SNMP, check the firewall logs.

In 2016, Obkio was just an idea, but it was an idea born from a real problem. Before writing a single line of code, we conducted a market audit to understand why Network Performance Monitoring solutions weren't more mature. We interviewed banks, manufacturing companies, and service providers, and the answer was unanimous: the NPM tools on the market were too complex, and most businesses simply didn't have the internal resources to dedicate full-time to managing them.

Most companies rewired how their people work, not once but twice. First for remote, then for RTO (Return to Office). Their network monitoring never caught up. So, what happened? IT teams are managing a network that spans headquarters, branch offices, home setups, and cloud apps with tools that still assume everyone's connecting back to one place. When something breaks (and it will), nobody can pinpoint where. IT takes the blame. Users lose productivity. Leadership loses patience.

IT teams are being held hostage in the return-to-office debate. They didn't even get a seat at the table. And if you're not at the table, you're on the menu. The job market has cooled dramatically. Canada's unemployment rate hit 7.1% in August 2025, which is the highest since May 2016, excluding pandemic years. Employers noticed. And the RTO mandates started rolling out fast: The debate is heating up. Employees don't want to give up remote work. Executives want people in the office seats.

When your company’s help desk receives fifteen "my connection is slow" tickets from remote employees in a single morning. Your network monitoring dashboard shows everything green; VPN concentrators running smoothly, bandwidth usage normal, no alerts. Yet employees can't get their work done. You try to ping their home routers. Nothing. Attempt a traceroute to diagnose the path. It dies at the ISP edge. Check your SNMP queries. They never make it past the residential gateway.

The rise of hybrid work has fundamentally changed where IT problems occur. Five years ago, most network issues happened in your data center or office network (infrastructure you could access, control, and troubleshoot directly). Today, the majority of critical issues occur in home offices, coffee shops, and remote locations where you have zero infrastructure access and limited visibility.

The way we work has fundamentally changed. Remote and hybrid work aren't temporary shifts; they're the new reality for most organizations. And with that reality comes a challenge IT teams know all too well: how do you troubleshoot network issues for users you can't physically reach?