Uptime monitors

Uptime monitors check your sites and services from our own infrastructure, independently of the servers they run on.

• HTTP — expects a 2xx/3xx status (or one exact status code you pick).
• Keyword — like HTTP, but also requires a piece of text in the response body (first 256 KB).
• TCP — opens a connection to host:port, for databases and other non-HTTP services.

Creating a monitor

Open Monitors → Add monitor, or use the Add monitor shortcut on a service page (the URL is prefilled). Pick an interval of 1, 3, 5 or 10 minutes and an optional linked service.

Targets must be reachable from the internet: we resolve the host and refuse private, loopback, link-local, CGNAT and cloud-metadata addresses, and we re-validate every redirect hop (at most 3). You can monitor any public URL — it does not have to run on WeServer.

How status is decided

• A monitor is marked down only after two consecutive failed checks, so one network blip does not page you.
• It is up again on the first successful check.
• While down we open an incident on your status page (if the monitor is shown there), send alerts to your notification channels and email you; the same happens when it recovers. Add the Monitor down and Monitor recovered events under Settings → Notifications.

What you see

The monitor list shows uptime for the last 24 hours and 30 days plus average latency. The detail page adds a latency sparkline, a 30-day bar per day, and the last 50 checks. Check history is kept for 30 days.

You can have up to 20 monitors per account.