Three parts that work together: checks that catch real failures, an incident workflow that keeps everyone informed, and a status page that stays honest without anyone maintaining it.
A ping only proves a server answered. These check whether it answered correctly.
Confirms the page returns the code it should. A server that responds with a 500 is down as far as your customers are concerned, and a plain ping would call it healthy. On Pro and Agency it also checks that the page still shows a text you chose, because an error page that answers 200 is not up either.
Every plan, content check on Pro and AgencyA certificate that quietly lapses is one of the most avoidable outages there is. You hear 30, 14, 7 and 1 days ahead instead of from a browser security screen, and you hear it when a certificate is in date but issued for the wrong name or by an authority browsers do not trust.
Every planSites rarely fail all at once, they get slow first. Tracking response time turns that slide into a warning instead of a surprise, and tells you when a service is slower than is normal for it, well before it crosses a limit.
Pro and Agency, or a Starter add-onWhen a domain name stops resolving, everything behind it is gone at once, and a record that changes without anyone knowing is how a site ends up somewhere it should not be. We look your name up through two independent DNS services, open an incident when it stops resolving, and tell you when it starts pointing somewhere new. Where the registry publishes it, you also hear in good time that the registration of the name itself is about to run out.
Pro and AgencyEvery outage moves through a clear lifecycle, so your team and your customers always know exactly what is happening. A slow response opens and closes its incident by itself; the two steps in the middle are for an outage somebody is working on.
Opened automatically at the first check that fails, with what the check ran into. No manual step, no missed outage.
Your team sets the status while working the problem, and the status page shows it.
Customers can see you are past diagnosis and actively shipping a repair.
Closed automatically once the check passes again. An incident whose recovery never arrived can be closed by hand, and its timeline says that it was.
Checks are only useful if the right people see them. These are the three places that happens.
Email reaches you on every plan, and each person on the account chooses whether they get it. Slack, Microsoft Teams and generic webhooks land alerts in the tools your team already has open, all at once if you like. Several services failing together are one message, not one each.
Email on every plan, the rest on Pro and AgencyA page your customers can open, with every service you monitor and its current state, updating itself from the checks. Live incident history, and maintenance banners your visitors see before the work starts rather than after.
Every planUptime percentages and response-time trends you can read at a glance, plus a PDF when someone needs the numbers on paper. On the first of the month the report of each status page arrives by mail, with a short summary of how the month went.
Pro and Agency, or a Starter add-onUnlimited client status pages under a single Agency account, each carrying the client's branding instead of ours. A shared pool of 250 services you divide however you like, unlimited team members, and read-only access for clients who just want to see their own page.
We monitor Lunolyte with Lunolyte. Our own status page is public, including the bad days.
Lunolyte