# 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-10-26

---

About monitoring is for anyone who wants to keep an eye on their websites, APIs, servers, DNS and certificates without being a technical expert.

## Overview
- Watches your infrastructure from several regions and confirms a real outage before alerting you, so a single blip doesn't wake you up.
- Tracks incidents automatically with a timeline, and lets you schedule planned maintenance so that work doesn't trigger alerts.
- Routes alerts to the destinations you choose, and can publish a public status page on your own domain.

## What you can watch
1. Websites, APIs and keywords on a page.
2. TCP ports, SSL certificates and DNS records.
3. Ping and cron-style heartbeats.
4. Redirects, and even other companies' status pages.

## Check the Monitoring page
1. Open **Monitors** from the sidebar.
2. Review the list of checks and their current state — Active, Inactive, In maintenance, Silenced, or Not monitored.
3. Use **Filter** or **Search** to find a specific check, and check the **Uptime 24h** column for a quick health snapshot.
4. Select any check to **Open monitor** and see its **Latest checks**, **Latest incidents**, and **Current status**.
5. Select **Add monitor** to create a new check.

> [!NOTE]
> If a monitor shows as down but the site loads fine for you, this usually means the outage is real from another region or has already recovered — see the article on a monitor saying your site is down when it loads for you.

## Route alerts to your team
1. Open **Settings**, then go to **Channels** or **Destinations**.
2. Select **Add resource** or **Attach destination** to connect email, Slack, Telegram, Teams, Discord or a webhook.
3. On a specific monitor, open **Edit monitor** and choose **Choose destinations** under **Notification policy** to control where its alerts go.
4. Select **Save changes** when done.

## Schedule maintenance
1. Open **Maintenance** from the sidebar.
2. Select **Create** to set up a maintenance window.
3. Pick the monitors affected under **What this affects**.
4. Confirm the dates and select **Save**.

> [!TIP]
> Use monitor dependencies (**Dependencies**, **Add parent**, **Add child**) so that when a parent service goes down, InfraNest doesn't send a flood of alerts for everything that depends on it.

## Tips
- Check from **All regions** or a specific one under **Probe regions** to confirm an outage isn't limited to one location.
- Use **Silence alerts** temporarily instead of deleting a monitor if you're doing short-term work on a service.

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

![About monitoring (1)](/media/30cafd8e-d4e0-4608-87bd-3a51059d43b2)

![About monitoring (2)](/media/a88f55f1-ad50-414b-9a70-2781f5f4ff44)

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