Alerts & Notifications

    Hysteresis band explained

    Lemwatch requires response time to fully clear a threshold before recovering, preventing oscillation alerts.

    Updated 2026-07-09
    1 min read
    hysteresis
    thresholds
    accuracy

    Quick answer#

    If your alert threshold is 2000ms, Lemwatch won't mark the site "recovered" until response time drops below 1600ms (2000 − 20% band). This stops jittery pages toggling between degraded and healthy.

    What it does#

  1. Adds a 20% clearance band below every threshold
  2. Requires the metric to fully cross the band before flipping status
  3. Applies to response time, TTFB, LCP, INP, and health score
  4. Prevents "recovered → degraded → recovered" alert loops
  5. Where to find it in Lemwatch#

    Site → Settings → Alert accuracy → Hysteresis band.

    How to tune it#

  6. Open the site's Alert accuracy settings.
  7. Adjust the Band width (default 20%) — wider = more stability.
  8. For very stable sites, drop to 10%.
  9. For noisy sites near threshold, raise to 30%.
  10. Save.
  11. FAQ#

    Does this delay recovery alerts?#

    Only when the metric hovers right at the threshold. Clear recoveries fire immediately.

    Does it apply to uptime status?#

    No — uptime is binary. Hysteresis is for continuous metrics.

  12. Response time thresholds
  13. Flapping detection
  14. Why am I getting false alerts?
  15. Was this article helpful?