Ping monitor online
Logdash does not send ICMP ping; it requests your URL over HTTP every 5 minutes for free, which answers what ping cannot: whether the site serves pages, not just whether the machine is switched on.
Most people searching for a ping monitor want to know when their website goes down. ICMP ping answers a narrower question: does the network stack on that IP address reply. Logdash does not do ICMP. The checker on this page sends an HTTP GET instead, records the status code and response time, and counts anything outside 200 to 399, or no answer within 10 seconds, as down.
Why a website ping monitor should use HTTP
- The machine replies to ping while nginx is stopped, the app has crashed or the database is gone. Ping stays green and every visitor gets a 502.
- Behind Cloudflare or another proxy CDN, ping reaches the edge, not your server. Your origin can be down for hours and ping will never notice.
- Plenty of firewalls and cloud networks drop ICMP by default, so ping reports down while the site serves pages fine.
- An HTTP check measures the request your users make, so its response time means something. Ping latency is network distance and nothing else.
Ping and HTTP side by side
# ICMP: does the machine answer?
ping -c 4 example.com
# HTTP: does the site answer? This is what Logdash checks.
curl -sS -o /dev/null -L --max-redirs 5 -m 10 \
-w '%{http_code} in %{time_total}s\n' https://example.comRead them together. Ping fine and curl 200: all good. Ping fine and curl 502 or 000: the box is up and the app is not, the case ping alone misses. Ping lost and curl 200: ICMP is blocked, and the site is fine. Both failing: the host or its network is gone. The third case is common enough that a ping-only monitor will wake you for a site that never went down.
The other kind of ping
Some tools use ping for the opposite direction: your cron job or worker calls the monitor, and silence means it died. Logdash has that as push monitors on the Pro plan. The worker sends POST https://api.logdash.io/ping/<monitorId>, no auth header, no body, and the monitor goes down on the first 15-second window without one. So it pings from a loop every few seconds. A nightly job that pings once would read as down all day, and Healthchecks.io or Cronitor fit that better.
When you really need ICMP ping
Some things have no web server to check: a router, a NAS, a VPN gateway, a printer, the internet connection at your office. For those, ICMP is the right tool, and Logdash cannot do it today. UptimeRobot includes ping monitors on its free plan, 50 monitors at 5-minute intervals, and is the better pick for that job.
Logdash vs UptimeRobot
| Feature | Logdash | UptimeRobot |
|---|---|---|
| ICMP ping | Not shipped | Included on the free plan |
| Free HTTP check interval | Every 5 minutes | Every 5 minutes |
| Free monitors | 5 services, one HTTP monitor each | 50 |
| Fastest paid interval | 15 seconds on Pro | 30 seconds on Team |
| App logs and metrics beside the check | Eight SDKs into the same service | Not part of the product |
When UptimeRobot is the better pick
- You need to ping hardware or hosts with no HTTP endpoint. Logdash has no ICMP, port or keyword checks.
- You have more than five things to watch and no budget. 50 free monitors beats five.
- You want email or SMS alerts. Logdash sends Telegram messages and webhooks, and nothing else.
Set it up in 3 steps
- Check the URL Paste your site into the checker. The first result arrives in about a second with the status code and response time, no signup.
- Claim it and pick the interval Sign in with a free account to keep the monitor. Every 5 minutes on the free plan, every minute on Builder, every 15 seconds on Pro, which is 5,760 checks a day.
- Connect Telegram and test it Add a Telegram channel to the monitor, then stop the web server and leave the machine up. Ping would stay green. The next check fails and a Telegram alert arrives saying the site is down.