Creating and Managing Monitors

Create your first monitor in two minutes; everything you'll touch most often, pause, edit, delete, bulk actions.

A monitor is the unit of work in UptimeWarden. You point it at a target, a URL, a host and port, a domain, and it checks on a schedule. This page walks through creating, editing, pausing, and deleting monitors. For type-specific detail (HTTP, SSL, DNS, gRPC, and the rest), follow the dedicated pages.

Creating your first monitor

From the dashboard pick Monitors → New Monitor:

Choose a type. HTTP for a website or REST API; Ping for raw ICMP reachability; SSL for certificate health; the Monitors overview lists every type with a one-line description of what it's for.
Fill in the target. A URL, a host plus port, or a domain, depending on type. The form validates as you type.
Pick a check interval. How often the check runs. Faster intervals catch outages sooner but consume more of your monitor allowance; the form locks intervals faster than your plan allows behind an upgrade prompt.
Pick a region (or accept the default). Choosing a region is available on Professional (up to 5 regions) and Enterprise (all regions); on other plans the monitor runs from the default region. On Starter and above you can also pick verification regions for multi-location consensus.
Pick notification channels and alarm types. Which channels (email, SMS, WhatsApp, voice, push, webhook, Slack, Telegram) get which alarm types (down, recovery, ssl, high_response, etc.).
Save.

The first check usually completes within a few seconds and the result lands on the monitor's detail page.

The monitor detail page

Open any monitor and you'll see:

Status header: current state (up, down, recovery, or unknown), last check time, latest response time
Uptime chart: rolling uptime percentage over 24h / 7d / 30d
Response-time chart: latency over the same windows
Recent checks: a scrollable list of the last N results with timing and any error text
Incidents: every incident this monitor has triggered, with duration and notification trail
Settings: the same form you saw at creation, editable in place

For the full reference see Monitor Detail.

Editing a monitor

Open the monitor → Settings → change what you need → Save. UptimeWarden picks up the change on the next cycle (under a minute), so you don't need to wait around for old behaviour to expire.

A few changes are worth flagging:

Changing the URL or host is treated as the same monitor: historical data continues against the new target. If that's not what you want, create a new monitor instead.
Changing the region keeps historical data; the breakdown panel labels old checks against their original region.
Changing the interval takes effect immediately; the next check follows the new schedule.
Disabling all alarm types silences notifications but the monitor still records data. Useful for "I want the chart but not the page."

Pausing and resuming

Pausing a monitor stops checks immediately, no data is recorded, no incidents fire. Resume restarts checks on the next check cycle.

Pause is the right tool for:

Planned maintenance you don't want polluting uptime
A monitor someone configured wrong and you're not ready to delete
Decommissioning a service while you keep the monitor for reference

If you find yourself pausing the same monitor on a recurring schedule, consider a Maintenance Window, it suppresses notifications without zeroing out check data.

Deleting a monitor

Delete is permanent, the monitor and its history go away. Your plan's monitor count drops by one. There is no undo, so we ask you to type the monitor's name to confirm.

If you might want the data later, pause instead. Paused monitors still count toward your plan limit, your monitor count only drops when you delete. (On Enterprise the limit is unlimited, so it doesn't matter there.)

Bulk operations

When you select multiple rows on the Monitors page, a sticky toolbar appears with:

Pause / Resume: flip a whole batch at once
Add tag: same tag on the whole selection
Set group: assign to a monitor group
Assign escalation policy: wire to a tiered on-call rotation
Delete: bulk delete (with a confirmation phrase)

Every bulk action lands in the audit log so you have a record of what changed.

Search and filtering

The Monitors page header has a search box and filter dropdowns:

Search matches name, URL/host, and tags simultaneously
Status filter narrows to up / down / recovery / paused
Type filter shows only HTTP, only SSL, etc.
Group filter scopes to one group's monitors
Tag filter scopes to monitors carrying that tag

The URL updates as you filter, so a complex filtered view is shareable as a link.

Sharing monitors with a team

By default, a monitor is private to the user who created it. To share access, add the monitor's owner team to the monitor (or create the monitor under a team in the first place). Team members inherit the team's role: readers see the data, editors can change settings, admins can delete.

For role detail see Roles & Permissions.

Plan limits

Plan	Monitor limit	Minimum interval
Free	20	3 minutes
Hobby	35	2 minutes
Starter	50	2 minutes
Professional	100	1 minute
Enterprise	Unlimited	30 seconds

Reaching your monitor limit blocks new monitor creation until you delete one or upgrade your plan. There's no overage billing.

FAQ

Q: How long does it take for a new monitor to start checking? A: A few seconds. The first result usually appears before you've finished moving to the detail page.

Q: Can I copy an existing monitor? A: Yes, click the Clone Monitor button on the monitor's row in the Monitors list. The new monitor inherits every setting except the name (which gets a (Copy) suffix). Tweak what's different and save.

Q: What happens to a monitor's data when I delete it? A: The monitor row, its check results, and its incidents are removed. If you want the data preserved, pause the monitor instead.

Q: Can I import or export monitors? A: Yes. See Monitoring as Code for a TypeScript/CLI workflow and the Terraform Provider for HCL.