https://eu.api.ipregistry.coYou can use it in replacement of our default base URL (https://api.ipregistry.co) to ensure your requests and related data are processed in Europe and not transferred outside.
Indeed, when you send a request to endpoints using the new base URL, your request is forwarded to the closest Ipregistry node in Europe via an anycast load balancer. Then, the EU node process your request but associated data is not transferred outside Europe.
All existing endpoints and options described in our docs work the same.
Note that using our new dedicated EU base URL makes sense if you have users or servers in Europe. However, if your users or servers are located for instance in the US, you will experience higher latencies. In that case, you should keep our default base URL.
]]>https://eu.api.ipregistry.coYou can use it in replacement of our default base URL (https://api.ipregistry.co) to ensure your requests and related data are processed in Europe and not transferred outside.
Indeed, when you send a request to endpoints using the new base URL, your request is forwarded to the closest Ipregistry node in Europe via an anycast load balancer. Then, the EU node process your request but associated data is not transferred outside Europe.
All existing endpoints and options described in our docs work the same.
Note that using our new dedicated EU base URL makes sense if you have users or servers in Europe. However, if your users or servers are located for instance in the US, you will experience higher latencies. In that case, you should keep our default base URL.
]]>