Troubleshooting

I got a false-positive alert

This should be rare by design — an incident only opens after a failure is independently re-confirmed, never on a single blip. If you believe you saw a false positive, check the incident’s timeline: it shows what happened and when.

My probes are being blocked by a WAF or firewall

Some hosts and WAFs block traffic from unfamiliar IPs or user agents. Pingdeck identifies itself with a distinct user agent on every request — allowlist it, along with our probe IP ranges (shown in your workspace settings), the same way you’d allowlist any monitoring service.

A heartbeat monitor keeps reporting missed

• Confirm the cron job is actually running — check your server’s own cron logs first.
• Confirm the ping only fires on success (&&, not unconditionally) if that’s the intent.
• Check the expected interval and grace period aren’t tighter than the job’s real schedule — a job that occasionally runs a few minutes late needs a grace period to match.

My probes/heartbeat pings are rate-limited

Heartbeat pings are capped at 60/min per token — plenty for a normal schedule, including retries. If you’re hitting it, something is pinging in a tight loop; check for a misconfigured retry.