Ping monitoring that knows when a machine drops off the network.

When a host stops answering, everything running on it is down with it. Uptimia pings the host every 30 seconds from 171+ locations and pages you once several regions confirm it's unreachable — a dropped packet at one location never wakes anyone.

Start free trial → View pricing
30-day free trial · ICMP and TCP ping No credit card GDPR-ready
Fastest interval
30s
Alert channels
12
Checkpoints
171+
Countries covered
70+

The night the gateway went quiet

Nobody rebooted it and nothing was scheduled. At 03:12 the gateway simply stopped answering, and the only trace anywhere was a checkpoint in Mumbai getting silence back.

03:12:09 gw1.caldmont.com stops replying to pingMumbai gets no reply at all on a 30-second check — no alert yet impact: none
03:12:16 São Paulo, Sydney and Mumbai agreeOne incident opens; Slack, SMS and PagerDuty fire 7 s later impact: none
03:18 On-call acknowledges from the alert itselfSigned link, one tap, no login · MTTA 6 min impact: none
03:36 Recovered — with proof attachedRound-trip times, the probe's response and a traceroute — captured at failure time impact: none yet
24 mindark → back
You knew first — with proof.03:36
Spotted on a 30-second check, confirmed by two more regions seven seconds later, acknowledged within six minutes. Every ping from the outage is saved with the incident.
on-call paged 7 s lateracknowledged straight from the alertevery check keptSlack · SMS · PagerDuty and 9 more
And without monitoring? A gateway that stops answering doesn't email you. You find out when users start timing out — with no latency history, no record of the checkpoints that lost it, and no idea when it began. no evidence

Ping anything with an IP address

Servers, routers, firewalls, VPN endpoints, load balancers, IoT and network appliances — anything that answers ICMP echo — and a TCP check for anything that doesn't.

Servers & bare hostsReachable, and how fast
Routers & gatewaysThe edge between you and them
Firewalls & VPN endpointsPerimeters and tunnels
ICMP or TCP pingEcho, or a handshake when it's blocked
171+ checkpoints pinging every host you run
CDN & load-balancer edgesEvery POP, from every region
IoT & network appliancesNAS, printers, sensors, PLCs
Game & voice serversWhere latency is the product
Alerts fire on what actually went wrong: a host gone unreachable, or one answering slower than the timeout you set — never on one checkpoint's missed reply. not just down

Confirmation, paging and diagnostics

False-alarm protection

Paged when several regions agree

A single dropped packet at one checkpoint never pages you. Uptimia re-pings from other regions, and only a host unreachable from several of them opens an incident. Recovery is fail-safe: one clean reply clears it.

  • Confirmation you set — 1 to 3 independent regions must miss it, default 3
  • One outage, one page — however many checkpoints miss the host, a single incident opens
  • Your alert delay — set how long a host must stay unreachable before anyone is paged
How outage confirmation works →
🇮🇳Mumbaiap-mum · 03:12:09unreachable
🇧🇷São Paulosa-sao · 03:12:12no reply
🇦🇺Sydneyap-syd · 03:12:14timeout
3 / 3regions
agree
Incident opened03:12:16
Alert sent 7 s after the first drop — confirmed real, not one lost packet.
SlackEmailSMSPagerDuty
Only one region misses a ping? Re-checked and dismissed — one lost packet never pages you. no alert
Alerting

The on-call responder knows in seconds

A confirmed outage reaches the channels your team already watches. If no one responds, the ladder brings in the next on-call, and a recovery notice ends it.

  • Escalation ladders that climb to the next responder until someone acknowledges — no login
  • Maintenance windows and pause — a scheduled reboot never wakes the on-call
  • Recovery notice carrying the total downtime once the host answers again
Alerting & escalations docs →
Down confirmed03:12:16
gw1.caldmont.com — paged the instant three regions agreed it was gone.
SlackEmailSMSPagerDuty+ Teams, WhatsApp…
1
First on-call
paged 03:12:16 · Slack, SMS and email
unacknowledged
5 minutes later the ladder climbs
2
Second on-call
acknowledged 03:18:04 · one tap, no login
MTTA 6 m
step 3
3
Engineering lead
never paged — the incident never climbed this far
Back up 03:36:08 — a recovery notice with the total downtime goes to the same channels. Loop closed. down 24 m
Diagnostics

What the failing probes recorded

Each incident keeps exactly what the failing probes recorded — the round-trip times, the error each one came back with, and the path the echoes took — so you debug from data, not by trying to reproduce it at 3 a.m.

  • Round-trip time on every check — stamped with the checkpoint that ran it, right up to the one that failed
  • The probe's own response — the error text it recorded at the moment the host went quiet
  • Traceroute to the host — the hop where the echoes stopped, ready to hand over as PDF, HTML or a link
