Uptime monitoring

When to use Uptime#

Use Uptime for public websites, APIs, health endpoints, checkout paths, login pages, and other HTTP or HTTPS targets where availability and response behavior matter.

Create the monitor#

1. Open Monitors and click New Monitor.
2. Select Uptime.
3. Enter a customer-readable Friendly Label.
4. Enter the URL. Watchfox assumes HTTPS when you enter a domain without a scheme.
5. Choose an interval allowed by the current plan.
6. Leave probe coverage on Automatic.
7. Configure alerting only as strictly as the service requires.
8. Create the monitor and wait for a real check.

Recommended settings#

• Timeout: start with 10000 ms; shorten only when a slower response should count as failure.
• Expected HTTP status: leave empty to accept 200–399.
• First alert delay: use 0 for critical immediate alerting or a short delay to absorb transient failures.
• Repeat reminders: keep Off until the escalation expectation is clear.
• Recovery alert: normally enabled for production monitors.

Expected result#

The monitor detail should show a recent check with state, status code, latency, probe group, and time. A redirect can still be healthy when Expected HTTP status is empty.

Common mistakes#

• Monitoring a login-required URL without understanding the anonymous response.
• Requiring HTTP 200 when the intended target redirects to a canonical URL.
• Using a timeout shorter than the service's normal slow-but-acceptable response time.
• Treating an internal probe-group label as a guaranteed country or region.
• Creating duplicate monitors for the same URL and monitor type in one project.

When an Uptime monitor is Down#

Review the latest non-OK result, HTTP status, final URL, redirect behavior, latency, and whether the issue is current or historical. Then compare the target from another independent connection before changing the monitor. See Troubleshooting by symptom.