Regions and probes

Regions and probes let you see and control where InfraNest checks your service from, so a hiccup in one location doesn't set off a false alarm.

Overview

• Each check runs from multiple regions at once, not just one.
• A status only changes when enough regions agree, which is what keeps a single flaky location from paging you.
• You can pin preferred regions and choose IPv4 or IPv6 for a check.
• The check's detail page lets you compare how each region sees your service over time.

How regions and consensus work

1. When you set up a check, InfraNest checks it from multiple regions rather than just one.
2. Open a check's detail page to see the per-region results side by side.
3. A status change only happens once enough regions agree — this is the consensus setting that prevents one-off, flaky results from triggering alerts.
4. Before an alert fires, InfraNest also requires a number of consecutive confirmed failures in a row. Slow responses appear as degraded rather than Down.
5. If you want, pin preferred regions for a check, and choose whether it should prefer IPv4 or IPv6.

Compare regions on the chart

1. Open the check's detail page.
2. Above the chart, open the dropdown and select Compare regions.
3. Each region gets its own response-time line, drawn only where that region actually reported a result. A break in a line just means no measurement came from that region at that time — it doesn't mean nothing was checked at all.

NoteA line can break for two normal reasons: the probe in that region was temporarily offline or restarting (InfraNest borrows a probe from another region to keep your checks running, and marks the gap so you know which region stood in), or the region was only added recently and simply has no history before that point. Hover the gap or read the note under the chart for details — for example, "APAC had no probe of its own for part of this period. It was checked from EU instead."

4. Switch between the 24 hours, 7 days, and 30 days views. The 24 hours view plots every individual check, while 7 days and 30 days average results into 4-hour and daily points — so a brief spike will look smaller on the longer views than it does over 24 hours.

Tips

TipIf you're troubleshooting a suspected regional issue, use Compare regions first — it's the fastest way to tell whether a problem is local to one probe or affecting your service everywhere.