How does API endpoint degradation alerting work?
Lemwatch compares each endpoint's current response time against a rolling 24-hour baseline and alerts when it degrades by 2× or more.
Quick answer#
Each endpoint keeps a 24-hour rolling average response time. If the current p50 goes above 2× baseline for 3 consecutive checks, we open a degradation incident.
Why not a hard millisecond threshold?#
APIs have wildly different normal ranges. A 500 ms baseline API paged at 500 ms is fine; a 50 ms baseline API at 500 ms is broken. Baseline math catches both.
Where to find it in Lemwatch#
Site → API Endpoints → <endpoint> → Alerts.
FAQ#
Can I set a hard cap too?#
Yes — the "max response time" field overrides baseline logic.
How long until a new endpoint gets a baseline?#
24 hours of data. Until then only status-code alerts fire.
Related#
Related Articles
API Endpoint Monitoring
Monitor your API endpoints for uptime, response time, and expected responses.
How do I monitor a JSON API endpoint?
Add any HTTP endpoint under API Monitoring and Lemwatch checks status code, response time, and optional JSON body assertions every minute.
Fleet Health Overview
Get a bird's-eye view of your entire site portfolio with Fleet Health.
Traffic Analytics
Understand your site's traffic patterns with built-in analytics.