Know before they do.
The worst way to learn your site is down is a customer telling you. LogClip probes every site and endpoint around the clock, tells you the moment something breaks, and keeps a public status page honest.
Incidents that open and close on their own.
4 stops, each one a real screen from the console.
Every monitor on one screen
One line per monitor over 24 hours, 7 days or 30, with the incidents marked on it. A card with nothing behind it shows a dash rather than a zero, because missing data and a measured nought are not the same answer.
Opened by a failing check, closed by a passing one
An incident opens itself, goes out to email, Slack or a webhook, and closes itself when the checks go green — keeping the reason and the duration on the record. Degraded is its own state, because answering slowly is not the same as being down.
Ninety days each, on one list
Endpoint, state, uptime and median response time over a strip of daily history — amber notches are the degraded days, so a quarter of behaviour reads in one pass. The monitors that took an incident are the ones carrying notches.
Maintenance, notifications, and a page you can show customers
A maintenance window keeps the probes running and the notifications quiet. Then flip on the public status page — each public monitor's state, 90-day uptime and recent incidents, with URLs and secrets never exposed to it.
Everything under uptime
Probe your sites and endpoints around the clock — status, latency, SSL expiry and incidents — with alerts by email, Slack or webhook and public status pages.
Probes on your interval
A URL, an expected status and how often to check. Every probe records status and response time, and rolls up into the uptime figure.
Fleet at a glance
Monitors up, open incidents, 30-day uptime and p50 latency across the top; operational, degraded, down and paused counted in a ring.
Response time across monitors
One chart with a line per monitor over 24 hours, 7 days or 30, with the incidents drawn on it where they happened — or flip the whole chart to uptime.
Incidents open and close themselves
Down after consecutive failures, degraded when latency holds over threshold, resolved when checks pass again — with the duration logged.
Email, Slack or your own webhook
Incidents go to the addresses you add, falling back to the workspace owners and admins, and to Slack or a webhook if one is connected.
An alarm in the tab
Arm “Page me” and the console sounds for as long as anything is down, until you acknowledge it. The tab has to stay open.
TLS expiry
An HTTPS monitor tracks when its certificate expires alongside its status, so a renewal is never the thing that takes you down.
Ninety-day history
A daily uptime strip and a response-time sparkline on every monitor, with the degraded days notched in amber rather than hidden.
Maintenance windows
Schedule planned work ahead of time: the probes keep running and keep recording, but the incident notifications are held back until it closes.
Public status page
An unauthenticated page with each public monitor's state, 90-day uptime and recent incidents. Private monitors, URLs and secrets never reach it.
Why it matters.
Around-the-clock probes
Continuous checks on every monitor for status, latency and SSL expiry, with 30-day uptime and p50 latency at a glance.
Incidents that find you
An incident opens the moment a monitor degrades or goes down, and goes out by email, Slack or your own webhook before the complaints start.
Public status pages
Publish a clean public status page with each monitor's state, 90-day uptime and recent incidents — never a URL or a secret.
Minutes, not quarters.
Add a monitor
A URL, the status you expect, how often to check. Mark it public if it belongs on the status page.
It gets probed
Every minute, status and latency are recorded; TLS expiry is tracked alongside.
Incidents find you
Degraded or down opens an incident and sends it out; resolved closes it and tells you how long it lasted.