Where a check runs from decides what it can see. PulseTrace's probe fleet spans 12 regions; every monitor runs from the ones you choose, in parallel, and reports per region — so a CDN pop failing in one geography, a geo-DNS answer, or a regional latency creep is visible as exactly that.
Regional results feed everything above them: confirmation rules can require failures from more than one region, the Global Monitoring Map plots monitors where their targets live, and Regional Intelligence shows which DNS answer each region receives. For targets inside your network, the probe agent joins the fleet as a private region.
Region count is a plan dimension — one on Free, three on Team, all on Pro and Enterprise — so the free tier is real monitoring, and the paid tiers buy geographic certainty.
Free: 1 region · Team: 3 regions · Pro and Enterprise: all regions · probe agent on every plan with API access.
Compare plans →