What does Lemwatch monitor?

Lemwatch runs 20+ automated checks per site: uptime, response time, SSL/TLS expiry, domain expiry, DNS changes, sitemap health, broken links, content changes, SEO audits, mobile usability, security headers, and more.

Yes. The free tier monitors up to 5 sites. Pro is $19/month for 50 sites and Agency is $59/month for 100 sites, both with full feature access.

How is Lemwatch different from UptimeRobot or Pingdom?

Lemwatch bundles uptime, change detection, SEO audits, security scans, and a public API in one platform — features competitors charge separately for. It also includes team workspaces, white-labelled status pages, and a webhook system out of the box.

Does Lemwatch send alerts?

Yes. Lemwatch supports email, browser push, webhooks, and per-site notification routing so the right person hears about the right incident.

Is there a public API?

Yes. Pro and Agency plans get a public REST API with webhooks for sites, checks, incidents, and reports.

Are incidents created automatically or do I have to create them manually?

Incidents are created fully automatically. When a site transitions from up to down — confirmed by 2 or more consecutive failed checks to prevent false positives — an incident is created with the start time, affected URL, error details, and response time data. You don't need to create incidents manually, but you can add context and notes as you investigate.

What does the incident workflow look like?

The lifecycle is: Active → Acknowledged → Investigating → Resolved. When downtime is detected, the incident starts as Active. A team member clicks 'Acknowledge' to signal they're working on it. They add investigation notes as they diagnose. Once the issue is fixed and the site is back up, they resolve the incident. The full timeline — including all status transitions, notes, and timestamps — is preserved for postmortem review.

How do postmortem reports work?

After resolving an incident, click 'Write Postmortem' to document what happened. The template includes sections for: Root Cause (what broke and why), Impact (who was affected and for how long), Timeline (minute-by-minute breakdown from detection to resolution), and Action Items (concrete steps to prevent recurrence). Postmortems are stored with the incident record and searchable for future reference when similar issues arise.

Do incidents automatically show on my public status page?

Yes. Active incidents display on your public status page automatically with current status and affected services. When incidents are resolved, they move to the recent history section. If you have status page email subscribers, they receive automated notifications when incidents start and resolve — no manual status page updates needed.

How is MTTR calculated?

Mean Time to Resolution is calculated as the time between incident creation (first failed check) and incident resolution (site confirmed back up). We track MTTR per incident, per site, and across your entire fleet. You can see MTTR trends over 7, 30, and 90-day windows to identify whether your team's response is improving or degrading.

Can multiple team members work on the same incident?

Yes. Any team member can acknowledge an incident, add investigation notes, and update the status. All actions are attributed and timestamped, so you have a complete audit trail of who did what and when. This is especially useful for incident handoffs between shifts — the incoming team can read the full investigation timeline and pick up exactly where the previous team left off.

Is there on-call scheduling or escalation built in?

Lemwatch focuses on the incident response workflow — detection, acknowledgment, investigation, resolution, and postmortem. For complex on-call rotations, escalation policies, and schedule management, we integrate with PagerDuty via webhook. This gives you Lemwatch's detection intelligence combined with PagerDuty's scheduling power — without duplicating functionality.

Can I export incident data for compliance or SLA reporting?

Yes. Incident history, MTTR metrics, and postmortem reports are all available through the dashboard and can be included in white-label PDF reports for clients or stakeholders. The SLA dashboard also references incident data to show compliance status against your uptime targets.

Incident Management

From Alert to Postmortem

Automatic incident detection, team acknowledgment, investigation tracking, MTTR metrics, and postmortem reports. The complete incident lifecycle — from first failed check to 'here's how we prevent this next time.'

Auto

Incident Detection

Zero manual intervention

MTTR

Tracked Per Incident

Measure response improvement

Full

Audit Trail

Every action timestamped

Status Page Updates

Everything syncs automatically

The Complete Incident Lifecycle

Every step from detection to prevention — automated and tracked

Detection

Automated downtime detection with 2-check confirmation. Screenshot captured on failure for visual debugging.

Notification

Team alerted via all channels. Status page auto-updates. Subscribers notified. Incident timeline begins.

Acknowledgment

Team member claims the incident. Everyone else knows someone is actively investigating. Clock starts on response time.

Investigation

Add notes as you diagnose. Document hypotheses, tests, and findings in real-time. Build the timeline as you work.

Resolution

Mark as resolved when fixed. Site recovery is confirmed automatically. Status page updates. Subscribers notified.

Postmortem

Document root cause, impact, and action items. Searchable knowledge base prevents the same issue from recurring.

Incident Management Features

Every tool your team needs to detect, respond to, and learn from incidents

Automatic Incident Creation

When a site goes down (confirmed by 2+ consecutive failed checks), an incident is created automatically with start time, affected checks, and full diagnostic context. No manual intervention required.

Acknowledge & Investigate

Team members can acknowledge incidents to signal they're actively working on resolution. Add timestamped investigation notes as you diagnose — building a real-time timeline of your response.

MTTR & MTTD Tracking

Mean Time to Resolution and Mean Time to Detection are calculated automatically for every incident. Track how your team's response improves over weeks and months.

Postmortem Reports

After resolution, document root cause, customer impact, detailed timeline, and concrete action items. Build a searchable knowledge base of past incidents to prevent recurrence.

Status Page Integration

Active and recently resolved incidents automatically display on your public status page. Email subscribers get notified when incidents start and resolve — zero manual status updates.

Team Workflow & Handoffs

Assign incidents to team members, hand off between shifts with full context, and track who acknowledged what and when. Complete audit trail for post-incident review.

Investigation Notes

Add structured notes during investigation — hypothesis, actions taken, findings, and resolution steps. Each note is timestamped and attributed to the team member who wrote it.

Incident Analytics

Dashboard showing incident frequency, MTTR trends, most-affected services, and resolution patterns. Identify systemic issues and track improvement over time.

How It Works

From detection to resolution in three steps

Incident Detected Automatically

Uptime check fails 2+ times consecutively. An incident is created automatically with full context — affected URL, error codes, response times, and timeline.

Team Notified Instantly

Alerts go out via all configured channels (email, Slack, Discord, Telegram, webhook). Status page updates. Email subscribers are notified. Your team knows immediately.

Acknowledge, Investigate, Resolve

Team member acknowledges to signal they're on it. Add investigation notes as you diagnose. Resolve when fixed. Write a postmortem to prevent recurrence.

Why Teams Need Structured Incident Management

Without Incident Management

• "Who's looking at this?" — nobody knows who's working on what
• Same issue recurs because nobody documented the root cause
• Shift handoffs lose context — incoming team starts from scratch
• Manually updating status pages during an outage adds stress
• No MTTR data — no way to prove response is improving

With Lemwatch Incidents

• One-click acknowledge — everyone knows who's on it
• Postmortem templates capture root cause and prevention steps
• Full investigation timeline for seamless shift handoffs
• Status pages and subscriber emails update automatically
• MTTR trends show measurable improvement over time

Incident Management FAQ

How Lemwatch handles the complete incident lifecycle

Explore More

Handle Incidents Like a Pro

From automatic detection to postmortem. Track every incident, measure your response, and prevent recurrence.

Start Free Trial

No credit card requiredFree forever planCancel anytime