timestamp1589875200001Dashboard Enhancementsby Ipregistry TeamHere are the enhancements that have been deployed: API keys are now hidden by default. You can download receipts for payments made with cards. A few bugs affecting slow connections have been fixed. All buttons are disabled when an...
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...
timestamp1580511600001The United Kingdom left the European Unionby Ipregistry TeamThe United Kingdom left the European Union on 31 January 2020, at midnight. This change is reflected in the Ipregistry API and data sets. The field ineu is returning true_ for the remaining 27 state members: Austria, Belgium, Bulgaria...
timestamp1579065120001IP lookups are now returning the routing prefixby Ipregistry TeamFollowing recent requests, it was expressed a need to get the routing prefix associated with an IP address. This data is now included under the field connection.route for all API calls that return IP data. The value uses the CIDR...
timestamp1577977320001New field value CDN for connection typeby Ipregistry TeamHappy New Year! We wish you the best for 2020. Last year was incredible and we are looking forward to continue innovating in the IP and cyber-security domains with you. It was not possible to start this year without announcing something...
timestamp1572430080001New currency data 💱by Ipregistry TeamThe API has been updated to include 2 new fields in the currency section: namenative and pluralnative. The existing fields name and plural are returning, respectively, the currency name and plural name in US locale. The new fields...
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...
timestamp1565265600001More Data Points!by Ipregistry TeamIt was awaited by most of you. We've deployed a big update that brings new data points. Thanks to the hard work we made these last weeks to correlate and analyze data, we are proud to announce new data fields! The API is returning a new...
Subscribe to updatesSubscribe to updates