> ## Documentation Index > Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt > Use this file to discover all available pages before exploring further. # Introduction > Set up uptime monitoring, alerts, escalation, on-call, and status pages. Practical guides for every part of Tallwatch. 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 Add HTTP checks, pick regions and intervals, and set assertions, dependencies, and maintenance windows. Acknowledge, resolve, and understand when an alert is held back on purpose. Connect Slack, Discord, Teams, Telegram, email, PagerDuty, or a webhook. Build ordered levels that keep paging until someone acknowledges. Set up rotations, overrides, and who's responsible when. Publish uptime and incident updates on your own domain. 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.