InfraNestInfraNest

Monitors & checks

About monitoring

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

Monitoring keeps an eye on your websites, APIs, servers, DNS, and certificates so you find out about outages before your customers do — built for anyone who needs reliable uptime tracking without managing complex infrastructure themselves.

Overview

  • Watches many kinds of targets: websites, APIs, TCP ports, SSL certificates, DNS records, keywords, redirects, ping, cron heartbeats, and even other companies' status pages.
  • Checks from multiple regions and only flags an outage once enough regions agree, so one flaky location won't wake you up for nothing.
  • Automatically tracks incidents with a timeline, and lets you set up dependencies between monitors to avoid getting flooded with alerts.
  • Lets you schedule maintenance windows so planned work doesn't trigger alerts.
  • Routes alerts to email, Slack, Telegram, Teams, Discord, or a webhook.
  • Can publish a public status page on your own domain.

Check the Monitors page

  1. Open Monitors from the sidebar.
  2. Review the list of checks, each showing its current StatusUp, Down, Degraded performance, In maintenance, or not yet checked — along with its Uptime 24h.
  3. Select Open monitor on any row to see per-region results and its History.
  4. Select Add monitor to create a new check.

NoteA monitor only turns Down after enough regions agree there's a real problem — this avoids false alarms from a single region having a bad moment.

Add a monitor

  1. From the Monitors page, select Add monitor.
  2. Choose what to monitor — for example HTTP / website monitoring, API monitor, Port monitoring, Keyword monitoring, Ping monitor, Redirect monitoring, DNS monitoring, Heartbeat / Cron monitor, or Server metric alert.
  3. Fill in the details for that monitor type, such as the URL to monitor, Hostname, or Check interval.
  4. Adjust Advanced settings if needed, such as Response assertions, Failed checks before alerting, or Also verify SSL certificate.
  5. Select Create monitor to save it.

TipUse Check from with Monitor from multiple regions at once so a single region's hiccup doesn't cause a false alert.

Set up alerts and maintenance

  1. Open a monitor by selecting Open monitor.
  2. Go to Alerts & Dependencies to attach an alert channel — select Attach alert channel and choose where alerts go (email, Slack, Telegram, Teams, Discord, or a webhook).
  3. To prevent alert storms, set up Parent monitors or Child monitors under Dependencies.
  4. To schedule planned work without triggering alerts, use Mark as expected / planned downtime and check Next maintenance or No upcoming maintenance for what's scheduled.
  5. Select Save changes when you're done.

Publish a status page

  1. Go to Status Pages in the sidebar.
  2. Select Add to status page on the monitors you want to make public.
  3. Confirm the name shown as “{name}” for each item.
  4. Open Manage status pages to review layout and which components are visible.
  5. Use Open status page to see how it looks to visitors.

Tips

  • Use Silence alerts temporarily instead of pausing a monitor if you just want to mute notifications for a bit.
  • Check Recent checks and Response time on a monitor's page to spot slow responses before they become outages.

About monitoring (1)

About monitoring (2)

Related articles

Start in seconds

Bring your whole infrastructure into one modern dashboard.

Free plan · No credit card required · Set up in minutes