Incident evidence docs →
DOWNIncident #5207
gw1.caldmont.com · Sydney · 03:12:14 UTC
03:10:4424 ms
03:11:1427 ms
03:11:4471 ms
03:12:14timeout
03:12:44no reply
Confirmed by
3/3regions agreed
Round-trip time 
03:11:44   71 ms
03:12:14   timeout
03:12:44   no reply
Traceroute 
7   be-2.syd     9 ms
12  ae-1.lax   148 ms
15  * * *      lost
The whole incident is portable — save it as PDF or HTML, or hand a colleague a public link that needs no Uptimia account. 1 click
Global network

Pinged from 171+ locations in 70+ countries

Probes on six continents reveal a machine that answers instantly in Los Angeles and not at all in Sydney — a routing or peering fault that only hurts some of your users. Run the full fleet, or narrow it to the regions you care about.

  • Pings as often as every 30 seconds — a flapping link can't hide between checks
  • Round-trip time per checkpoint — every check is stamped with the probe that ran it, and the log filters by country
  • Probe IPs are published — one firewall allow-list covers every location
See all monitoring locations →
gw1.caldmont.comrotating across every region · 11:26 UTC
🇺🇸 Los Angeles
reply · 11 ms
🇦🇺 Sydney
no reply
🇧🇷 São Paulo
reply · 148 ms
+ 168 more
probes worldwide
Never fewer than six probes ping a host — one checkpoint's bad route can't fake an outage. min 6

Give us a hostname.Hear it from us, not from a support ticket.

ICMP and TCP checks, every region, every alert channel — free for 30 days, and none of it is a paid add-on.

Try it free for 30 days →
30 days free no credit card cancel anytime

How ping monitoring works

Live in under a minute — nothing to install; the pings come from our own probe fleet.

Step 120 seconds

Point it at a host or IP

Pick an ICMP ping or a TCP check; frequency and locations come pre-filled — change anything, or nothing.

Host or IP
gw1.caldmont.com
ICMP · replies from us-west in 11 ms
Check frequency
Every 30 seconds
Probe set
All regions · 171+
Step 220 seconds

Pick who gets paged

Add channels and people — escalation ladders and quiet hours come later if you want them.

Send alerts via
EmailSlackSMSWhatsApp+ PagerDuty, Teams, Telegram…
Alert when
Unreachable · agreed by 3 regions
CancelStart pinging →
Step 3automatic

Get paged in seconds

A confirmed outage opens a single incident and alerts every channel you chose.

#ops-alerts
Uptimia 03:12
⚠ Down — gw1.caldmont.com
no reply to ICMP echoconfirmed from 3 regions03:12:16 UTC
Also sent to EmailSMSPagerDuty

Also included

Full REST API

Create, pause and clone ping monitors straight from CI or scripts, with per-user API keys.

POST /api/v2/uptime → 201 · interval: 30s · locations: all

When ICMP is blocked

Point a TCP check at a port instead — same reachability and timing, no ICMP needed.

ICMP filtered → TCP :443 check

Scheduled reports

Reachability and latency summaries, wearing your logo and palette.

DailyWeeklyMonthly

Public status pages

Show the world your network is healthy, and speak up when it isn't.

public · live status · incident updates

Maintenance windows

A scheduled reboot never wakes the on-call.

Sat 01:00–02:00 · alerts silenced

Every monitor type in one account

Ping monitors sit beside uptime, SSL, port, DNS and heartbeat checks — same contacts, groups and roles.

www.caldmont.comUPTIME gw1.caldmont.comPING db-backup · nightlyHEARTBEAT

Paged where your team already works

The same contacts and channels you already use for your websites, pointed at your network gear.

On-call & escalation
PagerDuty Webhooks Twilio
Direct
Email SMS

Twelve destinations, one contact list. Set it up once; every monitor you create draws on it.

Browse the full integrations directory →
03:12 · incident opened — gw1.caldmont.com · no reply
#ops-alertsSlack
⚠ Down — gw1.caldmont.com
request timed outconfirmed 3/3 regionsAcknowledge ↩
+371 ··· 4082SMS
Uptimia: UNREACHABLE gw1.caldmont.com. No reply to ICMP echo, confirmed from 3 regions at 03:12 UTC.
InboxEmail
⚠ Unreachable — gw1.caldmont.com · no reply to ping
Confirmed from São Paulo, Sydney and Mumbai at 03:12:16 · acknowledge in a single tap…
ProductionPagerDuty
TRIGGEREDUnreachable — gw1.caldmont.com
assigned to on-call · via Uptimia integration

What is ping monitoring?

Ping monitoring is an automated service that repeatedly sends ICMP echo requests to a host and records whether it replies and how fast — typically every 30 seconds to a few minutes, from probes spread around the world. The moment a host stops answering, it alerts you by email, SMS or chat, so an unreachable machine is caught long before your users trip over it.

While everything works

How does ping monitoring work?

