Uptime monitors

An uptime monitor performs an HTTPS request against the URL you provide on a recurring interval, records the response, and alerts you when the site is unreachable, slow, or returns an unexpected status code.

Quick setup

1. Go to Add uptime check.
2. Enter the URL (must start with http:// or https://) and a friendly name.
3. Pick an interval: 1, 5, 10, 15, 30, or 60 minutes. (Free plan: 5 minutes minimum.)
4. Choose an importance level — high, medium, or low.
5. Set Consider down after (timeout in seconds) and Alert after (consecutive failures before we email you).
6. Save. The first check runs within one interval.

How it works

Each check fires a single HTTPS GET (with redirects followed) and records the response status, content length, response time, and any SSL validation result. When a check fails consecutively for the number of times you set in Alert after, we email you and push to any active notification channels.

Recovery alerts fire automatically the first time the site returns 2xx after a string of failures. The default Resend alert interval is 30 minutes — change it on the monitor's edit page if you want repeat alerts to be more or less frequent.

Monitoring zones

Checks run from ViewPeek's own monitoring probes in multiple regions — currently Europe and North America, with more regions on the way. On the monitor's add/edit page you choose which zones check it.

When a monitor is checked from two or more zones, an outage must be confirmed from a second region before we alert you. A transient network blip between one region and your server no longer wakes you up at 3am — only outages the rest of the world can see do.

• Automatic (default): we check from every region we operate, and you get confirmed alerting with no configuration. This is the right choice for almost everyone.
• Explicit selection: paid plans can pin specific zones — useful when your audience is regional or your firewall only admits certain geographies. Selecting a single zone disables cross-region confirmation for that monitor: alerts fire on that region's view alone.

Each result records which zone observed it, so your SLA reports can state "verified from Europe and North America" — a claim your customers can trust more than a single-vantage number.

Alert recipients

By default, alerts go to the monitor owner. From the edit page you can add additional users from your team. Each user receives the alert email; if you've set up notification channels at the team level, those fire too.

Plan limits

The monitor count includes uptime + SSL + active ping monitors together. Sitemap monitors count separately. Need more than Pro? Contact us for a custom plan.

Troubleshooting

I added the monitor but it shows "no result yet." The first check fires within one interval — give it up to your configured interval before assuming something's wrong.

I'm getting too many alert emails. Widen Resend alert on the monitor (default 30 minutes). Or pause it for an hour or a day. ViewPeek will also auto-pause any monitor that fires 5+ alerts in 60 minutes as a safety net.

The site looks up to me but ViewPeek says it's down. Check the Last result details — the most common cause is a firewall, WAF, or bot filter blocking our monitoring probes (they connect from cloud IP ranges in Europe and North America, which some bot filters treat as suspicious), or a self-signed certificate that fails validation. Allowlist ViewPeek's monitoring traffic in your bot filter, or for staging endpoints behind a non-public cert, switch to a ping monitor on the host instead.

Next steps

• Route alerts to Slack instead of (or alongside) email.
• Pause this monitor when you push a planned deploy.
• Add an SSL monitor for the same domain to catch cert expiry.
• Generate an SLA report from the uptime data this monitor records.