Avoiding false alarms

Pingerer already re-checks every failure before alerting. If you still get alerts that don't reflect a real problem, these settings help.

Let our checks through

Bot protection (Cloudflare, Sucuri, Wordfence and similar) sometimes challenges or blocks automated requests. Allow our User-Agent, Pingerer/1.0 (+https://pingerer.com/bot), or our IP addresses.

Accept the right status codes

If a page always redirects or answers with an unusual code on purpose, add it to the monitor's expected status codes.

Give slow pages more time

For pages that are slow by nature, like reports or search, raise the “alert when slower than” limit, alert on the average over a few minutes instead of checks in a row, or point the check at a lighter page. A dedicated health URL (like /up) is ideal.

Choose a stable keyword

Pick text that's always on the page, like your business name in the footer, not something that changes, like a price or date.

Check from more regions

On plans with several regions, failures are confirmed from another region before you're alerted, which filters out most network blips. See pricing.

Plan maintenance

Schedule a maintenance window before planned work so it doesn't alert.

Send the right alerts to the right place

Use alert rules, escalation and quiet hours so urgent problems wake someone up and the rest waits for the morning. See Alerts.

Still getting false alarms?

Tell us with the incident number. We look at every report.