For users: Report wrong IP geo location here

[jimaek]

If you are hosting a probe and know that the resolved location is incorrect then please report it here. We will use this data to improve our algorithm.
Please do it only if you're fine with making your IP public.

Please comment with:

Real location:
Resolved location:
IP address:

[yoursunny]

Real location: Dallas TX, USA
Resolved location: "(New Zion, US, NA) (lat: 33.7957 long: -80.0148)"
IP address: 108.174.203.*

This is LigaHosting VPS, described to be in Dallas, confirmed via ping latency.

[gshapiro]

Real location: Milpitas, US, NA
Resolved location: Santa Clara, US, NA
IP address: 98.51.131.164

It was close (within 8 miles), not sure what fidelity you are looking for. The probe reported:

[2023-01-13 22:32:50] [INFO] [695] [api:connect] connected from (Santa Clara, US, NA) (lat: 37.3541 long: -121.9552)

[Ne00n]

Real Location: Frankfurt
Resolved Location: Berlin
Probe: Berlin, DE, EU, 210993

[skapytek]

Real Location: Wolfsegg am Hausruck, Upper Austria, Austria
Resolved Location: Laakirchen
Probe: Laakirchen, AT, EU, 8412 -- T-Mobile Austria GmbH
If its not a problem i wont write my IP publicly cause ive installed the probe at my privat home.

[skapytek]

Real Location: Wolfsegg am Hausruck, Upper Austria, Austria
Resolved Location: Laakirchen
Probe: Laakirchen, AT, EU, 8412 -- T-Mobile Austria GmbH
IP: 84.113.52.3

[jimaek]

We released a new version of our geo IP resolution logic. I invite everyone to check their probes and provide us with feedback.

[gshapiro]

We released a new version of our geo IP resolution logic. I invite everyone to check their probes and provide us with feedback.

@jimaek What sort of accuracy are you interested in having reported? My probe geolocation is within 3 miles of actual (though different city).

[jimaek]

3 miles is considered good for us :) Once we release our dashboard you will be able to correct it manually too

[gshapiro]

Real location: Fremont, US, NA (37.4719,-121.9204)
Resolved location: Astoria, US, NA (46.1558,-123.7978)
IP address: 65.19.141.130

(about 750 miles difference)

[jimaek]

Thanks for reporting, it should start showing the correct location very soon, within the next few days once our caches expire and your probe does a scheduled restart.

[alissonlauffer]

Real location: Fortaleza, CE, Brazil (-3.7362,-38.4672)
Resolved location: Lisbon, Portugal (38.7167,-9.1333)
IP address: 185.148.113.186

The probe's geoip seem to be floating between Fortaleza and Lisbon, I'm not sure why though. Probably the company doesn't split the Fortaleza and Lisbon ranges correctly (i.e. 185.148.113.5 is in the same /24 range, but it's in Lisbon).

[jimaek]

Interesting, ipinfo and ip2location show Portugal, only maxmind reports Brazil. I'll look into it, thanks for reporting

[alissonlauffer]

@jimaek hello, any update regarding it? Thanks!

[jimaek]

Unfortunately it will take some time to fix as it's not really an issue with our algorithm but the DBs. I reported the issue to them.

[risturiz]

Real location: Cúcuta, Norte de Santander, Colombia ( maxmind.com )
Resolved location: Barranquilla ( ipinfo.io ) & Pamplona ( ip2location.com )
IP address: 179.32.121.124

[ellieschieder]

Many German nodes report the wrong geolocation. NO node that is hosted by Hetzner should ever get assigned any other location then either Nuremberg or Falkenstein for now. This are there only possible geolocations. Also it’s looks a bit excessive when nearly 50% of my requests get assigned to probes in the same ASN. Even more when they are all hosted by just one provider.

[jimaek]

Hey, thanks for the feedback

1. Geolocation is quite complicated, we want to avoid manual rules per provider and have a system that works for everyone. Based on what I see the majority of Hetzner German locations are correctly assigned to those 2 cities. But there are a few exceptions, I'll try to find out why
2. We're currently working on launching our dashboard. It will allow all probe owners to manage them and fix the location of the probes. I hope this will be enough in most cases
3. "Also it’s looks a bit excessive when nearly 50% of my requests get assigned to probes in the same ASN. " can you give a few examples? Do you mean when you run "from Germany" you get Hetzner too often?

[arraisfilho]

Real location: Araguaína, Tocantins, BR
Resolved location: Brasília, Federal District, BR
IP address: 200.213.107.174

[LindenCX]

Real location: Barcelona, Spain
Resolved location: Scranton, US, NA
IP address: 194.26.100.1

[jimaek]

@LindenCX hey is your probe online and connected? Can you leave it up while we check the issue?

[LindenCX]

@jimaek Not my probe sorry, was just reporting one I commonly see in the US that has high latency to basically everything since it's not in the US.

There's a few more if you want me to drop them here, or I can toss you an email if you prefer with the list.

[jimaek]

Yes please email me [email protected] the IPs and more details about how you made the list. Thanks!