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.
]]>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.
]]>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 contact us.
]]>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 contact us.
]]>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.
]]>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.
]]>Restrictions are optional but enable:
Controlling what IP addresses can use your API key
Defining what websites origins can use your API key
Rate limiting the number of requests per hour
Until now IP filtering was only supporting IP addresses per entry. You can now enter a CIDR subnet and select whether you want to allow or deny the specific IP addresses or CIDR subnets.
Similarly, you now have the option to choose whether the specified origins are either allowed or denied.
To manage restrictions, click on “API Keys” in the left navigation bar of the Ipregistry dashboard. Then, select “Settings” for the desired API key and apply the changes you want:
Restrictions are optional but enable:
Controlling what IP addresses can use your API key
Defining what websites origins can use your API key
Rate limiting the number of requests per hour
Until now IP filtering was only supporting IP addresses per entry. You can now enter a CIDR subnet and select whether you want to allow or deny the specific IP addresses or CIDR subnets.
Similarly, you now have the option to choose whether the specified origins are either allowed or denied.
To manage restrictions, click on “API Keys” in the left navigation bar of the Ipregistry dashboard. Then, select “Settings” for the desired API key and apply the changes you want:
Until now we were detecting abusers, attackers, bogons, cloud providers (datacenters), public proxies, relays, and also tor exit nodes. Starting today, we are adding VPN IP addresses detection to the list. Our VPN dataset contains several millions of IP addresses updated daily.
The new field is named is_vpn and appears under the security object of API responses we return.
As always, we'd love to hear your thoughts on this new feature as well as what you'd like us to build next! Leave us a reaction or feedback below.
]]>Until now we were detecting abusers, attackers, bogons, cloud providers (datacenters), public proxies, relays, and also tor exit nodes. Starting today, we are adding VPN IP addresses detection to the list. Our VPN dataset contains several millions of IP addresses updated daily.
The new field is named is_vpn and appears under the security object of API responses we return.
As always, we'd love to hear your thoughts on this new feature as well as what you'd like us to build next! Leave us a reaction or feedback below.
]]>No action is required on your part. We’ve updated our Subprocessors page: https://ipregistry.co/gdpr#subprocessors
Thanks for using Ipregistry.
]]>No action is required on your part. We’ve updated our Subprocessors page: https://ipregistry.co/gdpr#subprocessors
Thanks for using Ipregistry.
]]>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 relay node. Unlike VPNs, relay nodes are location-aware. Instead of bypassing geo-controls, a relay node pools multiple users behind the same IP address.
Using relay nodes is a manner to protect the identity and privacy of users behind individual IPs. Currently, we identify relay IP addresses from Apple Private Relay (APR).
When the new field is_relay returns true as value, then you know the request comes from devices making use of a relay node.
With the end of the year that’s also the time for us to thank you for an amazing 2021. See you in January, and have a wonderful holiday season!
]]>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 relay node. Unlike VPNs, relay nodes are location-aware. Instead of bypassing geo-controls, a relay node pools multiple users behind the same IP address.
Using relay nodes is a manner to protect the identity and privacy of users behind individual IPs. Currently, we identify relay IP addresses from Apple Private Relay (APR).
When the new field is_relay returns true as value, then you know the request comes from devices making use of a relay node.
With the end of the year that’s also the time for us to thank you for an amazing 2021. See you in January, and have a wonderful holiday season!
]]>https://eu.api.ipregistry.coYou 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 transferred outside.
Indeed, when you send a request to endpoints using the new base URL, your request is forwarded to the closest Ipregistry node in Europe via an anycast load balancer. Then, the EU node process your request but associated data is not transferred outside Europe.
All existing endpoints and options described in our docs work the same.
Note that using our new dedicated EU base URL makes sense if you have users or servers in Europe. However, if your users or servers are located for instance in the US, you will experience higher latencies. In that case, you should keep our default base URL.
]]>https://eu.api.ipregistry.coYou 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 transferred outside.
Indeed, when you send a request to endpoints using the new base URL, your request is forwarded to the closest Ipregistry node in Europe via an anycast load balancer. Then, the EU node process your request but associated data is not transferred outside Europe.
All existing endpoints and options described in our docs work the same.
Note that using our new dedicated EU base URL makes sense if you have users or servers in Europe. However, if your users or servers are located for instance in the US, you will experience higher latencies. In that case, you should keep our default base URL.
]]>This incident was not affecting the API. However, the usage displayed on the dashboard was incorrect during the incident.
The cause of the issue has been identified. The incident is resolved and the usage reported on your dashboard is now correct (including the period that was under issue).
]]>This incident was not affecting the API. However, the usage displayed on the dashboard was incorrect during the incident.
The cause of the issue has been identified. The incident is resolved and the usage reported on your dashboard is now correct (including the period that was under issue).
]]>The batch endpoint was accepting up to 256 IP addresses per request until recently. Starting today, we’ve increased this limit to 1024.
To give you an idea about how fast and powerful our API is, let’s assume you are sending requests in parallel using 8 threads from a node that has about 40ms latency to our API, then you can resolve 600,000 IP lookups in one minute or less.
]]>The batch endpoint was accepting up to 256 IP addresses per request until recently. Starting today, we’ve increased this limit to 1024.
To give you an idea about how fast and powerful our API is, let’s assume you are sending requests in parallel using 8 threads from a node that has about 40ms latency to our API, then you can resolve 600,000 IP lookups in one minute or less.
]]>