Feature
Incident management
A monitoring tool that only sends alerts leaves you with a mailbox. This one leaves you with a record.
What it does
The moment a check fails, an incident opens by itself — carrying the failure reason, the last status code and the time it started. Nobody has to notice an alert and remember to write it down.
The incident stays open while the site keeps failing and closes when the site recovers, which is what produces a real downtime window rather than an estimate. Those windows are what the uptime percentages on your client reports are built from.
Between those two moments the incident is something you work: acknowledge it so your colleagues know it is handled, leave the reasoning behind a fix, and escalate automatically when nobody has acknowledged it. Afterwards a postmortem can be attached, so the same outage teaches you something the second time.
- Incidents open and resolve automatically from check results
- Failure reason and last status code captured at the moment of failure
- Acknowledgement, so the team can see an incident is already owned
- Escalation when an incident goes unacknowledged
- Postmortems and a full incident history per site
Works alongside
Uptime & performance
HTTP/HTTPS checks around the clock — down to every 30 seconds. Status codes, response time (TTFB), payload size, plus ICMP ping and TCP-port checks per site.
Read moreSSL, domain & security
Certificate-expiry and domain (WHOIS) expiry alerts days in advance, SSL chain validity, and a security-headers audit (HSTS, CSP, X-Frame-Options).
Read moreContent & keyword checks
Catch the “white screen of death” at HTTP 200: keyword present/absent, unexpected redirects to foreign domains, and page-defacement detection.
Read moreFAQ
About incident management
Do I have to close incidents by hand?
No. An incident resolves itself when the site starts answering again, and the downtime window is recorded from the real start and end times.
What does acknowledging actually do?
It marks the incident as owned, which stops the escalation clock and tells everyone else looking at the queue that somebody is already on it.
Do incidents show up in the client portal?
Yes — each client sees the incidents for their own sites, with the downtime that was actually measured. It is the same record you are working from, not a sanitised copy.