Uptime¶
Uptime monitoring is a lightweight "is it up?" check, separate from screenshot Monitors — it checks that a URL responds correctly, not whether it looks different. Set it up from the Uptime tab.
Creating uptime monitors¶
The fastest way to set up uptime checks: pick the languages and pages you want covered, and one monitor is created for every combination that isn't already being checked. You can also add a single custom-path monitor for a URL that isn't one of your saved pages.
| Field | What it means |
|---|---|
| Languages × Pages | Every combination becomes its own monitor. |
| Check interval | How often to check — options depend on your plan (faster plans check more often). |
| Custom path (optional) | A specific URL to check that isn't one of your pages. |
Uptime checks always target your Production environment/domain — you can't point one at staging or a different domain.
Uptime checks come from a single, fixed source IP and user-agent (
Localization-QA-Uptime/1.0). If your site has a firewall or bot-blocking rule that might catch this, allowlist it — otherwise checks may report false failures. See Allowlisting VisualRunner Traffic for the current IP and per-platform instructions, or contact support to get it.This is true even if you use a Private Runner: a Private Runner delivers screenshot captures and screenshot Monitors, not uptime checks. Uptime checks always run from VisualRunner's platform, so an internal URL a Private Runner can reach still can't be uptime-monitored unless VisualRunner's IP is allowlisted to reach it directly.
Your plan limits how many uptime monitors your workspace can have in total (across every project), and sets a minimum check interval.
Reading status¶
| Status | Meaning |
|---|---|
| Pending | Just created, hasn't checked yet. |
| Up | Responding normally. |
| Down | Failed enough consecutive checks in a row to be considered actually down (a single blip doesn't flip this). |
| Recovering | Was down, has started passing checks again, but not yet enough in a row to confirm recovery. |
| Paused | You've turned it off. |
| Blocked by site | The site refused the check (HTTP 403 or 429), usually bot protection blocking our IP. The site may well be up, so no incident or alert is raised. |
Each monitor shows its last HTTP status, last response time, and — if it failed — a plain-language reason (SSL problem, DNS failure, timeout, connection refused, unexpected redirect, or unknown).
If a monitor shows Blocked by site, allowlist our IP on the site, or send the environment's checks through your own proxy.
SSL certificate expiry¶
If SSL monitoring is on for a monitor (the default), you'll get a warning email as the certificate approaches expiry — at 30, 14, 7, 3, and 1 day(s) out. Each threshold only emails once, so renewing early won't spam you with repeat warnings for the same certificate.
Alerts¶
Turn on any of: email when it goes down, email when it recovers, email on an SSL warning. Unlike screenshot Monitor notifications, uptime alerts are sent immediately per event — there's no daily/weekly digest option for uptime.
Managing a monitor¶
Check now runs an immediate check outside its schedule. Pause/Resume stops or restarts checking without deleting it. Remove deletes the monitor along with its check and incident history — this can't be undone.