ICMP / Ping monitoring

Ping what cloud monitors can't — and see more than a single number.

Cloud-based ping tools reach the public internet. Full stop. CuliPulse lets you run an agent on your own network so you can ping any host that lives there — routers, switches, internal servers, database hosts — with no public exposure required. And instead of one RTT number, you get packet loss, min/avg/max, and jitter, so you know the real story.

No credit card · free plan forever

The real CuliPulse page for a ping monitor watching a test host on a private network
Real console · demo workspace

More than a single number

Packet loss, RTT breakdown, and jitter — not just “up” or “down”.

A single average RTT hides a lot. A host that responds in 18 ms on average might be dropping 20% of packets and spiking to 90 ms on bad runs. CuliPulse surfaces the full picture every check cycle so you can see degradation before users feel it.

Every check sends a short burst of packets — 4 by default, up to 10 — and records how many came back, the average, the fastest and slowest round trip, and how much they varied.

The real checkpoints card of a ping monitor: the agent's latest result with packet loss, replies, average, range and jitter
Real console · demo workspace

Alert before it's fully down

Flag high packet loss or latency as degraded — don't wait for a complete outage.

A host that's dropping 30% of packets or averaging 200 ms is not “up” in any meaningful sense. CuliPulse can treat that as a degraded state and alert you — so you're investigating while users are only slightly affected, not scrambling after the fact.

Packet loss threshold

Set a maximum acceptable packet loss percentage. Cross it and the monitor goes degraded — a warning, not an outage, so you can triage before it's critical.

RTT threshold

Set a maximum average round-trip time. When latency climbs past it, the monitor flags degraded so you know something is wrong on the path.

Like a down alert, a degraded alert by default waits for two checks in a row, so one bad burst doesn't page you.

Reach what cloud can't

Ping private hosts on your own network — routers, switches, internal servers, anything.

Every cloud-based ping monitor pings from the public internet. That's fine for a public website — useless for the router in your rack, the database host that never has a public IP, or the internal server your team actually depends on.

An agent on your network. Install CuliPulse's lightweight agent on any machine that can reach your hosts. It runs the ping checks from there and reports back over outbound HTTPS — no inbound firewall rules.

No public exposure needed. Private hosts stay private: the agent starts every connection, so there are no ports to open. How agents work →

The real card of a customer-run agent on a private network: online, what it can check, its load
Real console · demo workspace

Start pinging in 2 minutes.

Add a ping monitor, point it at any host your agent can reach, set your loss and latency thresholds, and get alerts you can trust.