Global Regions
Overview
Quismon runs checkers in 33 locations across 6 continents. Each check selects one or more regions; every regional execution is a real check from a real machine in that location.
Fetch the live list programmatically:
curl https://api.quismon.com/v1/regionsRegion Key Format
Region keys look like na-east-ewr — continent, compass position, and city airport code:
| Prefix | Continent | Example |
|---|---|---|
na- | North America | na-east-ewr (Newark/NYC) |
sa- | South America | sa-east-sao (São Paulo) |
eu- | Europe | eu-central-fra (Frankfurt) |
ap- | Asia Pacific | ap-southeast-sin (Singapore) |
au- | Australia | au-southeast-syd (Sydney) |
af- | Africa | af-south-jnb (Johannesburg) |
Familiar cloud-provider names are accepted too and mapped to the nearest Quismon region (e.g. us-east-1 → na-east-ewr).
Primary Regions (All Tiers)
Free-tier orgs can use the 6 primary regions — one per major geographic area, chosen for population density, connectivity, and centrality:
| Region | Location | Why |
|---|---|---|
na-east-ewr | Newark/NYC, USA | Largest population center, major IX |
eu-central-fra | Frankfurt, Germany | DE-CIX, central, best peering |
ap-southeast-sin | Singapore | Central for all of Asia, cable hub |
sa-east-sao | São Paulo, Brazil | 70% of Brazil's data centers |
af-south-jnb | Johannesburg, South Africa | Largest data center market in Africa |
au-southeast-syd | Sydney, Australia | Primary APAC cable landing |
Paid and enterprise tiers can use all 33 regions: 11 in North America, 2 in South America, 9 in Europe, 8 in Asia Pacific, 2 in Australia, and 1 in Africa. See GET /v1/regions for the authoritative list.
Simultaneous vs Staggered Execution
When a check targets multiple regions, simultaneous_regions controls when they run:
true(default) — all regions execute at the same instant. Best for detecting regional outages quickly and for global availability monitoring.false— regions execute staggered across the interval, spreading load over time and catching transient issues that a single instant would miss.
See Check Types & Execution for the diagrams.
Budget Impact
Every regional execution counts toward the hourly check budget: (3600 / interval_seconds) × number_of_regions. A 60-second check in 3 regions consumes 180 checks/hour — three times the single-region cost. See Optimizing Check Budgets for strategies.
Validation
Unknown region codes are rejected on check create/update with the full valid-region list inline plus a pointer to GET /v1/regions. Free-tier orgs attempting a non-primary region get the allowed primary regions in the error.