Monitoring locations: where your checks run from
A site can be up in Frankfurt and unreachable from Singapore — a CDN edge, a DNS change that has not propagated yet, a routing problem or a firewall rule that only affects some networks. Checking from where your users are is how you find out before they tell you.
The locations
| Location | Where |
|---|---|
| Germany | Falkenstein |
| Finland | Helsinki |
| United States (West) | Hillsboro, Oregon |
| Singapore | Singapore |
Every location is a server we operate ourselves. The addresses our checks come from are published on our page for server operators, so you can allow them through a firewall: https://pingsured.eu/bot
Choosing locations
You pick the locations for each ping when you create or edit it; the form only offers locations that are running. Each location checks the ping on its own, at the interval you set — every 15 or 30 seconds (Scale plan), every minute, every 5 or 15 minutes, or every hour.
How many different locations an account can use depends on the plan: one on Solo, up to three on Team, and all of them on Scale. The count is across the whole account, not per ping — a Team account checking some pings from Germany and others from Singapore and the US uses three.
How a failure is judged
Each location is judged on its own. Your alert threshold — such as "3 of the last 5 checks failed" — is applied per location, so one slow response from one place does not raise an alarm, and a site that is down from one location is not hidden by the others still reaching it.
A ping counts as failing when it is failing from any of its locations.
Where your data is stored
The checks run where you choose; everything they produce is stored in the EU. Account data and check results live on our servers in Germany and Finland. The locations outside the EU send each result back as soon as the check finishes and keep nothing. The details are in our privacy policy and the data processing agreement.