# Regions and probes

> InfraNest runs your checks from several locations ("probes"), so a problem in one place doesn't cause a false alarm — and you can see how your service looks…

Source: https://infranest.io/docs/monitoring-probes
Last updated: 2026-09-19

---

Regions and probes let you check your service from multiple locations around the world, so a single slow or flaky spot doesn't trigger a false alarm — and you can see exactly how your service performs from different parts of the globe.

## Overview
- Each check runs from multiple regions at once.
- A status only changes when enough regions agree, which prevents one flaky location from paging you unnecessarily.
- Slow responses show as degraded rather than down, and alerts only fire after a number of consecutive confirmed failures.
- You can pin preferred regions and choose IPv4 or IPv6 for each check.

<!-- screenshot: monitoring-probes -->

<!-- docs-screenshots:start:monitoring-probes -->

![Regions and probes](/media/15667b0a-e437-4de4-a343-afecb0461e51)

<!-- docs-screenshots:end:monitoring-probes -->

## How regions and consensus work
1. Open the check's detail page to see the per-region results and compare how each location is reporting.
2. Check the consensus setting to understand how many regions need to agree before a status change is triggered.
3. Note that a number of consecutive confirmed failures is required before an alert fires — a single failed check won't page you.
4. Remember that slow responses appear as degraded, not down, so you can tell performance issues apart from outages.
5. Set your preferred regions and choose IPv4 or IPv6 for the check, if you want to customize where and how it's tested.

## Compare regions on the chart
1. Go to the check's detail page.
2. Above the chart, open the dropdown and select **Compare regions**.
3. Review the overlaid response-time lines — one per region.
4. Look for breaks in a line: this means no measurement was reported from that region during that time, not that there's no data at all.
5. Hover over a gap, or read the note under the chart, to see why a line breaks. Common reasons include:
   - The probe in that region was offline or restarting. InfraNest may borrow a probe from another region to keep checking your service, and the chart will note this (for example, "APAC had no probe of its own for part of this period. It was checked from EU instead").
   - The region was added recently and only has history from the point it started running.
6. Switch between the **24 hours**, **7 days**, and **30 days** views as needed. The 24 hours view shows every individual check, while 7 days and 30 days average results into 4-hour and daily points — so a brief spike will look smaller over longer time frames.

> [!NOTE]
A line breaking on the chart just means that region didn't report during that window — it doesn't mean your service was down or that data is missing everywhere.

> [!TIP]
If you want the clearest picture of a short-lived spike, check the **24 hours** view rather than the 7-day or 30-day views, since those average out quick changes.