Know when a site needs you. Keep the history in view.
Track website availability and downtime alerts alongside site health. Start with the fleet overview, then investigate the affected site using its check history and available diagnostics.
Compare availability with the rest of site health
The monitoring overview separates uptime, speed, SEO, accessibility and security. A single score is only the starting point: inspect the affected dimension and its latest measurement before deciding on a fix.
Monitoring detects and reports problems. A downtime alert is not a guarantee that Irma can repair the underlying host or server.
How you use it
Check on a configured cadence
Each site's interval determines when the scheduled monitor probes it. The monitor currently runs from one primary location; it is not a multi-region network.
Distinguish warning from incident
A failed check updates the site's state. Incident and notification thresholds can require confirmation, so one failure and a confirmed outage are not the same record.
Keep maintenance distinct
The connector's recognized maintenance response is recorded as maintenance rather than ordinary downtime. An unrelated 503 response still counts as a failure.
What to know
Do checks run just because I open the dashboard?
Can a certificate problem appear as a failed check?
Start with your own sites.
Connect a small portfolio, check the tools you need, and choose the plan that fits your team's work.