Geolocation monitoring

Why monitor from specific regions, which locations we support, and how it differs from cropping a page in the preview.

Available on paid plans.

Why monitor location matters

The same URL can look different depending on where the request comes from. Companies often ship localized pricing, geo-targeted promotions, region-specific legal text, or CDN variants. If you only capture from one default location, you can miss changes your customers see — or mistake a locale flip for a real content change.

Geolocation monitoring means each check runs from the country or region you pick, so snapshots line up with that audience.

This is separate from drawing a region on the preview (a crop of the page). Preview regions answer “which part of the page?”; geolocation answers “from where in the world do we load the page?” Both can be used together. See Quickstart.

Supported regions

Pick one or more of the following when creating or editing a monitor:

  • US East — Virginia, United States
  • US West — Oregon, United States
  • EU West — Dublin, Ireland
  • London — United Kingdom
  • EU Central — Frankfurt, Germany
  • AP South — Mumbai, India
  • AP North — Tokyo, Japan
  • AP Southeast — Singapore
  • SA East — São Paulo, Brazil
  • Africa South — Cape Town, South Africa
  • North Africa — Cairo, Egypt
  • Middle East — Dubai, United Arab Emirates

On plans without custom monitor location, checks use a default location (US East) as noted in the product.

Tips

  • Prefer one primary region per monitor unless you intentionally track multiple geographies; comparing history across mixed regions can add noise.
  • Pair geolocation with a clear AI prompt on paid plans when only certain regional changes matter (for example VAT-inclusive pricing in the EU).