WatchFor
Monitors

Monitors overview

What a monitor is, how checks run, and the statuses you'll see.

A monitor is one thing you want to keep healthy. You give it a type and a target, choose how often to check, and WatchFor takes it from there.

Anatomy of a monitor

SettingWhat it does
TypeHow the target is checked — HTTP, DNS, SSL, ping, and 20+ more.
TargetWhat's checked — a URL, hostname, IP, or address, depending on type.
FrequencyHow often a check runs. Higher frequency = faster detection; the options available depend on your plan.
LocationsThe global vantage points checks run from. Checking from many places avoids false alarms from a single bad network.
Alert rulesWhat counts as a problem — see Alerting.

How checks run

Each check is one probe from one location. WatchFor runs them on your schedule from multiple regions. Before an incident opens, a failure is confirmed by several locations — so one flaky route never pages you. (More on this in How incidents work.)

By default checks use IPv4; many types let you choose IPv6.

Monitor statuses

🟢 Up

Latest checks are passing.

🟠 Degraded

A check failed, but it isn't (yet) a confirmed incident.

🔴 Down

A confirmed incident is open for this monitor.

⏸️ Paused

You stopped checks; nothing is being tested.

⚪ Unknown

No results yet (a brand-new monitor).

A single failed check shows as Degraded, not Down. "Down" is reserved for a confirmed incident, so the dashboard reflects real outages — not momentary blips.

Monitor types

WatchFor supports over 20 check types. Browse them by category:

Pausing, tags and maintenance

  • Pause / resume a monitor any time — checks stop and no alerts fire.
  • Tags group and filter monitors (in bulk, too).
  • Maintenance windows suppress alerts during planned work so your uptime isn't dinged.

On this page