Obkio
Obkio monitors network performance between locations, users and services, helping IT teams identify connectivity problems and investigate their causes.
Why it caught my attention
Network problems often disappear before anyone can investigate them. Obkio continuously measures connections between locations, creating a historical record of performance and routing behaviour. That makes it particularly interesting for troubleshooting intermittent problems affecting branch offices, remote workers and cloud services.
What problem does this actually solve?
Obkio could be worth considering if you recognise any of these challenges.
Intermittent network problems go unnoticed
Continuous measurements capture performance degradation that might disappear before IT staff can investigate it.
Slow connections have unclear causes
Historical traceroutes help identify where delays or packet loss appeared along a network path.
Remote locations lack performance visibility
Distributed monitoring agents measure connections from offices and remote locations rather than relying on one central monitoring point.
Network faults trigger unnecessary guesswork
Combining connection measurements with device information helps teams investigate whether problems originate internally or elsewhere.
Is this a good fit for you?
A quick way to see if Obkio is relevant for your situation.
- You manage network connections across multiple offices or cloud environments.
- Your users report intermittent slowness, disconnections or poor call quality.
- You need evidence when investigating problems with Internet service providers.
- You support remote workers and need visibility beyond central infrastructure.
- You want historical network measurements to support troubleshooting and incident reviews.
- You only need basic device availability checks or occasional connectivity tests.
- Your priority is inspecting application code rather than network connectivity.
How does it work?
In practice, the workflow looks something like this:
Install software or virtual agents at relevant sites, use dedicated hardware where appropriate, or select available public monitoring agents.
Set up monitoring templates and sessions between agents, such as a branch office and data centre or cloud-hosted location.
Agents exchange small test packets to measure latency, jitter and packet loss, with results sent to Obkio's cloud platform.
Review performance graphs, traceroutes and available device measurements to identify when problems occurred and where to investigate further.
What else should I know?
A few important things to be aware of before you investigate further.
Agent placement affects monitoring coverage
Detailed two-way measurements require agents at both ends of a connection; agentless destination monitoring provides different diagnostic capabilities.
A cloud service processes measurements
Monitoring results are analysed through Obkio's cloud platform, so review connectivity, data handling and organisational requirements.
Firewall access may need configuring
Agents require appropriate network communication permissions, including UDP traffic between agents and access to Obkio services.
Subscription limits affect monitoring scope
Plans limit available monitoring sessions and may differ in features; confirm current allowances before planning a larger deployment.
Think Obkio could fit your environment?
Visit the Obkio website to find out more, request a demo or speak to their team.
Something you'd like to know about Obkio?
Is there something I haven't covered in my research? Send me your question and I'll look into it and reply personally by email.