Product Updates Updates

ipregistry.co

timestamp1706270400000

Upcoming Ipregistry Legal Change

by Laurent Pellegrino, Founder and CEO

Happy New Year 2024! Thank you for your continued trust in Ipregistry. Ipregistry is undergoing a legal restructuring to become part of Elaunira, a newly established French company. This change is designed to support our continued growth

timestamp1693393826625

Changes to Pricing Effective October 1, 2023

by Ipregistry Team

Since Ipregistry's launch in 2019, we've worked diligently to offer high-quality services without altering our pricing. This has been part of our ongoing commitment to affordability. However, given the shifts in the economic landscape,

timestamp1650143445783

Introducing VPN detection

by Ipregistry Team

We’re excited to announce VPN detection as a new feature. This is available to everybody! Until now we were detecting abusers, attackers, bogons, cloud providers (datacenters), public proxies, relays, and also tor exit nodes. Starting

timestamp1646516211088

New Ipregistry Subprocessor

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 using

timestamp1640126874700

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 a

timestamp1638884700000

Dedicated EU base URL

by Ipregistry Team

Today, we are introducing a dedicated EU base URL: https://eu.api.ipregistry.co You 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

timestamp1638465005063

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 cause

timestamp1635422100000

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 an

timestamp1628929006833

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 what