Product Updates Updates

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

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

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

Usage Monitoring Improvement

by Ipregistry Team
We’ve updated our dashboard with some improvements related to API usage monitoring. Until now, it was possible to see the number of credits consumed in the last 24 hours and the last 31 days. Starting today, you can also get a month by
Dashboard
Enhancement

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
Incident