How it works
You choose a type, a target, at least three regions (non-heartbeat), and an interval. HTTP can add a body content check after the status check. Test now runs once from Tallwatch so you can confirm the target. It does not run from every region. Pause keeps history but stops checks. Pause can undo.Create a monitor
1
Open the form
Go to . Pick HTTP, TCP, Ping, DNS, SSL, Keyword, or Heartbeat.
2
Set the target
For HTTP, enter the URL. Defaults:
3
Content check
Optional: require the response body to contain (or not contain) a phrase.
Degraded after is a soft latency threshold (visible, does not page like down).
4
Pick regions and interval
Pick at least three regions (Free is capped at three). An incident opens when the quorum agrees (default two). Confirmation is across regions, not across time. Interval is 10s to 1h on the form. Free can run 30s; Pro/Business can run 10s.
5
Route alerts
Attach the monitor on an (create or edit the policy and pick monitors there). A monitor with no policy stays silent.
6
Test now
Test now runs once from Tallwatch, not from every region. Heartbeat has no Test action.
Pause
Pause stops checks and alerts and keeps history. Pause can undo. For a scheduled silence, use a . The monitor page shows response time by region, availability, and incident history. Charts stay near-live: closed 5-minute rollups plus a short live tail from recent probes.Import from UptimeRobot
Go to , or use the CLI (tallwatch import uptimerobot). Upload a getMonitors JSON export. HTTP and keyword monitors create as Tallwatch HTTP checks (three default regions). Ping, port, and heartbeat rows are skipped. Imports stop at your plan monitor cap.