First monitor
Add an HTTP, ping, or port monitor and watch your first check pass.
Monitor types
| Type | What it checks |
|---|---|
| HTTP / HTTPS | URL availability, status code, response body, SSL certificate |
| Ping (ICMP) | Host reachability via ICMP ping |
| Port (TCP) | Whether a TCP port accepts connections |
This guide uses HTTP — the most common type. The steps for ping and port monitors are nearly identical.
Create an HTTP monitor
- In the sidebar, click Monitors.
- Click + New Monitor and select HTTP / HTTPS.
- Fill in the required fields:
Name: Production API
URL: https://api.example.com/health
Check interval: 60s (Free tier minimum)
Expected status: 2xx (default)
- Click Save.
The first check runs within a few seconds. You should see the status indicator turn green if the endpoint responds with a 2xx status.
Optional: keyword check
If your endpoint can return HTTP 200 with an error body (common with some frameworks), add a keyword check:
- In the Advanced section, find Keyword check.
- Enter a string that must appear in the response body — for example,
"status":"ok". - If the keyword is absent, the check fails even if the HTTP status is 2xx.
Optional: SSL monitoring
For HTTPS monitors, enable SSL certificate monitoring to receive alerts before your certificate expires:
- Enable SSL monitoring in the Advanced section.
- Set warning thresholds (default: warn at 30 days, critical at 7 days).
Alert threshold
The alert threshold controls how many consecutive failures must occur before an incident is opened:
- 1 (default) — alert on first failure. Best for critical production endpoints.
- 2–3 — wait for N consecutive failures. Reduces alert fatigue from transient network blips.
Prober regions
By default, checks run from the EU West region. On Premium+ plans you can add additional prober regions (EU East, US East, US West) so checks run in parallel from multiple locations:
- All regions fail → monitor status: Down
- Some regions fail → monitor status: Degraded
See Concepts: Monitors for a full explanation of regions and degraded state.
Verify the monitor is working
After saving, the monitor list shows:
- Status — Up / Down / Degraded
- Last check — timestamp of the most recent check
- Response time — latest measured latency
- Uptime % — rolling 30-day figure
Click the monitor name to open the detail page with a 30-day uptime chart and incident history.
What's next
- First heartbeat — monitor cron jobs and background workers
- First status page — publish uptime data publicly
- Concepts: Monitors — deep dive into all monitor options
Was this page helpful?