Monitors

Uptime checks from multiple regions, with a clear down rule

HTTP, keyword, ping, TCP, DNS, SSL, and heartbeat checks. Free checks every 30 seconds from up to 3 regions; paid plans go down to 10 seconds and up to 6 regions. An incident opens when at least two regions agree the target is down — not when one probe fails.

Website and API checks

HTTP and HTTPS monitoring with status codes, response-body and latency assertions, plus keyword, ping, TCP, DNS, SSL expiry, and heartbeat checks.

Multiple regions

Six regions worldwide. Each monitor checks from up to six of them (three on the free plan), and at least two must agree before anyone is paged.

Consensus alerts

An incident opens only when at least two of the checked regions agree your target is down in the same round. Included on every plan, free included.

Dev-first

A clean dashboard plus a REST API, CLI, and MCP so you can manage monitors from code, the terminal, or agents.

Setup

Set it up in a minute. Edit it anytime.

A monitor is just configuration. Name it, pick what to check, and choose where it runs. Change any of it later without starting over.

Point it at a target
Add a URL, host, or heartbeat. HTTP checks can assert on status codes, response body, headers, and latency — so a soft 200 that still means broken can page you.
Choose your regions
Run every check from up to six regions worldwide (three on the free plan). Heartbeats are passive check-ins and do not need a region quorum.
Consensus, by default
Every multi-region monitor opens an incident only when at least two of the checked regions agree the target is down in the same round. No extra setup — that is the default.
Edit it anytime
Interval, regions, and what you check are all editable later. Nothing is recreated, so the monitor keeps its history.

FAQ

Uptime monitoring, answered

What teams ask before they point their website and API monitoring at Tallwatch.

Go deeper on how Tallwatch monitors

The thinking behind consensus alerts, multi-region checks, and running uptime monitoring for free.

Multi-region consensus monitoring

How Tallwatch pages only when at least two regions agree a check failed.

What Tallwatch is and how uptime monitoring works

A plain-language tour of consensus monitoring for websites and APIs.

Multi-region monitoring, explained

Why checking from several regions at once turns flaky alerts into real ones.

Free uptime monitoring you can run in production

What the free plan covers and why it is built for real projects.

Documentation

Setup guides

Step-by-step docs on docs.tallwatch.com for this part of the product.

Monitors overview

How Tallwatch checks work and how to configure them.

Monitor types

Check types Tallwatch offers and how each is evaluated.

Creating monitors

HTTP setup: assertions, regions, intervals, testing, and pausing.

Monitor dependencies

Suppress downstream pages when an upstream monitor is already down.

Maintenance windows

Schedule planned downtime so deploys do not open incidents.

A page after regions agree — not after one probe fails.

Start on Free with multi-region consensus. No credit card.

Start free

Agent

Page as markdown

Raw agent-readable copy for this route. Copy it into a model, or browse the site-wide agent index at /llms.txt.

---
title: "Monitors"
description: "HTTP and HTTPS checks from multiple regions every minute, with consensus before incidents."
canonical: https://tallwatch.com/services/monitors
url: https://tallwatch.com/services/monitors
llms_url: https://tallwatch.com/llms.txt
updated: 2026-09-02
---
Monitors

# Uptime checks from multiple regions, with a clear down rule

## Website and API checks

HTTP and HTTPS monitoring with status codes, response-body and latency assertions, plus keyword, ping, TCP, DNS, SSL expiry, and heartbeat checks.

## Multiple regions

Six regions worldwide. Each monitor checks from up to six of them (three on the free plan), and at least two must agree before anyone is paged.

## Consensus alerts

An incident opens only when at least two of the checked regions agree your target is down in the same round. Included on every plan, free included.

## Dev-first

A clean dashboard plus a REST API, CLI, and MCP so you can manage monitors from code, the terminal, or agents.

Setup
## Set it up in a minute. Edit it anytime.

A monitor is just configuration. Name it, pick what to check, and choose where it runs. Change any of it later without starting over.

1. **Point it at a target** — Add a URL, host, or heartbeat. HTTP checks can assert on status codes, response body, headers, and latency — so a soft 200 that still means broken can page you.

2. **Choose your regions** — Run every check from up to six regions worldwide (three on the free plan). Heartbeats are passive check-ins and do not need a region quorum.

3. **Consensus, by default** — Every multi-region monitor opens an incident only when at least two of the checked regions agree the target is down in the same round. No extra setup — that is the default.

4. **Edit it anytime** — Interval, regions, and what you check are all editable later. Nothing is recreated, so the monitor keeps its history.

FAQ
## Uptime monitoring, answered

What teams ask before they point their website and API monitoring at Tallwatch.

### What is uptime monitoring?

Uptime monitoring repeatedly checks whether your website or API is reachable and responding the way you expect, then alerts you when it is not. Tallwatch runs those checks from multiple regions — every 30 seconds on Free, as often as every 10 seconds on paid.

### How does Tallwatch decide my site is down?

Each round, Tallwatch checks your target from several regions at once. An incident opens only when at least two of the checked regions agree the target is down in the same round. That keeps a single flaky path from opening an incident on its own. Consensus runs on every plan, including Free.

### How often does Tallwatch check my site?

Free monitors check every 30 seconds. Pro and Business can check as often as every 10 seconds. Heartbeats follow the interval you configure for the job.

### Which regions does Tallwatch check from?

There are six regions worldwide: Frankfurt, Ashburn, Hillsboro, Singapore, Sydney, and São Paulo. A monitor can check from up to six of them; monitors on the free plan check from three. Per-region response time is recorded and charted so you can see where things slowed down.

### Can I monitor an API?

Yes. Point a monitor at any HTTP or HTTPS endpoint. Each round checks the status code and, if you want, body content, JSON paths, headers, or latency thresholds — so a 200 that still means broken can count as down.

### What check types does Tallwatch support?

HTTP/HTTPS (with optional content and latency assertions), keyword, ping, TCP/port, DNS, SSL certificate expiry, and heartbeats for cron jobs and workers.

### Can I monitor a cron job or background worker?

Yes. Heartbeat monitors expect a scheduled job to check in on an interval you set. If the check-in does not arrive within the grace period, Tallwatch alerts you that the job did not run.

### What does the free plan include?

Free is $0 with no credit card and is allowed for commercial use. It covers up to 10 monitors with multi-region consensus across three regions and 30-second checks, so you can run real uptime monitoring for production without a trial clock.

### What happens during planned maintenance?

Maintenance windows suppress alerts during planned work, so deploys or scheduled downtime do not page your on-call. When the window ends, normal alerting resumes automatically.

Related reading
## Go deeper on how Tallwatch monitors

The thinking behind consensus alerts, multi-region checks, and running uptime monitoring for free.

- [Multi-region consensus monitoring](https://tallwatch.com/consensus-monitoring): How Tallwatch pages only when at least two regions agree a check failed.
- [What Tallwatch is and how uptime monitoring works](https://tallwatch.com/blog/what-is-tallwatch): A plain-language tour of consensus monitoring for websites and APIs.
- [Multi-region monitoring, explained](https://tallwatch.com/blog/multi-region-monitoring-explained): Why checking from several regions at once turns flaky alerts into real ones.
- [Free uptime monitoring you can run in production](https://tallwatch.com/blog/free-uptime-monitoring-for-production): What the free plan covers and why it is built for real projects.