Skip to main content
Tallwatch watches your sites and APIs from several regions and tells you when they go down. A check has to fail in more than one region before Tallwatch opens an incident, so a single flaky vantage point doesn’t page you at 3am. When something does break, the alert goes wherever you’ve set it to: Slack, email, a webhook, PagerDuty, or an on-call rotation. These docs are task-focused. Each page walks you through setting one thing up in the dashboard. Pick a section below.

​
Set up Tallwatch

Monitors

Add HTTP checks, pick regions and intervals, and set assertions, dependencies, and maintenance windows.

Incidents

Acknowledge, resolve, and understand when an alert is held back on purpose.

Alerts

Connect Slack, Discord, Teams, Telegram, email, PagerDuty, or a webhook.

Escalation policies

Build ordered levels that keep paging until someone acknowledges.

On-call schedules

Set up rotations, overrides, and who’s responsible when.

Status pages

Publish uptime and incident updates on your own domain.

API keys

Drive Tallwatch from scripts, CI, the MCP server, or Terraform with a scoped Bearer key.
Tallwatch is pre-1.0. HTTP/HTTPS, TCP, DNS, and keyword checks run end-to-end today; SSL, ping, and heartbeat are still preview. Where a feature is partial, the page says so instead of implying it’s finished.