HTTP uptime monitoring for websites and APIs
Check whether an endpoint responds as expected, how long it takes, and when it becomes unavailable. Keep uptime and response-time history beside the machines and containers behind your service.
| Endpoint | Status | Response | Uptime |
|---|---|---|---|
| api.example.com/health | 200 | 124 ms | 99.98% |
| example.com | 200 | 56 ms | 100% |
| admin.example.com | 503 | 1,840 ms | 98.12% |
What you can monitor
HTTP availability
Set the request method, custom headers, expected status codes and an optional body match. Test the response your application should return instead of treating every response as success.
Latency and history
Inspect response-time and connectivity charts. Uptime bars provide views from 24 hours to 90 days, with available history depending on your plan and when collection began.
State changes
Set success and failure thresholds before an endpoint changes state. Use repeated results to distinguish a brief failed request from a sustained outage.
Set up an HTTP endpoint check
1. Add a host in your dashboard
Create a System Stats account, open the dashboard and add a host with an HTTP or HTTPS URL. Choose an endpoint reachable by the monitoring service, such as your public website or an API health route.
2. Define a successful response
Configure the request method, headers, timeout and expected status codes. For a health endpoint, add a body match when a successful status alone does not prove the application is ready.
3. Choose timing and review results
Select the check interval and success/failure thresholds. After checks run, review the reported state, response times and uptime. Intervals can be as short as 10 seconds, depending on your plan.
Choose the right check for your service
HTTP checks measure an endpoint response, not a full browser page load or a complete user journey. A passing health endpoint does not automatically prove every application feature works.
Checks run from the monitoring service. A private address that is reachable only inside your network will not become reachable merely by installing the machine agent.
ICMP ping and MongoDB connection checks are also available. Use HTTP for response codes and body validation, ping for network reachability, and MongoDB checks for database connectivity.
Free includes 5 host checks. Check intervals, retained history and notifications vary by plan; compare the plan table before choosing how frequently to check each service.
Explore monitoring for your systems
Docker monitoring →
See which containers are running, how much CPU and memory they use, and whether their health checks are passing. System Stats brings Docker and machine metrics into the same dashboard.
Proxmox monitoring →
Keep Proxmox guest state and resource usage beside the machine that runs them. Install statsd on the node to discover virtual machines and LXC containers through the local Proxmox tools.
Linux server monitoring →
Monitor Linux servers, ARM machines and Raspberry Pi from one dashboard. The statsd agent runs as a background service and collects the system metrics you need to investigate resource pressure.
Install the agent and see it all
Free up to 5 machines forever. No credit card. Two minutes from landing here to live metrics streaming in.