← All posts
Product

Why a check fails only when two regions agree

One region timing out is usually the network between us and you. Two regions failing the same way is usually you.

Most false pages we saw in early tests came from a single check location having a bad minute: a congested transit link, a DNS resolver that lagged, a cloud zone being drained. The service itself was fine.

So a Pingvale monitor is marked down only when at least two regions see the same failure within one interval. Before anyone is paged, a third region retries. If that retry passes, the event is logged on the monitor and nobody wakes up.

You can raise the number for noisy endpoints, or set it to one for internal services you check from a single region. The default is two because it removed almost all false pages without delaying real ones by more than a single interval.

Join the waitlist

Copied