Uptime Monitoring & Status Pages

What this scanner does

Sends a lightweight HEAD request (with automatic GET fallback) every 60 seconds with a 10-second timeout. Opens an incident only after consecutive failures to filter network blips, closes it on the first successful probe, and records the duration and error class. Treats 4xx responses (WAF challenges, rate limits) as up — only 5xx and transport failures count as down. Sends email alerts on both downtime and recovery, and renders a public status page with live state, 90-day daily history, and uptime percentages.

Why it matters

The gap between an outage starting and you finding out is pure damage: lost signups, failed payments, and customers discovering the problem before you do. A monitor bounds that gap to about a minute. The public status page absorbs support load during incidents and doubles as reliability evidence — a 90-day green bar answers the procurement question before it gets asked.

Common findings

• Downtime discovered by customers before the team
• Recurring short outages invisible to 5-minute-interval checks
• TLS and DNS failures misread as application errors
• No public status page for customers to check during incidents