Tallwatch
tallwatch.com
- Free plan
- Windows
- macOS
- Linux
- Web
- API
What Tallwatch is
Tallwatch monitors websites and APIs from several regions, opening an incident when at least two regions report the same failure during a check round. Checks cover HTTP, keyword, ping, TCP, DNS, SSL, and heartbeat, with probes listed in Virginia, Frankfurt, Singapore, Sydney, São Paulo, and Oregon. Alerts can go to email, Slack, Microsoft Teams, Telegram, Discord, PagerDuty, or signed webhooks. On-call rotations and escalation policies route incidents to responders until acknowledged. Status pages can be public or private, use a custom domain, and include incident history and email or RSS subscribers. Developers can manage monitors and triage incidents through a REST API, CLI, or hosted MCP endpoint. The free plan includes 10 monitors and 60-second checks from three regions. Pro is $11.99 a month billed annually, or $14.99/month billed monthly; Business is $19.99 a month billed annually, or $24.99/month billed monthly. Tallwatch says it does not currently publish a formal customer uptime SLA with automatic credits.
Who it suits
Tallwatch suits teams that need multi-region website or API checks, incident routing, and status pages. Its API, CLI, and hosted MCP endpoint also serve developers managing monitors and triaging incidents.
Good to know, and what to watch
- Free plan includes 10 monitors.
- Checks include SSL and heartbeat.
- Status pages support custom domains and subscriber feeds.
- On-call rotations and escalation policies route incidents.
- Free checks run every 60 seconds.
- Free plan checks use 3 regions.
- Tallwatch does not publish a formal customer uptime SLA with automatic credits.
Plans
Every plan and priceFree
Pro
Business
Free plan
The verdict
Tallwatch brings monitoring, alert routing, and status pages together, with region agreement required before an incident opens. The free plan is limited, while paid plans add broader coverage and higher limits.
What the maker publishes
- Alert integrations
- Alert channels include email, Slack, Microsoft Teams, Telegram, Discord, PagerDuty, and signed webhooks. source
- Alert integrations
- Confirmed incidents can be sent to email, Slack, Microsoft Teams, Telegram, Discord, PagerDuty or signed webhooks. source
- Availability commitment
- Tallwatch says it does not currently publish a formal customer uptime SLA with automatic credits. source
- Check types
- It supports HTTP, keyword, ping, TCP, DNS, SSL, and heartbeat checks. source
- Check types
- Supported checks are HTTP/HTTPS, keyword, ping, TCP/port, DNS, SSL-expiry and heartbeat checks. source
- CLI
- The CLI manages monitors and incidents, runs test probes and supports UptimeRobot imports from a terminal. source
- CLI package license
- The public @tallwatch/cli npm package is marked MIT licensed and exposes built-in TypeScript declarations. source
- CLI package version
- The npm listing shows @tallwatch/cli version 0.3.2 with a published package and a repository at github.com/nabinkhair42/tallwatch. source
- CLI platforms
- The CLI can be installed on macOS, Linux, and Windows and can import monitors from UptimeRobot. source
- CLI requirements
- The official installer requires Node.js 20 or newer and supports macOS, Linux and Windows through shell, PowerShell or npm installation. source
- Consensus behavior
- An incident opens when at least two regions report the same failure in one check round. source
- Consensus detection
- An incident opens only when at least two checked regions report the same failure during one check round. source
- Contracts SDK package
- The maker's npm profile lists @tallwatch/contracts as shared Zod schemas and TypeScript types for the Tallwatch REST API. source
- Data deletion
- The privacy policy says users may request early deletion and can also delete their account from settings. source
- Data retention
- The terms state that after termination account data is retained for 90 days to allow reactivation and then permanently deleted. source
- Developer access
- Tallwatch offers a REST API, CLI, and hosted MCP endpoint for managing monitors and triaging incidents. source
- Documentation
- The monitors page links to separate setup guides for monitor types, creation, dependencies and maintenance windows on docs.tallwatch.com. source
- External project description
- Nabin Khair's public portfolio describes Tallwatch as a multi-region service that monitors sites and APIs and alerts the appropriate people. source
- Funding and ownership
- A public post by the maker describes Tallwatch as a bootstrapped, pre-revenue project. source
- GitHub project listing
- The maker's GitHub profile lists Tallwatch as a downtime-monitoring service among his projects. source
- Heartbeat monitoring
- Heartbeat monitors detect missed check-ins from cron jobs and background workers and do not require regional quorum. source
- HTTP monitoring
- HTTP and HTTPS checks can validate status codes, response content, JSON paths, headers and latency. source
- Incident response
- Tallwatch provides on-call rotations and escalation policies that route incidents to responders until acknowledged. source
- Limit: missed-alert liability
- The terms disclaim liability for indirect losses including losses caused by missed or delayed alerts. source
Checked against the maker's pages on 15 Oct 2026.