Operations | Monitoring | ITSM | DevOps | Cloud

You know the conversation. Calls are choppy, users are complaining, and Obkio shows packet loss on the path to your ISP. You open a ticket, and they reply, "Everything looks fine on our end." Now you're stuck taking screenshots, exporting graphs, and trying to explain data to someone who can't see it. Meanwhile, the problem keeps happening. Today we're launching Shareable Links. With one click, you can create a read-only link to any Network Monitoring Session and send it to anyone.

Your Internet circuit is up. The firewall shows the WAN link as connected, your ISP's status page is green, and a speed test comes back at full provisioned bandwidth. Meanwhile, Teams calls at one branch break up for ten minutes every afternoon, and every user at that site sees Salesforce slow to a crawl at the same moment. Then everything recovers before anyone can capture it.

Your Internet link averages 40% utilization, yet users still complain that calls drop and SaaS apps crawl every morning at 9:00. Averages are where bandwidth problems hide. A five-minute polling interval can smooth a 30-second saturation spike into a flat, healthy-looking line. A total-usage graph also won't tell you whether the traffic is a backup job, a compromised endpoint, or an ISP delivering less than you're paying for.

A user opens a ticket: "The Internet is slow." IT checks the network. Bandwidth looks fine, no outages, no alerts firing. They check with the ISP, but nothing on their end either. Everything upstream checks out, and yet the user is still stuck watching a spinning wheel. What rarely gets checked is the one component sitting closest to the problem: the machine's own network interface.

If your network has been feeling sluggish, connections keep dropping, or you're getting alerts that don't point to an obvious cause, high bandwidth usage is one of the most common culprits and one of the hardest to pin down without the right visibility. The tricky part is that "slow network" can mean a dozen different things depending on where the congestion is actually happening.

Latency spikes that come and go. Packet loss that shows up for a few minutes, then disappears. None of it traces back to anything on your LAN, your firewall, or your switches because it isn't happening there. It's happening on the physical link between your building and your ISP's network: the local loop. This article covers what the ISP local loop is, what typically goes wrong with it, the most common root causes, and how to diagnose a local loop issue using traceroute data and Obkio Insights.

Every pair of Monitoring Agents in your Obkio account create a Network Monitoring Session to monitor network performance between the two agents. Every one of those monitoring sessions comes with its own dedicated page, automatically. You'll find it under the Network Performance tab: click into it, pick a network monitoring session from the list, and the full page loads for that specific connection.

Today, we’re launching Obkio Insights, our biggest feature yet, in beta, and the one we’ve been building toward for 8 years. Insights is launching in beta. That means existing customers can start using automatic network diagnostics today, with more root cause coverage, refinements, and improvements rolling out over the coming months based on real-world feedback. As with any beta, you may run into the occasional bug or rough edge.

Obkio is making improvements to its network performance monitoring and observability solution, aimed at helping users of every expertise level interpret their data more efficiently. That work isn't just about telling users something is wrong. It's about diagnosing the issue for them. And a big part of that is telling them where the issue is happening, so they know exactly where to direct their troubleshooting effort instead of guessing. The Status Overview widget solves this.

Obkio’s new Severity Summary widget is built to answer one question fast: “How healthy was my network overall, across every session I'm tracking?” Instead of opening session after session to check each one individually, you get a single combined view showing how much time your network spent in each severity level.