Alerts & Notifications

    Alert confirmation gates

    Lemwatch confirms a failure from multiple regions before alerting, so single-region blips stay quiet.

    Updated 2026-07-09
    1 min read
    confirmation
    multi-region
    accuracy

    Quick answer#

    Before firing a down alert, Lemwatch re-checks from 2 additional regions. If any region succeeds, the alert is suppressed as a single-region blip.

    What it does#

  1. Detects a failure from the primary region
  2. Immediately runs a confirmation check from 2 backup regions
  3. Fires the alert only if all 3 regions confirm the failure
  4. Otherwise logs the incident as suppressed with reason "single-region"
  5. Where to find it in Lemwatch#

    Site → Settings → Alert accuracy → Confirmation gate.

    How to tune it#

  6. Open the site's Alert accuracy settings.
  7. Toggle Multi-region confirmation on (default).
  8. Choose how many regions must agree (default 2 of 3).
  9. For critical sites, set All regions must fail — reduces false positives further.
  10. Save.
  11. FAQ#

    Does confirmation delay real alerts?#

    By 20–40 seconds at most. That's the cost of skipping a false page.

    Can I see which region failed?#

    Yes — every incident record lists per-region status.

  12. Why am I getting false alerts?
  13. Flapping detection
  14. Server geolocation
  15. Was this article helpful?