How to choose monitoring regions: Zurich, New York, Singapore
Checks run from Zurich, New York and Singapore. How many regions each plan keeps, how the fastest one is chosen, and why a second opinion is not a second region.
A monitoring region is the city a check is sent from. HyperMonitors has three: Europe (Zurich), US East (New York) and Asia-Pacific (Singapore). Which ones run on a schedule is a plan limit. Which one is asked again after a failure is a separate mechanism, and it is easy to describe them as the same feature. They are not.
How many regions each plan keeps
| Plan | Regular regions per monitor | Fastest interval |
|---|---|---|
| Free | 1 | 5 minutes |
| Solo, $5 / €5 / CHF 5 | 2 | 60 seconds |
| Team, $25 / €25 / CHF 25 | 3 | 60 seconds |
| Enterprise, from $39 / €39 / CHF 39 | All of them (3 today) | 30 seconds |
The dollar, euro and franc prices are the same number; checkout picks the currency from the country. Annual billing is $4, $21 and $32 a month respectively, charged yearly. The first paid month is a 30-day trial. None of that changes the region count.
Automatic means “measure, then keep the fastest”
A new monitor defaults to automatic regions. For up to an hour it is checked from every region, on purpose past the plan’s cap, so there is a latency sample from Zurich, New York and Singapore. After that it keeps the fastest N the plan allows, fastest first. On Free, N is 1, which is why automatic selection matters most there: you cannot tick a second box, and you also should not have to guess whether Zurich or New York is closer to the target.
Manual selection is available when the plan allows more than one region. You pick the cities, and the list is capped at the plan’s number. A monitor left on automatic re-measures when an upgrade unlocks another region, so the new city can win a place. A monitor you pinned to specific cities keeps those cities until you edit it. A downgrade trims the list to what the new plan allows.
A second opinion is not a second scheduled region
Every monitor that fetches a target — including a free monitor with one regular region — gets a confirmation check from another region when its own check fails. That request is not on the schedule, and it does not count as a second region in the table above. The scheduled view of “is it up this minute?” still comes from the regions you keep. The alert waits until the other city agrees the failure is real. The separate article walks through the states.
Which city to care about
Match the region to the users, not to the office. A product whose customers are in the EU is fairly measured from Zurich. A product with users in both the US and Europe learns something from two regions that one region will hide: a failure that is a routing problem into one continent. Three regions is the current ceiling, because three cities exist. Adding a city later widens Enterprise automatically; it does not silently give Free a second scheduled check.
The account data stays in Switzerland either way. A probe in New York receives the target URL or host for the checks you assigned to it, not the customer list. That split is covered on the GDPR page, and it is the reason “Swiss hosting” and “checked from Singapore” can both be true.