Help & guides ›
Advanced monitors
› Per-region latency
Per-region latency
3 min read · Advanced monitors
When you monitor from multiple regions, ePulz.io shows the response time separately for each region. This way you uncover a regional slowdown or outage that would be lost in the overall average - for example the site is fast from the EU but slow from the US.
Prerequisite
Per-region latency works with multi-region monitoring, that is when checks run from multiple geographically separated workers. If you monitor from only one location, a single region is shown.
How it works
- Each regional worker continuously samples the latency (roughly every 5 minutes) and stores it.
- In the monitor detail you see the current status and response time per individual region.
- The samples have a short retention - they serve to show the current difference between regions, not a long history.
What it is good for
- You uncover a CDN or routing problem that affects only some areas.
- You verify that your site is equally fast for customers in different countries.
- During an outage you can tell whether it is global or only in one region (and therefore more likely on the network side than your server).
Tip: per-region latency goes hand in hand with multi-region outage confirmation. We confirm an outage only when more than one region sees it - this filters out false alarms from a single location.
Was this guide helpful?