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.

I'm Not Receiving Alerts

Triage missing or delayed alerts: quiet hours, channels, spam, thresholds, maintenance mode, escalation policies, and acks.

I'm Not Receiving Alerts

Check These First

1. Quiet Hours

Are your quiet hours active? Go to Settings → Notifications → Alert Preferences and check the quiet hours schedule. Non-critical alerts are suppressed during quiet hours — they still show in the Alerts Inbox marked suppressed with a scheduled-for time.

2. Alert Channels

Verify your notification channels are configured:

Email: Check Settings → Notifications for the correct email address (and per-site override under Edit Site → Notifications)
Slack / Teams / Discord / Google Chat / Mattermost / Rocket.Chat: Verify the webhook URL is still valid (webhooks can expire, be deleted, or have their channel archived). For Teams, legacy O365 URLs (outlook.office.com / webhook.office.com) still work but are being retired — see Teams Integration.
Telegram: Confirm the bot is still in the chat/group and the bot token hasn't been revoked in @BotFather.
ntfy: Open the topic in the ntfy app/browser and check that the device is subscribed and online.
PagerDuty: Confirm the integration key matches an active service.
Push notifications: Check browser permissions (click the lock icon in your browser's address bar).

3. Spam/Junk Folder

LemWatch emails come from alerts@lemwatch.com. Check your spam folder and add this address to your contacts/allowlist.

4. Consecutive Failure Threshold

If set to 2 or 3, you won't get alerts for single failed checks. Go to Settings → Notifications → Alert Preferences to check your threshold.

5. Maintenance Mode

Is the site in maintenance mode? Alerts are suppressed during maintenance. Check the site's Settings tab.

6. Alert Type Configuration

You may have disabled certain alert types. Go to Settings → Notifications and check which event types are enabled.

7. Escalation policy already acknowledged

If the site is attached to an escalation policy and somebody already clicked Acknowledge on the incident, the remaining escalation steps stop firing on purpose. Reopen the incident or remove the ack to resume escalation. See Acknowledging incidents.

8. Escalation policy not attached

A per-site policy only fires when it's selected on the site. Open Edit Site → Notifications → Escalation policy and confirm one is chosen.

Still Not Working?

Go to Settings → Notifications and click Send test next to each configured channel
If the test alert arrives, the channel works — the issue may be that no alerts have been triggered
If the test alert doesn't arrive, the channel configuration needs updating
Contact support if you've verified all settings and still don't receive alerts

Lemwatch — All-in-One Website MonitoringUptime, performance, SEO, security, and change detection in one platform. Free tier available.Pricing · Features · Sign Up