# About monitoring

> Monitoring watches your websites, APIs, servers, DNS and certificates from several regions, confirms real outages before it alerts you, tracks incidents, and…

Source: https://infranest.io/docs/monitoring
Last updated: 2026-09-06

---

Monitoring keeps an eye on your websites, APIs, servers, DNS and certificates, and lets you know when something goes wrong — this article is for anyone getting started with checks and status tracking in InfraNest.

## Overview

- Watches your infrastructure from several regions and only alerts you once enough regions agree something is actually down, so a single flaky location won't wake you up for nothing.
- Keeps a record of incidents automatically, with a timeline you can review.
- Lets you schedule planned maintenance so expected work doesn't trigger alerts.
- Sends alerts to the destinations you choose, and can publish a public status page for your users.

## What you can monitor

InfraNest can watch many different kinds of targets, including:

1. Websites and APIs (**HTTP / website monitoring**, **API monitor**)
2. Specific ports on a server (**Port monitoring**)
3. SSL certificates, so you're warned before they expire
4. DNS records (**DNS monitoring**)
5. Keywords on a page (**Keyword monitoring**) or redirects (**Redirect monitoring**)
6. Ping checks (**Ping monitor**) and scheduled jobs (**Heartbeat / Cron monitor**)
7. Whole servers (**Server monitoring**)
8. Other companies' status pages, so you know if a provider you depend on is having issues

## Find your checks on the Monitoring page

1. Open **Monitors** from the sidebar.
2. You'll see a list of all your checks along with their current **Status** — **Up**, **Down**, **In maintenance**, **Silenced**, or not yet checked — plus their **Uptime 24h**.
3. Select any check to **Open monitor** and see its per-region results and **History**.
4. To create a new check, select **Add monitor** (or **Add a monitor** / **Create monitor**, depending on where you start from).

> [!NOTE]
An outage is only flagged once enough regions agree, so a single slow or unreachable region won't cause a false alarm.

## Avoid unwanted alerts

1. Set up **Dependencies** between monitors — for example, mark a **Child monitors** relationship — so a single root-cause outage doesn't trigger a storm of separate alerts.
2. Schedule a maintenance window in **Maintenance** and mark it as **Mark as expected / planned downtime**, so planned work doesn't page you.
3. Use **Silence alerts** (with **Silence for** a chosen duration) if you need quiet time without creating a maintenance window.

## Route alerts and publish status

1. Go to **Alerts** or **Notifications** to connect your destinations — email, Slack, Telegram, Teams, Discord, or a webhook.
2. Open **Notification policy** on a monitor to control who gets notified and how.
3. Visit **Status Pages** to **Add to status page** for the checks you want to make public, and publish a status page on your own domain.

> [!TIP]
Open any monitor's **Alerts & Dependencies** tab to review both its alert routing and its dependencies in one place.

<!-- docs-screenshots:start -->

![About monitoring (1)](/media/1f989d89-00ac-42e8-92f4-b78af4552fa9)

![About monitoring (2)](/media/fdc353c5-61ff-447a-964f-8a39e1e4867c)

<!-- docs-screenshots:end -->