Reference
Probe locations and IP allow-listing
Use this reference to identify the regions that can check your monitors and to decide how to handle network allow-listing for outside-in checks.
Probe locations
| Location | Fly.io region | UI region |
|---|---|---|
| Ashburn, Virginia | iad | US East |
| San Jose | sjc | US West |
| Stockholm | arn | Europe |
| Tokyo | nrt | Asia Pacific |
The Europe UI option maps to the backend region code eu and the Fly.io deployment region arn. In reader-facing text, use the city names: Ashburn, San Jose, Stockholm, and Tokyo.
Handle IP allow-listing
- Identify which monitor regions you selected. A target must allow traffic from every region that should check it.
- Ask your network administrator or GetPulseCheck operator for the current allocated egress addresses for the relevant environment and regions.
- Add only the supplied addresses or CIDRs to the target firewall, then run a test check from the monitor.
- Reconfirm the allow-list after infrastructure changes. Fly.io region codes identify placement; they are not IP addresses.