What an external check can show
It can tell you whether the monitored HTTPS endpoint answered from the checker’s location, and when. It cannot prove that every visitor can use every page or complete checkout. Application errors behind a successful home page need separate checks.
From failure to incident
Guardian watches the public endpoint of a verified domain. Its rules require repeated failed observations before opening a reachability incident. The incident can show what was observed and what needs attention; recovery is based on later observations rather than a user clicking “fixed.”
- Check your hosting and CDN status.
- Look at recent deployments, DNS, and certificate changes.
- Confirm the public endpoint recovers after the fix.
A sensible expectation
Monitoring shortens the time between a detectable problem and a useful response, but it cannot prevent every outage or provide a universal uptime guarantee. Treat its evidence as one input alongside server logs and customer reports.
Example: the home page works, but customers cannot pay
An external check of the home page may still return a successful response while a payment provider or checkout route fails. That is outside the conclusion of a simple availability check. Use transaction-specific checks and payment provider status for the purchase flow. When Guardian reports a reachable site, read that as evidence about the monitored endpoint at the check time, not a certification of the whole business journey.