Check website availability from multiple regions
A site can load perfectly for you and still be unreachable for part of your audience — from another city, another ISP, another country. Pingvera checks availability from 5 points at once — 3 regions in Russia and 2 in Europe — and shows exactly where the site doesn't respond. Plus SSL and domain expiry. No sign-up.
We check availability, SSL and domain expiry. Results are cached for 10 minutes.
What the check shows
The check reaches the site from several locations at once — Amsterdam, Lauterbourg and Nuremberg in Europe, plus Buffalo in the United States — and for each one shows three things: whether the site loads, what response code the server returned (200, 403, 500, timeout), and how many milliseconds the response took. The same request also checks SSL certificate expiry and domain registration expiry — a full picture of site health, not just "does it ping".
Why checking from a single location isn't enough
A regular availability check reaches a site from one server and can only honestly answer one question: "did it load for me". That's not the same as "the site works for everyone". Between "it loaded for me" and "it works for all visitors" there can be several causes a single vantage point simply can't see:
- ISP-level blocking. Some providers restrict access to a domain before others do — a site can be blocked for part of the audience and reachable for the rest at the same time.
- Routing and peering issues. The network path to a site can be fine from one region and go through a congested or broken link from another, so some visitors get a timeout or a slow response while others load normally.
- Regional DNS. Local DNS resolvers sometimes serve a stale or wrong record — the site "can't be found" only for a specific ISP or region, even though it's technically up.
- Geo-filtering on the site or CDN side. Some sites and protection services (anti-bot, CDN) restrict access by country or region themselves — sometimes catching legitimate visitors by accident.
A single-server check only ever answers "it loaded for me" — it physically can't see any of these situations, because it's only looking from one side.
How to read differences between regions
The result from each location breaks down into a simple logic:
- All regions say "ok". The site is alive and broadly reachable — no availability problem at the moment of the check.
- Some regions can't reach it, some can. This is almost certainly not the server — it's the network: blocking at specific providers, regional routing issues, or geo-filtering. The server itself is likely responding fine, just not to everyone.
- No region can reach it. The site really is down — this isn't network selectivity anymore, it's a server, hosting or domain failure.
- Slow response from only one location while the rest are normal. Looks like a routing or peering issue to that specific region, not overload on the site itself.
A one-off check vs. continuous monitoring
A one-off check is a snapshot "right now, from these 5 points". Continuous monitoring in Pingvera checks the site from the same regions every minute and confirms downtime by quorum: an incident only opens once several regions see the site down at once (a majority of the live regions, at least two), not just one. This is a deliberate defence against false alerts — if the network let down just one region while the rest say the site is alive, no alert fires. But if several points confirm it's down, you find out before your customer does.
See also
Check a website's SSL certificate · Check domain registration expiry · Check a WordPress site · Check for broken links
Which locations do you check from?
Amsterdam, Lauterbourg and Nuremberg in Europe, plus Buffalo in the United States. These are the same points the continuous monitoring runs from.
Why does the site load for me but not from another region?
Usually it's not a broken server but network selectivity: blocking at a specific ISP, a routing issue to that particular region, regional DNS, or geo-filtering on the site or CDN side. If at least some regions see the site fine, the server is most likely healthy — the problem is in the path to it for a specific audience.
What is quorum and why does it matter?
Quorum is the rule that monitoring only opens an incident once several live regions confirm downtime at once (a majority, but never fewer than two) — not just one. It protects against false alerts: if one region has a transient network glitch while the rest see the site up, no alert fires.
How do I check availability from multiple regions automatically?
The check on this page is a one-off snapshot. To get alerted automatically, put the site under continuous monitoring in Pingvera — checks run from the same 5 points every minute, and alerts fire by quorum rather than on a single failure.
Do I need to sign up?
No. A one-off check is free and requires no sign-up. Sign-up is only needed if you want continuous monitoring with an alert before your customer notices a problem.
How often can I check?
The result for each site is cached for 10 minutes so we don't add extra load to the site being checked. For continuous monitoring with checks every minute, put the site under ongoing monitoring in Pingvera.