Skip to main content
A monitor is one thing to watch: a URL, a host and port, a hostname, a certificate, an ICMP target, or a heartbeat from your job. Tallwatch checks it from each region you pick and opens an when enough of those regions agree it is down in the same probe round. Default quorum is two. Confirmation is across regions, not across time. Create one from .

​
How it works

Non-heartbeat monitors need at least three regions. You choose from six region labels (Free is capped at three). In each probe round, those regions check the target independently. An incident opens only when the quorum agrees the check failed in that round. Heartbeat is the other direction: your job pings Tallwatch, and you get an alert when a ping is later than interval plus grace. Interval on the form is 10s to 1h. Free can use 30s; Pro/Business can use 10s.

Monitor types

HTTP, TCP, DNS, SSL, Ping, Heartbeat, and legacy Keyword.

Creating monitors

URL, assertions, regions, interval, test, pause.

Check logs

Per-check history: region, latency phases, failure headers and body.

Maintenance windows

Planned downtime without incidents.

​
After you create one

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). The Logs tab lists each probe result (status, region, phases, and failure detail). Pause keeps that history but stops checks. Pause can undo.