-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Waiting time too long or Bad Gateway returns #69
Comments
Seeing the same thing. Started about a week or so ago with the get statement (we use axios) the response time is way down and will time out. manually typing api.ipify.org into the browser this morning I received the Bad Gateway but then refreshed and got the IP. Sometimes it responds fast for a bit then similar issues. |
I have the same problem, I changed to the version https://api64.ipify.org/ which is more stable but still fails. |
Experiencing the same. Sent them a message through their Geolocation API website where they promote paid services. |
Reply from IPIFY: "We have some problems with our service, api.ipify.org, that cause a long-time-response issue. We are working to fix it, and the response time will recover to normal value in the near future. All our paid services (including IP geolocation API or VPN & Proxy Detection API) have dedicated servers and don't have such problems. Unfortunately, we have no paid alternative for api.ipify.org, so we have to wait until our technical team resolves this issue." |
It is currently taking too long to get the IP with this api https://api.ipify.org
The text was updated successfully, but these errors were encountered: