Everything it watches, one page each.
What heyUptime checks, how often, what it tells you when something breaks, and what it does quietly in the background so you don't have to.
Website uptime monitoring
Checks every 30 or 60 seconds, a second check before any alert, and the reason in plain words.
Keyword and status-code checks
Accepted status codes like 200 or 2xx, text that must or must not appear, GET, HEAD or POST.
Public status pages
90-day uptime bars, components, incidents, posted updates, email subscribers and a maintenance state.
SSL certificate monitoring
Reminders 14, 7, 3 and 1 days before expiry; an expired certificate is reported as down, with the reason.
Domain expiry monitoring
Daily RDAP lookup of the registration date, with reminders 30, 14, 7 and 1 days before it runs out.
DNS change monitoring
Hourly snapshots of A, AAAA, CNAME, NS and MX records, an alert on change, and the change named as the likely cause of an outage.
Cron job and heartbeat monitoring
A ping URL per job, a period plus a grace time, and a missed check-in reported as down. Test it free first.
Alerts that explain why
Confirmed before sending, the likely cause in every message, a recovery message with the duration, six channels.
Maintenance windows
Planned work without alerts: checks keep running, the status page says maintenance, and anything still down afterwards is reported.
Incident history, notes and CSV export, weekly summary email
Every outage kept with its cause and duration, notes, CSV downloads, and a weekly summary email.
Next time, be the first to know.
Let someone else watch the shop. If anything breaks, you will hear it from us, not from a customer.