Choosing Monitor Locations

Last updated: 2026-03-06

Monitor locations determine where your checks run from geographically. Using multiple locations gives you better accuracy and helps catch regional issues.

Why Location Matters

Different regions can experience different issues:

• Network problems may only affect certain regions
• CDN issues might impact some areas but not others
• Server location affects response times globally
• False positives are reduced with multiple check points

Available Regions

We check your services from multiple locations worldwide:

The exact locations may vary - check your dashboard for the current list.

Selecting Locations

When creating or editing a monitor:

1. Find the Monitoring Locations section
2. Check the boxes for the regions you want
3. Save your monitor

You can select one location or multiple.

Best Practices

For Global Services

Select locations in all major regions your users are in:

• If you have US and European users, select both
• This catches region-specific outages

For Regional Services

Select locations near your users:

• If most users are in Europe, prioritize European locations
• You can still add one distant location for comparison

For Accuracy

Use at least 2 locations:

• If one location has network issues, the other can still check
• Reduces false alarms from temporary network blips

How Multi-Location Checks Work

When you select multiple locations:

1. Each location checks your service independently
2. We combine the results for overall status
3. You’ll see response times per region
4. An alert triggers only if multiple locations report issues

This prevents false alarms from a single location having temporary problems.

Viewing Location Results

On your monitor’s detail page, you can see:

• Response time from each location
• Status per region
• Which locations are having issues (if any)

This helps you understand if a problem is global or regional.

On the Monitors list (table and cards), monitors with multiple active regions now show compact colored region pills. The previous plain text list of regions is hidden to keep rows readable.

• Green pill = region currently up
• Red pill = region currently down
• Gray pill = no recent/usable signal yet (unknown)

Hover (or focus) a pill to open a rich popover with:

• Region status
• Region-specific average response time for the selected metrics window (same averaging model as the Avg response column, but scoped to that region)

Single-region monitors do not show the multi-region pill group.

Region-Based Troubleshooting

If one location shows problems but others don’t:

IPv6, Timeouts, and IPv4 Fallback Notes

In some cases, a check can fail on the first network path (often IPv6) but succeed immediately on IPv4. When that happens, StatusPage records the check as UP and adds an IPv4 fallback note in Recent Checks.

This helps reduce noisy false DOWN events caused by transient path-level transport failures while still giving you visibility that fallback was required.

Timeouts are also interval-aware (instead of fixed), so short-interval monitors avoid overly aggressive timeout failures.

What’s Next?

• Setting Your Primary Monitoring Region — choose which region runs your scheduled checks
• Transport Errors, Timeouts, and IPv4 Fallback — understand UP-with-note fallback behavior and transport error handling
• Monitors List: Sticky Filters and Grouping — organize large monitor inventories faster with saved status-page filters and grouped sections
• Configure monitor alerts
• Understand uptime and SLA reports
• Learn about monitor types