Multi-location monitoring: one failure is a question, not an answer
A check from a single location can’t tell your outage apart from a bad network route between two data centres. StatusEagle runs every monitor from three locations and asks the others before it wakes anyone up.
Example check · demo data
Multi-location monitoring runs the same check against a service from several geographically separate locations. Comparing the results separates a real outage (failing everywhere) from a local network or regional problem (failing in one place).
Why single-location monitoring cries wolf
Between a monitoring server and your website sit several networks you don’t control: the monitor’s provider, one or two transit carriers, your CDN, your host. Any of them can drop packets or stall for a few seconds. From one location, that looks exactly like your site going down. That’s the most common source of the 3 AM alert that has cleared by the time you open your laptop.
How StatusEagle verifies a failure
The trade-off. Verification adds seconds before an alert, not minutes. If a particular monitor needs the fastest possible signal, lower its retry count.
Where StatusEagle checks from
Every plan, including Free, uses 3 monitoring locations. List the three locations (city, country, provider) here Three is enough to answer the question that matters for alerting (is it everyone, or is it one path?). It isn’t a map of how your site performs in every country. If you need per-country performance data, real user monitoring measures it from your actual visitors.
Reading per-location results
| What you see | What it usually means | All locations fail | One location fails repeatedly | One location is always slower | All locations get slower together | Failures rotate between locations |
|---|---|---|---|---|---|---|
| Real outage: server, app, DNS or certificate | ||||||
| Routing or regional CDN problem between that location and you | ||||||
| Distance. Normal, not a problem | ||||||
| Your server or database is under load | ||||||
| Intermittent capacity issue; watch for a pattern |
Related monitoring
Pair these monitoring checks to ensure complete stack coverage.
Frequently asked questions
Still deciding? Start monitoring free and verify your first service in ~2 minutes.
Running the same check from several geographically separate locations, so you can tell a real outage from a local network problem.
Your first monitor takes about two minutes.
Free plan: 10 monitors, 3 locations, 1 status page. No credit card.