FlowData

Why does IP Geolocation show my server's location instead of my visitor's?

Published on 10. November 2026

You've added IP Geolocation or Client Info to your website, but every request returns the same city, the same network operator or a data center? Then you're most likely seeing the data of your own server. That's not a FlowData problem; it comes down to who actually sends the request.

Why this happens

FlowData only ever sees the connection that reaches it. Because your key doesn't belong in the browser, you call the APIs from your server, so to FlowData your server is the sender, not the visitor to your website.

  • GET https://api.flowdata.one/v1/geolocation without an IP in the path locates the IP address the request comes from. From your backend, that's the address of your server or hosting provider.
  • GET https://api.flowdata.one/v1/client-info reads the IP address, browser and language from the incoming request. Without anything else, the response describes your server and the program it uses to make the request.

You can spot this quickly in the area's Log: click the eye icon on a request. IP address and User agent show who really asked. If you put the visitor's IP address in the path, these two fields still show your server, because it sent the request. That's exactly how it should look.

How to get your visitor's data

  1. In your own application, read the visitor's IP address. Most frameworks have a ready-made function for this. If your website runs behind a proxy or CDN, make sure the function returns the forwarded visitor address and not the proxy's.
  2. Query IP Geolocation with exactly that address in the path:
curl "https://api.flowdata.one/v1/geolocation/203.0.113.24?lang=en" \
  -H "Authorization: Bearer fd_YOUR_KEY"
  1. For browser, device and language, pass your visitor's headers on to Client Info. How do I detect browser, device and language with Client Info? shows how.

Why do 192.168.x.x or 10.x.x.x return status fail?

Addresses like 192.168.1.20, 10.0.0.5 or 172.16.0.1 are private, and 127.0.0.1 is reserved. They exist in countless local networks at the same time, so they can't be tied to a place. If you query such an address, you get "status": "fail" with HTTP 200, and message says private range or reserved range. These responses aren't billed.

If you see private addresses in your data, your application is usually reading the address of an internal proxy or load balancer instead of the visitor's. Check which header your proxy sets for the real visitor address.

How accurate is locating by IP?

Locating by IP is always an estimate. Country and region are usually right for fixed-line connections, while the city is often only an approximation. The coordinates rarely point to an address and more often to the middle of a town or area. On mobile networks, company networks and VPN services, the location shown can be far from the real one.

The fields mobile, proxy and hosting are always null, so they don't help here. The network operator in org gives a hint: if it's a hosting or cloud provider, the request is more likely from a data center than from a person.

Good to know

Was this article helpful?

Back to IP Geolocation & Client Info