Signal, not noise
Expected HTTP status, bounded timeout, fresh connections and conservative incident confirmation.
UptimeLoop checks public services every 5 minutes, confirms failures twice, tracks expiry dates, and gives users a status page that says what is actually happening.
Expected HTTP status, bounded timeout, fresh connections and conservative incident confirmation.
SSL and best-effort WHOIS expiry checks run daily and preserve the last valid date through transient lookup failures.
Publish selected components, incidents, maintenance windows and 30-day availability without exposing raw infrastructure errors.
UptimeLoop is deliberately smaller than a full observability suite. It answers whether a public service responds, whether a deadline is approaching, and what users should know.
Read the security modelNo synthetic browser, RUM or invented score. The current product focuses on public availability, DNS, SSL, domain expiry, incidents and status pages.
Checks public URLs, follows vetted redirects, measures latency and compares the response with the expected status.
Reads the certificate presented by HTTPS targets and tracks its published validity window separately from availability.
Checks common DNS records and displays a domain-expiry date when the relevant registry publishes one.
Billing is not connected. Early-access workspaces are currently free.