Why does the session location not match where my candidate is based?

The location displayed in session monitoring is derived from IP geolocation, not the candidate's physical location. This means it reflects where the network provider routes the traffic — not where the device actually is.

There are several reasons why the displayed location may differ from the candidate's actual location:

• IP address reallocation – IP addresses are frequently reassigned between regions and providers. A block previously registered to one city or region may still resolve to that location in geolocation databases, even after reallocation.
• Outdated geolocation data – Geo-IP databases are not always current, and mapping can lag behind real-world IP assignments, sometimes by months.
• Mobile network routing – Candidates connecting via mobile data (3G/4G) are assigned an IP by their network provider's infrastructure, which is often centralized in a different region from where the candidate physically is. This is especially common in markets where mobile is the primary means of internet access.

For these reasons, location discrepancies in session monitoring — even large ones — are not necessarily an indicator of any irregularity.

If you have concerns about session integrity, we recommend reviewing the video snippets captured during the assessment. These provide a reliable way to verify that the intended candidate completed the assessment, independent of IP geolocation data.