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:
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.
]]>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 month usage overview for the last 12 months:
The option is available for the chart displaying your global account usage on the main dashboard page, but also for usage monitoring per API key. This allows you to get a better understanding of your usage over a longer period of time.
Note that we started collecting monthly usage in April, 2021 so if you do not see data prior this date, that’s normal.
]]>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 month usage overview for the last 12 months:
The option is available for the chart displaying your global account usage on the main dashboard page, but also for usage monitoring per API key. This allows you to get a better understanding of your usage over a longer period of time.
Note that we started collecting monthly usage in April, 2021 so if you do not see data prior this date, that’s normal.
]]>
Besides, It is no longer required to make a purchase before enabling automatic renewal. However, you need to set up a payment method.
If you enabled automatic renewal in the past, we used information from your last purchase to set the pack of credits and the payment method to use with upcoming renewals. Regarding the renewal threshold, it is set to 10% of the number of credits included in the pack you last bought. For instance, if 700,000 credits were bought with your last payment, your renewal threshold is set to 70,000, meaning that if your number of credits goes below this threshold, then a renewal is triggered.
We suggest looking at the new options and configure them based on your needs. As always, your feedback is welcome!
Note that Enterprise customers are not affected by this change.
]]>Besides, It is no longer required to make a purchase before enabling automatic renewal. However, you need to set up a payment method.
If you enabled automatic renewal in the past, we used information from your last purchase to set the pack of credits and the payment method to use with upcoming renewals. Regarding the renewal threshold, it is set to 10% of the number of credits included in the pack you last bought. For instance, if 700,000 credits were bought with your last payment, your renewal threshold is set to 70,000, meaning that if your number of credits goes below this threshold, then a renewal is triggered.
We suggest looking at the new options and configure them based on your needs. As always, your feedback is welcome!
Note that Enterprise customers are not affected by this change.
]]>