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...
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...
timestamp1562846400001IPv6 support for API endpointsby Ipregistry TeamIPv6 adoption starts growing quickly. Based on Google reports, almost 30% of the Internet makes use of IPv6. We are happy to announce that IPv6 support for our API endpoint (api.ipregistry.co) has been added this weekend. What does it...
timestamp1546866000001We're starting a changelog 📣by Ipregistry TeamToday we're are thrilled to introduce our product timeline. The purpose of this timeline is to keep you informed about updates and changes we are continuously pushing to Ipregistry. This includes new features, improvements, fixes but...
Subscribe to updatesSubscribe to updates