A healthy local check is only one view
Your site loads quickly from your office, but a customer elsewhere reports long waits. Both observations can be correct. Network paths, regional infrastructure, and the distance to your service can produce different experiences for the same URL.
PageLantern lets you select monitoring locations for a monitor and inspect the response-time evidence they return. That gives you a practical starting point for investigating whether a slowdown appears across locations or is concentrated in a particular part of the journey.
Choose locations with a purpose
Use Monitoring locations when creating or editing a monitor. Choose from the locations available in the product, starting with the markets your customers depend on. Each selected location runs at the monitor’s interval and uses one monitoring slot, so review the displayed slot count before saving.
There is also a primary location: the first selected location, with the home location taking priority when selected. Begin with a small, useful set and expand when another location would answer a specific operational question. More measurements are most useful when you know what you want to compare.
Compare readings without hiding the gaps
The monitor’s Location performance range brings regional readings together so you can inspect response times and locations outside the normal range. Compare the same period across locations before deciding whether the problem is widespread.
A selected location with no measurements stays visible as No data. That distinction matters: missing observations do not establish that a service was healthy, and they should not look like a successful check with zero latency. If a location has no readings, investigate the gap before drawing a regional conclusion.
Use the evidence to narrow the next check
If one location is consistently slower, compare that finding with your CDN, hosting, and application evidence. If all measured locations slow down together, start with the shared service path. Regional monitoring helps direct that investigation; a response-time difference alone does not prove its cause.
Available locations can change, and an offline probe location may use an infrastructure fallback. These fallbacks do not consume an extra monitoring slot. Review the location information alongside the measurements so you understand the observation you are using, then adjust your selection as your customer footprint changes.