UpDownTracker / How it works
From check to recovery — one clear monitoring flow.
Configure the signal that matters, follow confirmed problems, and keep the history after your service recovers.
- 01
Configure a monitor
Choose a public URL, expected text or a heartbeat interval.
- 02
Scheduled check / heartbeat
The service checks the target, or your task sends its check-in.
- 03
Problem detected
An observation fails or an expected signal is missing.
- 04
Incident confirmed
The monitor’s confirmation rules establish an incident.
- 05
Email alert
Enabled notifications report the confirmed problem.
- 06
Recovery detected
A successful check or resumed signal records recovery.
- 07
Recovery notification
A recovery email closes the notification loop.
- 08
History remains
Review the incident alongside response-time and uptime history.
The right check for the job
Website Monitoring
Monitor availability, response time and downtime.
02API Monitoring
Track public API endpoint availability and latency.
03Keyword Monitoring
Detect when important page content disappears.
04Heartbeat Monitoring
Know when scheduled tasks stop checking in.
A check is an observation, not a guarantee. Confirmation and recovery provide context; the history helps you investigate. Email delivery is retried after failed attempts.
Start monitoring
Know about downtime before your customers do.
Add your first monitor and keep website availability, performance and incident history in one clear place.
7-day Starter trial · No credit card required · Starts with your first monitor