Product Updates Updates

Updates to Third-Party Subprocessors

2024-02-29T22:59:53.336Z

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 Infrastructure
Hetzner
HostHatch

Removed Subprocessors:

Coinbase Commerce
Mailgun

For more information about the specific tasks performed by each subprocessor, please refer to our updated Subprocessors List.

We appreciate your continued business and are committed to providing you with the most reliable and secure services possible. If you have any questions or concerns, please do not hesitate to contact us.

Upcoming Ipregistry Legal Change

2024-01-26T12:00:00Z

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 and does NOT involve any change in ownership or management.

We will continue to deliver the same level of service you've come to expect, with the same team remaining dedicated to your needs.

Important Update Regarding Billing Information

As a result of this legal restructuring, Ipregistry/Elaunira, in collaboration with Stripe, will now be responsible for collecting Value Added Tax (VAT). This means it's crucial that you review your billing information to ensure it's current and accurate.

By taking a moment to verify your information, you'll help us maintain compliance and keep your service uninterrupted.

If you have any questions, please don't hesitate to [email protected]" rel="noopener nofollow" target="_blank">contact us.

Changes to Pricing Effective October 1, 2023

2023-08-30T11:10:26.625Z

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, including inflation and rising operational costs, we're facing the need to adapt.

To continue delivering the quality, performance, and innovations you've come to expect from Ipregistry, we are modifying our pricing structure beginning October 1, 2023. Your continued use of Ipregistry services starting this date constitutes your acceptance of these changes.

What's changing?

Beginning October 1, 2023, a new pricing will apply to our standard pay-as-you-go offer (note that Enterprise plans will remain unaffected). Although the price points for the packs remain constant, the number of credits each pack contains will change as detailed below:

Current pack (USD)	Current credits	New credits
$5	40k	discontinued
$10	100k	50k
$50	700k	400k
$100	2M	1M
$500	11M	6M

The new pricing will be automatically applied to all purchases made on or after October 1, 2023, including those triggered by auto-renewal. Please be aware that the $5 pack will be discontinued and replaced by the $10 pack.

Stock up now to save

If you would like to purchase credit packs at the current rates, you have until September 30, 2023, to do so. Rest assured credits in your account will continue to be valid and can be used at any time until they are fully consumed.

We recognize that price changes are never welcome news, but we hope you understand that this adjustment is necessary for us to continue innovating and providing you with the high-quality services you expect.

New Ipregistry Subprocessor

2022-03-05T21:36:51.088Z

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 Ipregistry.

Changes about the Connection Type field

2021-07-27T11:14:58.661Z

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. This means you will see the value hosting for entries with connection.type field that had value cdn in the past.

Official client libraries have been updated. We suggest upgrading to the latest version as soon as possible, especially with the Java library since old versions were not supporting new connection type values (this is fixed and parsing is now more robust with the latest version).

Renaming for error code PRIVATE_IP_ADDRESS

2021-05-10T07:00:00Z

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 whether the old or the new error code is returned.

For instance, if you have something like this:

if ("PRIVATE_IP_ADDRESS".equals(exception.code)) { ... }

You should update your code to something like that:

if ("PRIVATE_IP_ADDRESS".equals(exception.code) ||
"RESERVED_IP_ADDRESS".equals(exception.code)) { ... }

Then, after the date mentioned above, you can safely remove the conditional statement that involves the old error code.

Change regarding API field `security.is_threat`

2020-11-30T08:00:00.001Z

The Ipregistry API includes in its responses the field security.is_threat. This field contains as value a boolean that is true if one field of the following fields evaluate to true:

security.is_abuser
security.is_attacker
security.is_cloud_provider.

After February 1, 2021 the Ipregistry API will set the value associated with security.is_threat to true if the field security.is_abuser or the field security.is_attacker evaluates to true. In other words, the field security.is_cloud_provider will no longer be taken into consideration.

In the case you rely on this field and you want to keep the behavior unchanged after the date above, we suggest updating your code right now as follows:

security.is_threat OR security.is_cloud_provider

Usage Alerts by Email

2020-08-12T20:41:00.001Z

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 enable if you pay by cards via Stripe. You just need to enable the option from your dashboard:
https://dashboard.ipregistry.co/credits/buy

Once done, purchase a pack so that Stripe knows what card and pack to use for reloading. We’ll charge your card automatically for the same pack when less than 10,000 credits or 3 days usage are left based on your last hour usage. Obviously, you can cancel at any time.

Minor changes regarding credits consumption

2020-05-25T09:55:00.001Z

Starting June 1, 2020, the following changes will apply:

Bulk endpoints will consume 1 credit plus as many credits as IP addresses you input. Currently, it is consuming as many credits as IP addresses you input. The difference is one additional credit per bulk endpoint call.
Looking up private IP addresses will consume 1 credit. Currently, performing a lookup for a private IP address is free of charge.

The change should make almost no differences for legitimate usages of our API but will allow us to keep the infrastructure safe and prevent some recent abuses we noticed.

Service outage ⚠️

2020-03-30T08:55:00.001Z

We experienced a service outage starting this morning at 2:27 AM GMT due to somebody who intentionally compromised our systems. The team has worked hard restoring the services.

An investigation is in progress to identify what has been corrupted. All necessary changes will be made to ensure this does not happen again.

We sincerely apologize for the issue. Thanks for your patience and trust during these hard times.

Update: the breach has been identified and fixed, logs have been analyzed, the service is fully restored and a security audit has been performed. Thanks again for your patience and understanding.