HTTP(S) Monitoring
Check status codes, response time, and expected content on any URL, with configurable timeout and retry rules.
Downtime you find out about first is downtime you control
The real cost of an outage isn't the outage itself — it's the twenty minutes between it starting and someone noticing. CloudStats closes that gap with checks as frequent as every 60 seconds from multiple monitoring locations, so a single network blip doesn't trigger a false alarm, but a real outage reaches you fast.
Ping (ICMP) Monitoring
Classic ping checks for servers and network devices that don't run a web server at all.
TCP Port Monitoring
Monitor any service on any port — mail servers, databases, custom applications, game servers.
Multi-Location Checks
Confirm an outage from more than one geographic location before triggering an alert, cutting down false positives.
Escalation Rules
If the first responder doesn't acknowledge within N minutes, escalate to the next person or channel automatically.
Public Status Pages
Show real-time and historical uptime to your customers on a branded status page.
1. Add the URL, IP, or port you want to monitor.
2. Choose the check interval (as low as 1 minute) and the locations to check from.
3. Define what "down" means for this check — status code, timeout, keyword match.
4. Get alerted immediately when the check fails from multiple locations.
FAQ
Frequently asked questions
How often can CloudStats check my site or server?
As often as every 60 seconds on paid plans, with longer intervals available on the free tier.
What counts as "down"?
You define it — an unexpected HTTP status code, a timeout, a missing keyword in the response, or a failed ping/port check.
Can I monitor internal servers that aren't public?
Yes, using the CloudStats agent for internal/private network monitoring in addition to external checks.
Will a single failed check trigger an alert?
You can require confirmation from a second location before an alert fires, to avoid false alarms from local network issues.