timestamp1581667200001Uniform region code formatby Ipregistry TeamRegion/subdivision codes returned in Ipregistry data sets and API (field location.region.code) are now all based on the ISO 3166-2 standard. If needed, we also provide complete and up-to-date ISO 3166 countries and subdivisions data in...
timestamp1570461300001Incorrect Email Reportsby Ipregistry TeamSome of you may have received an email reporting the wrong number of weekly or monthly request calls to our API. We apologize for the inconvenience. Be reassured, the issue is now fixed and it was only affecting email reports: your...
timestamp1568101140001Usage Chart Per API Keyby Ipregistry TeamWe allow creating multiple API keys to keep different concerns isolated (e.g. projects). Although the dashboard includes a chart that shows the cumulative usage for all API keys, some of you have expressed the need to check usage per API...
timestamp1567062900001Error Code for Bad Inputsby Ipregistry TeamIt has been reported that inputting an invalid request body value for the batch lookup endpoint (using the POST method) was returning an HTTP 500 error. This was not impacting the service but confusing users. We have introduced a new...
timestamp1564477200001Throttling per Client IPby Ipregistry TeamWe've improved our Rate limit/throttling feature. Once enabled, the rate limit feature was limiting the total number of requests that can be made per hour for a given API key. It was possible to have a user that consumes 10,000 look...
Subscribe to updatesSubscribe to updates