Response Time Threshold Alerts
Get alerted when response times consistently exceed your limits.
Response Time Threshold Alerts#
Set a per-site millisecond threshold. When response times exceed it for 2+ consecutive checks, you get a slow_response alert. Use this to catch performance degradation before it becomes downtime.
Setup#
Go to Edit Site → Advanced Monitoring → set Response Time Threshold (e.g., 2000ms). Save. The threshold applies from the next check onward and does not affect historical data.
How It Works#
Choosing a good threshold#
Look at your last 30 days of response time history in the Performance tab. Set the threshold at roughly your p95 — high enough to avoid noise from normal variance, low enough to catch real degradation. Marketing sites typically use 2000-3000ms; API endpoints 500-1000ms.
Related settings#
FAQ#
Does the threshold affect uptime %?
No. The site is still considered "up" as long as it returns a 2xx status code. The threshold only controls the slow_response alert channel.
Can I set different thresholds per region?
Not yet — the threshold is global per site. Vote for it on the roadmap.
Related Articles
RSS Alert Feeds
Subscribe to monitoring alerts via RSS for flexible notification delivery.
Alert Routing Rules
Route different alerts to different channels based on custom rules.
Notification Channels Overview
Tour of all 11 channels with links to the full setup walkthrough.
Default vs Per-Site Channels
How LemWatch picks which channel and recipient to use for each alert.