apilayer / ipapi Goto Github PK

Currently the IPv4 block 206.1.86.0/23 is showing the geolocation at Russia, however this block is currently geolocated at:

Country: Colombia
Region: Antioquia
City: Rionegro

This information is actually updated on internet registries but remains out of date on APILAYER, please see: https://whois.arin.net/rest/net/NET-206-1-86-0-1/pft?s=206.1.86.254

Current geolocation provided by APILAYER:

"country_name": Russia 
"state_prov": Ural Federal District 
"city": Surgut 
"latitude": 61.25505 
"longitude": 73.43602 
"time_zone": Asia/Yekaterinburg 
"isp": PSINet, Inc. 
"currency": Russian Ruble ```

What is the difference between ipapi.com and ipstack.com?

At least one IP address (164.90.174.228) is being given an incorrect geolocation from IPAPI, as seen in a query on this page: https://www.iplocation.net/ip-lookup

It shows this erroneous / outdated geolocation data:

164.90.174.228 | United States🇺🇸 | Washington | Issaquah
Digitalocean LLC | Not Available | 47.569351196289 | -121.77702331543

Only the ISP "Digitalocean" is correct. This IP address is in Germany: DigitalOcean's Frankfurt am Main data centre. You can find our correct IP location and post code from this official database: https://www.digitalocean.com/geo/google.csv

164.90.160.0/20 DE DE-HE Frankfurt 60341

This request is fairly urgent because any host we have in this IP range will be part of a global network using real-world coordinates to estimate propagation delays in a dynamically generated P2P topology.

Incorrect location for 23.247.211.0/24

This is a local internet service provider.

Correct Location: Waxahachie, TX USA

See geofeed at: https://www.fiberfly.com/geofeed.csv

Company website: https://fiberfly.com

the ip address 212.178.231.138 has given an incorrect geoloaction from IPAPI when seen as a query on this page : https://ipapi.com/

It shows 43.8296012878418

LONGITUDE
20.481830596923828

IP Location: Serbia (RS)
CITY, STATE
Čačak (Central Serbia)

ZIP CODE
32224

LANGUAGE
Serbian (SR)

CALLING CODE
+381

TIME ZONE
CEST

CURRENCY
Serbian Dinar (din.)

When using https://ipapi.co/?utm_source=google&utm_term=ipapi&utm_campaign=862321563&adgroupid=46098134600&device=c&utm_medium=cpc&utm_content=445058769074&gclid=CjwKCAjwi8iXBhBeEiwAKbUofQ_-JBhfm4b3NbDQ2rq8a5BjxHzCFgxPpt9-PhSSNjUQWjbC2rrP3xoC9KYQAvD_BwE
it brings up the correct information.

At the moment, documentation says:

Your API access key is private and should at no time be shown publicly.

Yet, on the same page, there is an example with jQuery where this key is exposed to anyone looking at browser dev tools:
$.ajax({ url: 'https://api.ipapi.com/' + ip + '?access_key=' + access_key, ..... } });
I used to work with the previous API version in a similar way, but now it's actually impossible, and in order to hide the access_key, I need to perform api calls from the server side - which is not that good idea, especially, when the website traffic goes high.
I understand the idea of monetizing the service - but this part reduces it value to possible users quite significantly.
Can't think of a solution right away - but firstly, I wonder if the authors see a problem with it as well.

Urgent: We are currently using your API in our application for user sign up and users who are within our state are getting denied access from our app because their IP address is being listed as if they are in a different state. This is only happening in select cases but not with every one of our users. Is this a known bug and are there any current fixes that can be implemented? Thank you for any help that can be provided.

Is there a way to stop adblockers from triggering when making a request to ipAPI

our company purchase (https://ipapi.com) standard plan yearly but not getting timezone data in response.since last two day that is happening.