The returned result is as follows:
{
“ip”: “0.0.0.0”,
“bogon”: true
}
However, since we called a paid API, this resulted in significant additional charges, and this result is of no help to us. How should we handle this? Is it possible to negotiate a partial reduction of the excess fees?
Hi,
Thank for posting on the community. Can you tell me what you mean by “significant additional charge”, please? When you are on a paid subscription, we count each valid request against your quota.
If you are querying a private or a bogon IP address, it counts as a valid request.
ow many requests did you make to get IP info on bogon IPs?
— Abdullah | DevRel, IPinfo
It is estimated that there will be approximately seven million times.
Moreover, the bill is unreasonable. The bill for the period from October to December last year was issued in January, which prevented us from promptly tracking our consumption situation.
We subscribed to the monthly package, but due to the failure to disable the automatic over-limit billing, some abnormal requests were not promptly intercepted, resulting in a large number of calls to the charging interface. Only when a large amount of deduction bill was generated did we realize that the unreasonable outflow of additional fees beyond the limit occurred. This seriously prevented us from promptly disabling the automatic over-limit billing. Could we negotiate to reduce some of the fees? Because the amount is simply too large and it has exceeded the budget significantly.
Hi,
Talk with our support team, please: https://ipinfo.io/support
The community is not designed for critical commercial conversations. Please talk to our support team; they will investigate and find a solution for you.
— Abdullah | DevRel, IPinfo
1 Like