Monitoring Regions
Unseenr runs uptime checks from multiple geographic locations to provide accurate, multi-perspective monitoring.
Available Regions
| Region ID | Location | Data Center |
|---|---|---|
| FSN1 | Falkenstein, Germany | Hetzner EU |
| HEL1 | Helsinki, Finland | Hetzner EU |
| ASH | Ashburn, Virginia, USA | Hetzner US (planned, not yet active) |
Region Availability by Plan
| Plan | Regions |
|---|---|
| Free | FSN1 only |
| Starter | FSN1 only |
| Pro | All regions (FSN1, HEL1, ASH) |
| Business | All regions |
| Scale | All regions |
| Platform | All regions |
Multi-Region Confirmation
When using multiple regions, you can configure the Required Regions setting. This determines how many regions must independently confirm a failure before the monitor is marked as DOWN.
For example, with requiredRegions: 2, at least 2 of the 3 regions must report a failure in the same check cycle. This prevents false positives caused by transient network issues in a single region.
Worker Architecture
Each region runs a dedicated uptime worker process:
- FSN1 (Full Worker): Runs all job types including event processing, billing, and uptime checks. Has direct database and Redis access.
- HEL1 (Uptime API Worker): Runs HTTP uptime checks only. Communicates with the main app via an internal API. No direct database access.
- ASH (Uptime API Worker): Same as HEL1 but in the US East region.
The uptime API workers have public IPs that users can whitelist in their firewalls if needed.
IP Whitelisting
If your monitored service is behind a firewall, you may need to whitelist the Unseenr worker IPs. The worker IPs are available in your project's monitor settings. All three workers have dedicated public IP addresses.