Troubleshooting

    Why am I getting false alerts?

    Diagnose flapping monitors, rotating content, and single-region blips that fire alerts you can ignore.

    Updated 2026-07-09
    2 min read
    false alerts
    noise
    accuracy

    Quick answer#

    Most false alerts come from three sources: single-region network blips, flapping monitors, and rotating page content. Lemwatch already filters the first two with confirmation gates and hysteresis — this article helps you tune them.

    What causes false alerts#

  1. A single probe location failing while others succeed
  2. The site returning 200 → 500 → 200 within seconds (flapping)
  3. Response time briefly crossing a threshold, then recovering
  4. Ads, banners, or timestamps changing on visual monitors
  5. Third-party scripts blocking the load once
  6. Where to check#

    Alerts inbox → Suppressed tab shows alerts Lemwatch caught but held back. That's your evidence base.

    How to reduce false alerts#

  7. Open Alerts inbox → Suppressed and read the top 5 suppression reasons.
  8. If you see "single-region failure" → keep confirmation gates on.
  9. If you see "flapping" → tighten the flap detection window.
  10. For response-time noise → widen the hysteresis band.
  11. For visual noise → follow reducing visual noise.
  12. FAQ#

    Will these settings make me miss real outages?#

    No — every setting is a *confirmation delay*, not a threshold change. A real outage still alerts within 60–120 seconds.

    Can I turn all filters off?#

    Yes, but you'll see 3–5× more alerts. Not recommended.

  13. Flapping detection
  14. Alert confirmation gates
  15. Hysteresis band
  16. Was this article helpful?