Skip to main content
A monitor type is the kind of check Tallwatch runs against a target. On create you choose HTTP/Website, TCP, DNS, SSL, Ping (ICMP), or Heartbeat. Each type looks at a different signal: an HTTP response, a TCP connect, a public DNS lookup, a leaf certificate, an ICMP echo, or a ping from your job. Checks run from the regions you select and vote in , except Heartbeat, which is a ping from your job to Tallwatch. An incident opens when enough regions agree the target is down in the same probe round. Default quorum is two.

​
How it works

Pick the type that matches the signal you care about, then set regions and an interval. Non-heartbeat monitors need at least three regions (Free is capped at three). For the HTTP form, assertions, and defaults, see .

​
HTTP / Website

Requests a URL. You set method, accepted status, redirects, timeout, and optional content check, headers, and body. Point the URL at a health endpoint that touches real dependencies, not a static page.

​
TCP

Connects to a host and port.

​
DNS

Resolves a hostname (A, AAAA, CNAME, MX, TXT) via public DNS. This is not a query to your authoritative nameserver.

​
SSL

Inspects the leaf certificate. Expiring soon is degraded (no page). Expired is down.

​
Ping (ICMP)

Sends an ICMP echo request.
If only Ping fails while HTTP works, treat it as ICMP blocked.

​
Heartbeat

Your job hits Tallwatch on a schedule:
You get an alert when a ping is later than interval plus grace. There is no Test action.
Keyword is edit-only for existing monitors. For new content checks, use HTTP with a content check.