Uptimia
171+ checkpoints
ICMP echo · every 30 s
Your host
reply · 11 ms

Each check records the round-trip time from the checkpoint that ran it, building the latency history you can chart and compare.

When a check fails

Confirm first, then alert

Your host
no ICMP reply
re-checked · 3 regions
Uptimia
opens the incident

agreed by 3 of 3 regions → incident opened, alerts sent

Reading the numbers

What counts as a good ping time?

Round-trip time is measured in milliseconds — the lower and steadier, the better. Jitter (how much it varies) and packet loss matter as much as the average.

Guide: what is a good ping time? →
Round-tripHow it feelsTypical case
< 20 msInstantSame city or region
20–50 msExcellentSame continent
50–100 msGoodCross-continent
100–200 msNoticeable lagIntercontinental
> 200 msSluggishFar region, congestion or satellite

Ping monitoring FAQ

01What is ping monitoring?+
An automated service that continuously sends ICMP echo requests to a host from outside your network and alerts you the moment it stops replying. Uptimia pings from 171+ locations across 70+ countries, as often as every 30 seconds, and agrees an unreachable host across several regions before it pages anyone.
02How does ping monitoring work?+
Each check sends an ICMP echo to the host from one of your chosen checkpoints and records the round-trip time it came back in. A host that stops answering from one region is re-pinged from others; only an agreed failure opens an incident, and the first clean reply closes it.
03What is the difference between ping monitoring and uptime (HTTP) monitoring?+
Ping (ICMP) proves the machine is on the network and how fast it answers. An HTTP or port check proves a specific service on it is actually working. A host can reply to ping perfectly while its web server, database or VPN is dead — so ping is the reachability and latency layer beneath your service checks, not a replacement for them.
04What can I monitor with a ping check?+
Anything with an IP address that answers ICMP: servers and bare hosts, routers, firewalls, VPN endpoints, load balancers and CDN edges, NAS and other network appliances, IoT devices, and game or voice servers where latency is the product. When a host filters ICMP, point a TCP check at one of its ports instead.
05What if the host blocks ICMP ping?+
Many hosts silently drop ICMP while answering TCP fine. When that happens, switch the monitor from Ping to TCP: Uptimia opens a connection to a port you name (say 443) and times the handshake instead, so you still get reachability and latency without relying on ICMP.
06Can it catch a link degrading, not just a full outage?+
Partly, and it is worth being precise about which part. Every check records the round-trip time from the checkpoint that ran it, so a link that is slowing down shows up in the response-time history and in the per-check log well before it fails outright. The alert itself fires on unreachable — a host answering slower than the timeout you set counts as down. A ping monitor does not chart a packet-loss percentage; for a one-off loss and jitter reading on a host, the free Ping Test tool sends a burst and reports both.
07What is a good ping time?+
It depends on distance. Under 20 ms is same-region and feels instant; 20–50 ms is excellent within a continent; 50–100 ms is normal cross-continent; over 200 ms starts to feel sluggish. Steady is as important as low — rising jitter and packet loss matter as much as the average.
08How do you prevent false alarms?+
Every host is pinged from at least 6 probes, and a suspected outage is re-tested from up to 3 independent regions before any alert — one dropped packet on one route can't page you. Recovery is fail-safe: a single clean reply brings the host back.
09How do I get alerted when a host goes unreachable?+
Through 12 channels: email, SMS, Slack, Microsoft Teams, Discord, Mattermost, Telegram, WhatsApp, PagerDuty, Twilio, webhooks and Atlassian Statuspage. When the first responder stays silent, the ladder moves on to the next one, and an acknowledgement takes a single tap on a signed link — no sign-in at all.
10Is there a free plan?+
Yes — the free plan pings one host every 5 minutes, no card needed, and commercial use is fine. The 30-day trial opens everything up with headroom for 500 monitors. You can also fire off a single check right now using our free Ping Test tool.
11Can I ping a host inside my own network?+
Not with a ping monitor — the echoes come from Uptimia's public probes, so they can only reach a host that has a route from the internet. That is the point for anything customer- or partner-facing: you see the gateway the way the outside world sees it. For a machine with no public route, Uptimia Server Monitoring runs a small agent inside your network and reports from there instead.
12Which plans include ping monitoring?+
Every plan, including the free one — ping and TCP checks are part of the uptime monitor family, never a paid add-on. The free plan pings one host every 5 minutes; paid plans raise the count (10 monitors on Basic, 100 on Professional, up to 1,000) and Professional unlocks 30-second intervals. The free 30-day trial opens the full platform with room for 500 monitors, no credit card.

Start watching your hosts today.

Give us a hostname or an IP and choose your channels — you will know the moment it stops answering.

Ping a host →
30-day free trial 500 monitors on the trial No credit card EU-hosted, GDPR-ready
ICMP and TCP ping checks ship with every Uptimia plan, the free one too.