Hi, for some reason, Google detects Armenian’s exit node country as Nederland:
Location service detects it correctly, though:
Unfortunately, switching Tor circuit doesn’t give a new exit node (if set to Armenia).
What can be a problem and where to report it further?
I think it is because 185.234.57.150 is assigned to AM but is probably owned by a company in NL
I get:
Query: 185.234.57.150
Country: Armenia
ISP: WorkTitans B.V.
Org: WorkTitans B.V
AS: AS209847 WorkTitans B.V.
Proxy: true
Hosting: false
RIPE gives me
Responsible organisation: WorkTitans B.V.
Abuse contact info: abuse@the.hosting
inetnum: 185.234.57.0 - 185.234.57.255
netname: THE-HOSTING
country: AM
Notice WorkTitans B.V. which signals a company in NL
org-name: WorkTitans B.V.
org-type: OTHER
address: Hoge Bothofstraat 39, 7511 ZA Enschede, Netherlands
country: NL
There are probably not many exit nodes in Armenia so switching circuits may not work. In an exit node list I have from about 1 month ago had no exit node in AM
Thanks, but this situation with the location is probably not right?
What can be done with it?
Maybe we can send a note to the exit node admins?
Sorry I’m newbie here do don’t know all the details..
Google sees it as NL and Tor as AM. Guess it depends what database they use. From what I can see Tor uses the IPFire database. I use Maxmind and as of today it says Moldova but their demo site says Central Macedonia in Greece. IP=API says AM. Who is more correct?
OK what is the goal here? Why AM?
A tracert from a Dallas TX based site gives this:
9 169.45.18.167 ae18.bbr01.xn01.fra01.networklayer.com
10 80.81.194.31 frkt-ar2.intl.ip.rostelecom.ru
11 185.140.148.159
12 90.154.106.246 broadband-90-154-106-246.ip.moscow.rt.ru
13 37.186.95.25
14 37.186.95.26
15 185.234.57.150 vm4601994.example.com
As we can see it goes through RU. Now 185.234.57.150 says vm4601994.example.com but that’s fake
Probably the physical location is the truth here, I don’t know.
Just wanted to inform the exit node admins about the accident, maybe they could fix it.
I didn’t see such situation for any other nodes.
I don’t know about this specifically but general experience told me Google do weird shit with their IP database.
I have seen Hong-Kong IP being classified as located in Mainland China because someone setup a proxy there to browse the web but didn’t turn off their phone’s location service, so Google updated this IP’s location with the GPS location they obtained from their phone.
I don’t think it’s necessary to advise anyone. I’m guessing the relay operator knows already. Agreed with Lind above that Google uses it’s own database and it’s wrong on this.
Here is the geofeed of WorkTitans B.V. which says AM
185.234.56.0/24,SI,SI-061,Ljubljana,
185.234.57.0/24,AM,AM-ER,Erevan,
IPFire gives me this which agrees with the geofeed above
net: 185.234.56.0/22
country: MD
net: 185.234.56.0/24
country: SI
aut-num: 209847
drop: yes
net: 185.234.57.0/24
country: AM
aut-num: 209847
drop: yes
Maxmind’s database says it’s geoname_id is 617790 which it translates to MD and is way off geographically.
185.234.56.0/23,617790,617790,0,0,