Uptime monitoring

Uptime monitoring checks your sites from outside — the way a visitor on the Internet sees them. A control-plane prober dials each target on a schedule and opens an incident when it goes down, then alerts you through the channels you already connected. It is included on the Free plan.

Uptime vs. server monitoring

These answer different questions — keep them separate:

	Server monitoring	Uptime (this page)
Vantage	Inside the box — the agent reads /proc	Outside — synthetic check from the network
Question	”How loaded is the box?” (CPU/RAM/disk)	“Is the site up, from the Internet?”
Catches	High load, full disk, a service down on the box	Whole-box/network outages, DNS/TLS/CDN failures

Note

When a whole VPS goes down, the agent goes down with it — so it can’t report its own site as down. That dead-man case is exactly the one uptime monitoring is built to catch, which is why the check runs from the control plane, not the agent.

Add a monitor

In the dashboard open Uptime and choose Add monitor. Pick a check type:

Type	What it does	Example target
HTTP	Fetches the URL, checks the status code (and optional keyword) and TLS	https://example.com
TCP	Opens a TCP connection to a host and port	example.com:443
ping	ICMP reachability of a host	203.0.113.10

You can point a monitor at any public URL — including sites that aren’t hosted on MZPanel. The prober records the status code, response time, and connection/DNS/TLS errors on each run, and warns early when a TLS certificate is nearing expiry.

Tip

The prober sends a stable User-Agent so you can allowlist it. On boxes MZPanel manages, the agent keeps the prober’s traffic clear of fail2ban and rate limits automatically, so a health check never trips your own defenses.

Incidents & strikes

A single failed check doesn’t page you — a brief network blip on the prober’s side shouldn’t either. The scheduler waits for N consecutive failures (an N-strike confirmation, default 2) before flipping a monitor from up to down and opening an incident. When the target recovers, the incident resolves and is timestamped on the incident timeline.

Each monitor shows recent checks (a tick bar), a response-time sparkline, and an uptime percentage over time.

Alert channels

Incidents are delivered through your account-level alert channels, configured once under Advanced → Integrations → Chat & Alerts (/connect/channels) and reused everywhere — uptime, per-server alerts, backups, and deploys all route to the same connected destinations.

Supported channels:

Channel	How it connects
Email	A recipient address
Telegram	A bot token plus a chat
Slack	An incoming webhook for a channel
Discord	An incoming webhook
MS Teams	A Workflows (Power Automate) webhook
Google Chat	An incoming webhook for a space
Generic webhook	A JSON POST to your own endpoint

Credentials are encrypted at rest; only the last few characters are shown back to you. On a monitor, pick which connected destinations should receive its alerts. If you haven’t connected a channel yet, the picker links you to set one up first.

In progress

Publishing a public status page for your organization is planned but not yet available. Today, uptime data lives in the dashboard.