Network Destinations: ICMP Monitoring Feature Highlight - Obkio

Introducing Network Destinations, Obkio's all-new ICMP Monitoring feature.

Quick question: are you paying for a second tool just to ping a few IPs?

We heard that a lot. So we fixed it.

Now, here's the thing about Obkio.

We've always been laser-focused on agent-to-agent performance monitoring.

Our secret? Distributed monitoring agents.

Deploy them at your sites and over the Internet, and you get complete visibility between them, all in the app.

Works like a charm.

Since the beginning, we focused on performance and quality, not just up and down, doing things differently than traditional tools.

And that worked

But here's the thing: We log every support question and feature request.

And when we looked at the top requests, a pattern emerged.

People were frustrated: "What about our SaaS endpoints? What if we can't install agents there?"

Or they'd ask: "Can we use Visual Traceroute for servers we don't control?"

And then: "Look, we have printers, access switches, devices where we just need to know if they work. Can we do that without SNMP?"

And here's the kicker: "We're paying for PingPlotter on top of Obkio just to monitor a few critical IPs. Can you do that too?"

So when we were rebuilding Visual Traceroute from the ground up, re-engineering the whole thing to make it the best traceroute tool we could imagine,

We realized: this is the perfect time.

While we're at it, let's go all the way.

Let's expand the scope and address all these needs.

Because if we'd built all these advanced features but you still needed a second tool? That's not good enough.

So here we are.

Exactly one month after launching our new Visual Traceroute, we're ready to launch Network Destinations, our ICMP monitoring solution powered by the same traceroute engine you now have.

So what did we build? Network Destinations. And it's exactly what it sounds like. You get continuous traceroute monitoring, and when I say continuous, I mean a traceroute every second.

No agent needed. Point to any IP address or hostname.

Now, you might be thinking, isn't this just ping monitoring?

Not quite. We're doing continuous traceroutes, not just pings. And that's a big difference.

With ping, you know if something is up or down.

And when it's down, it's too late.

With traceroute, you see WHERE the problem is in the path.

If it's hop 1, your gateway, that's your problem. Hop 3? That's your ISP. Hop 8? That's the internet backbone.

The destination itself? You know exactly where it is.

Plus, you catch issues before they become critical. You see latency building up at a specific hop before everything goes down.

It's the same traceroute engine you already trust from Obkio, just now available for any endpoint where you can't deploy an agent.

But here's what makes it powerful: everything shows up in the same timeline.

Your agent monitoring sessions, your SNMP data, your Visual traceroutes, your APM, and now your Network Destinations, all correlated in one view.

So when something goes down, you immediately see the full picture.

Is it your network? Your ISP? The destination's infrastructure? You know right away.

And if you're one of those people running PingPlotter on top of Obkio just to monitor a few IPs?

One platform, one dashboard, everything together. And yes, Network Destinations are included in all plans.

Learn more: www.obkio.com/network-destinations-icmp-monitoring/