Targets and cadence
Active monitors run every 5 minutes. HTTP and HTTPS monitors compare the response with an expected status code. DNS monitors can check A, AAAA, CNAME, MX, TXT and NS records, optionally against an expected value.
Targets must be public. Local, private, reserved and credential-embedded URLs are rejected. Redirect destinations are validated again before a request follows them.
Incident confirmation
A first target failure is not enough to open an automatic incident. UptimeLoop performs a second complete check after at least 10 seconds, using fresh DNS resolution and a new connection. If the target responds on the second check, no incident opens.
Failures identified as monitoring-infrastructure problems are recorded as probe diagnostics. They leave the public service state unchanged and do not count against uptime. Unexpected HTTP responses, target connection refusals and target timeouts remain target failures.
HTTPS and expiry data
HTTPS availability and certificate dates are separate signals. Availability checks whether the public endpoint responds. A daily certificate probe reads the presented certificate and stores its validity dates. This separation avoids treating a local certificate-chain limitation as proof that the target application is unavailable.
Domain expiry is best effort. WHOIS output varies by registry, and some registries publish no usable expiry date. The last valid SSL or domain date is preserved if a later lookup fails transiently.
History and retention
- Detailed checks: 7 days.
- Hourly availability aggregates: 90 days.
- Resolved incidents: 90 days.
- Public component history: 30 days.
Probe failures and checks suppressed by an active maintenance window do not count against availability.
Status pages and operations
A workspace can publish selected monitors on a public status page. Status pages show current component state, 30-day availability, automatic incidents, manual incidents, maintenance windows and updates.
Public email subscriptions are not available. Custom status-page domains, team accounts, two-factor authentication, a public API and online billing are also not represented as available.
Health and release identity
/health/live verifies that the web process is running. /health/ready verifies a short PostgreSQL query. Health responses expose the deployed Git revision when the release supplies it, but no secret.