Checker IPs are now one click away in the monitor form
If your service sits behind a firewall or a WAF, PingZen’s checks have to be let through — and for that you need to know which addresses they arrive from. That address is now printed in the monitor form, one click from your clipboard.
How it works
Open a monitor for creation or editing and expand the Check locations block. Every checker shows its IP underneath.
Click the address and it is copied. A green “Copied” marker appears and the address stays on screen, so you can compare it against the rule you are typing. Paste it into your firewall allowlist, your WAF’s IP set, or your cloud provider’s rule.
Picked several locations? Copy each one and add them all. Every checker reaches you independently, from its own address.
The addresses stay current
Nobody types them in. The server determines the address when a checker connects and refreshes it on every reconnect. When we move a location to a new machine, the new address simply appears in the UI — no release, no announcement.
That makes the monitor form the source of truth: if you ever added one of our addresses to a firewall by hand, open it and check it still matches.
For automation the whole list is available over the API, no authentication required:
GET https://pingzen.dev/api/v1/probe/ipsHandy when your firewall rules are generated rather than hand-edited.
Two cases where the address differs
The IP shown is the address the checker connects to PingZen from. For an ordinary VM that is the same address your service sees. Two exceptions — so you do not chase a false DOWN:
- SOCKS5 and MTProxy monitors. The check runs through the proxy, so the target sees the proxy’s address, not the checker’s.
- An HTTP(S) proxy on the checker host. If one is configured, HTTP checks egress through it while ICMP, TCP and DNS leave the host directly.
Also in this update
Our full list of locations is Moscow, Novosibirsk and Minsk. The Istanbul probe has been retired: the machine has been unreachable since late July and is not coming back, so it is no longer offered when creating a monitor. Monitors that used it keep running via their remaining checkers or the central server.