Product Updates Updates

Product Updates Updates

ipregistry.co

Updates to Third-Party Subprocessors

by Laurent Pellegrino, Founder and CEO
We’re updating our third-party subprocessor list. These changes are being made to enhance the resilience and redundancy of our services and will go into effect on April 1, 2024. New Subprocessors: Oracle Cloud
Announcement

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
Announcement

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,
Announcement

Improved Filtering Options

by Ipregistry Team
With Ipregistry you can create multiple API keys to manage different concerns and track usage independently but more importantly, you can also define restrictions per API key from the Ipregistry dashboard. Restrictions are optional but
Enhancement

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 using
Announcement

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
API
New

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
Incident