timestamp1646516211088
New Ipregistry Subprocessor
by Ipregistry
We are adding Microsoft Azure to our list of subprocessors. The change will be effective on March 15, 2022. No action is required on your part. We’ve updated our Subprocessors page: https://ipregistry.co/gdpr#subprocessors Thanks for usingtimestamp1640126874700
New `is_relay` security field
by Ipregistry Team
We’ve added a new security.is_relay field to responses we return when you look up an IP address (as always, official client libraries have also been updated). The purpose of this new field is to identify IP addresses that are used by atimestamp1638465005063
Delayed usage report on 2021/12/02
by Ipregistry Team
Starting 12:30pm UTC and until 5:15 UTC on December 2, 2021, usage reporting was delayed for some accounts. This incident was not affecting the API. However, the usage displayed on the dashboard was incorrect during the incident. The causetimestamp1635422100000
Introducing Company Data
by Ipregistry Team
We’re continuously working on improving our datasets. Innovation is also an important part. Today, we are introducing company data to provide customers with data on the company behind their IP traffic. API endpoints returning data about antimestamp1628929006833
Unexpected Service Disruption
by Ipregistry Team
The issue is now fully resolved. Customers impacted by automatic renewal have been contacted by email. The disruption was caused by a corruption of our main database storing API keys and credits balance. We are sorry and apologize for whattimestamp1627384498661
Changes about the Connection Type field
by Ipregistry Team
Starting August 3, 2021, we will introduce the value of government for the connection.type field. Due to confusion and low interest with the cdn type classification from the connection field, the value cdn has been merged with hosting. Thistimestamp1620630000000
Renaming for error code PRIVATE_IP_ADDRESS
by Ipregistry Team
Starting June 8, 2021 the error code PRIVATE_IP_ADDRESS will be renamed to RESERVED_IP_ADDRESS. If you are using this error code in your code, we suggest updating as soon as possible your code to check the same behavior is applied whethertimestamp1606723200001
Change regarding API field `security.is_threat`
by Ipregistry Team
The Ipregistry API includes in its responses the field security.isthreat. This field contains as value a boolean that is true if one field evaluates to true among security.isabuser, security.isattacker or security.iscloud_provider...timestamp1597264860001
Usage Alerts by Email
by Ipregistry Team
Starting Today, usage alerts you receive by email before you run out of credits are sent from [email protected]. Make sure this email address is not put to your spam box. Please also note there is an automatic renewal option you can...
Subscribe to updates