The 560 GEO Location Not Found error indicates that our system was unable to find an available exit node matching your specified GEO location request. This typically happens when there are no proxies currently available in the country or region you’ve targeted, either due to high demand, limited node availability, or maintenance in that area.
To resolve this issue, start by double-checking that you’ve entered the correct country code in your request. An incorrect or unsupported code could lead to this error. If the country code is correct and you’re still encountering the issue, it may be due to temporary unavailability of nodes in that location.
In such cases, you can either:
Try again later: Node availability can change over time, so retrying your request after a short period may resolve the issue.
Remove GEO targeting parameters: If immediate access is critical, consider removing the GEO location restrictions from your request. This will allow our system to assign an available proxy from a broader pool of nodes.