AI root-cause analysis
For every incident Lemwatch correlates recent deploys, DNS diffs, cert changes, and upstream provider status pages to pinpoint the likely cause.
Quick answer#
We cross-reference the incident timestamp with your last deploy, DNS diff, cert change, and upstream cloud provider status pages, then rank the top 3 causes by likelihood.
Signals correlated#
Where to find it in Lemwatch#
Incident detail → Likely cause. Each candidate has an evidence link.
How to fix#
FAQ#
What if it can't find a cause?#
You'll see "No correlated changes in the last 60 minutes" — start with outage triage.
Does it access my server logs?#
No — it uses only signals Lemwatch already collects.
Related#
Related Articles
AI incident summaries
Plain-English summaries of every incident — what happened, what changed, and the likely cause — generated the moment an alert fires.
DNS Diagnostics
Monitor DNS records, email authentication, and detect DNS changes.
Why am I getting false alerts?
Diagnose flapping monitors, rotating content, and single-region blips that fire alerts you can ignore.
Incident Management Workflow
Acknowledge, investigate, and resolve incidents with your team.