Monitoring that explains what happened
Website downtime alerts with context
A downtime alert should help you decide what to do next. See whether a check failed at DNS, connection, TLS, HTTP status or expected page content.
Define the failure before it happens
Select the acceptable HTTP status range and optional required or forbidden text. A page that returns 200 with a maintenance message can still fail your content check.
Confirm, investigate, recover
A first failure is evidence; the configured confirmation threshold opens an incident. Recent checks, safe failure categories and alert delivery history provide context. The next successful check resolves the measured incident.
Plan for intentional downtime
Use maintenance windows to suppress incident notifications during planned work. Keep a separate public status update to explain what customers should expect.
Common questions
How fast is a downtime alert?
Detection depends on your plan’s check interval, the confirmation threshold, worker scheduling and notification delivery. It is not instantaneous.
Do I need to install code on my website?
No. HTTP monitoring checks a public URL. It does not require a website agent.