Regions & status
A VPN server can be perfectly healthy from one country and completely blocked from another. TunnelHQ tests from the regions you choose, tracks a result for each, and rolls them into one status you can act on.
On this page
Any vs. specific regions
By default a monitor tests from Any — TunnelHQ picks a worker and runs the check. That's all you need to answer "is this server up?"
Add specific regions when location matters. Each region you add (Pakistan, Germany, Singapore, and so on) gets its own independent check on every cycle, so you can see that a server is reachable from one place and blocked from another — exactly the kind of thing a single-location check would miss.
Specific regions are a Pro feature
Aggregate status
When a monitor tests from more than one region, TunnelHQ keeps the latest heartbeat per region and rolls them into a single aggregate status:
- Healthy — every active region is passing.
- Degraded / partial — some regions are failing while others still pass. The server isn't down everywhere, but it's not fully reachable either.
- Down — at least one region is failing and none are passing.
The aggregate is what drives the status pill, the dashboard counts, and incident creation, so a multi-region monitor reflects the experience of all your users, not just one vantage point.
Partial-failure alerts
It's your call whether a partial failure is worth a page. Each monitor has a notify on partial switch — on by default once a monitor has more than one region, off for single-region monitors. Turn it off for servers where one blocked region is expected and you only want to hear about a full outage.
Pausing a single region
You can pause an individual region without removing it. The region chip stays in the list (dimmed), the scheduler skips it, and it stops counting toward the aggregate — handy when a probe location is having its own problems and you don't want the noise.
Region codes
pk, de, sg, …), plus the special value any. You'll see these in the API and in heartbeat history.