Your location is an information that is not usually send by the browser and, I would say, also not by the VPN server. So it's up to the site to try to figure out from where the IP you are using is coming from.
The site can do it by checking the IP range, or by asking a third party service, etc, and all of them is subject to give wrong results.

OK, so slightly strangely, There are no BGP announcements for the parent network - 77.111.244.0/22. It announces each of the /24's in the /22 separately. Not efficient, but common.

Ok, so this (Opera owns HERN) changes nothing major directly.

But it's clear that OPERA owns IPs IN THE US, including: 37.228.104.0/21, 141.0.12.0/22, 185.26.180.0/22. Proof. It COULD use one to host the Americas VPN IP (exit node). How much work that would be is hard to say from here, but Opera's, for example, 10 Gbps peering connection in DC (Ashburn) suggests not much.

That's the point, I don't see how it would help the sites to guess your location correctly.

I never said anything about helping the sites to guess my location correctly (or at least didn't intend to.) (I also never said anything about problems with search engines, other than mentioning google in passing, and please ignore that mention going forward; the workaround for search engines works. It's a kluge, in the worst sense, but it is a working workaround, for search engines only.)

I DID say something about helping the sites to guess my continent or part of the world correctly!

So, can

Well, on the first site the geolocation is correct while in the second it isn't.

Sorry? What are you talking about? Not so. See below for the sites I mentioned; I'm not in Paris, the Ukrain, or Norway. So the first and second and third sites are ALL NOT correct.

@mrelvey said in Bug/WARNING: Opera VPN server location reported is ON WRONG CONTINENT!?:

*https://www.where-am-i.co/my-ip-location says I'm in Paris,
https://www.google.com thinks I'm in the Ukraine, etc.
LastPass thinks I'm in NORWAY. (All three while my server is 77.111.246.20)
I see the network - 77.111.246.0/24 is assigned to HernLabs of Sweden.

@leocg also said:

Now, seeing that only the third section of the IP changes when you change the region, I think that there is a chance that they may be using some virtual IP.

Sorry? Again, what are you talking about? Again, not so. All the IPs start "77.111.246." Are you talking about the FOURTH section of the IP, which, indeed, changes?

Again, the entire /24 network - in which ALL the assigned VPN IPs can be found (AFAIK), whether nominally for the Americas, Europe or Asia - 77.111.246.0/24 - is assigned to HernLabs of Sweden, and is reachable ONLY via HernLabs of Sweden. Proof:

Opera actually owns an ASN - https://bgpview.io/asn/39832 - but these VPN IPs are NOT assigned to that ASN (proof, and thus are not reachable through it. Maybe the terms I'm using are over your head. If you aren't familiar with ASNs, BGP, /24, etc, please bring this to the attention of someone at Opera who IS familiar!
At Opera.com, that is netops@ and/or peering@ !
And at hernlabs.se, that is netops@ !

So I ask: Is Opera willing to send the info to the 2 providers I mentioned that have it VPN IPs all geolocated wrong or not? Alternately, is it willing to (and able to) put them in its ASN?
I think I've explained why, but if it's STILL not clear that Opera has work to do to fix VPN geolocation problems, or how what I'm asking for would help with the problem I'm reporting (which is that the IPs are all in the same /24, which is only reachable via Sweden, let me know.

Update: Hold on... Opera OWNS Hern Labs. So that changes things a bit. Will edit above if I still can. Otherwise, see any newer posts from me first.

Well, on the first site the geolocation is correct while in the second it isn't.

Now, seeing that only the third section of the IP changes when you change the region, I think that there is a chance that they may be using some virtual IP.

The problem of sites guessing wrongly from where you are connecting from is difficult for them to fix because it's not an Opera or VPN issue.

[edit:]: and here: db-ip.com/report/ ?

I see that in that post from 10 months ago, a staff member says "We're working on a proper fix".

It's already there and it's called 'bypass VPN for default search engines'.

http://blogs.opera.com/desktop/2018/01/opera-50-introduces-anti-bitcoin-mining-tool/#comment-3693794894

I see that in that post from 10 months ago, a staff member says "We're working on a proper fix".

https://www.iplocation.net shows some useful-to-such-a-fix info:

Geolocation data from IP2Location (Product: DB6, updated on 2018-11-1)
IP Address Country Region City
77.111.246.196 United States Virginia Ashburn
ISP Organization Latitude Longitude
Opera Software AS Not Available 39.0437 -77.4875

Geolocation data from ipinfo.io (Product: API, real-time)
IP Address Country Region City
77.111.246.196 Norway Not Available Not Available
ISP Organization Latitude Longitude
HERN Labs AB HERN Labs AB 59.9500 10.7500

Geolocation data from EurekAPI (Product: API, real-time)
IP Address Country Region City
77.111.246.196 Europe - -
ISP Organization Latitude Longitude
Opera Software AS Opera Software AS 47.0 8.0

Geolocation data from DB-IP (Product: Full, 2018-11-2)
IP Address Country Region City
77.111.246.196 Sweden Östergötland Linköping (Innerstaden)
ISP Organization Latitude Longitude
HERN Labs AB Hernlabs 58.4116 15.6268

So, IP2Location gets it right, as does EurekAPI , but the other two get it wrong. Clearly, a fix would be for Opera (or perhaps a user?) to contact the other two! Links on the actual page... Hello, https://disqus.com/by/michaowicki/? @michaowicki ? Looks like @Michał left Opera very shortly after posting that. Any idea who's working on it, @leocg? Good to pass that info on in case the right person(s) don't have it/forgot about this bug.

Geolocation data from IP2Location (Product: DB6, updated on 2018-11-1)
IP Address Country City
66.249.69.90

This is really really strange - this is NOT my real IP address or my VPN IP address.

...OK I UNDERSTAND! Google is showing me CACHED CONTENT - hence the info is the IP of google's web spider.

See http://blogs.opera.com/desktop/2018/01/opera-50-introduces-anti-bitcoin-mining-tool/#comment-3693794894

Also see the several other topics on this subject opened in these forums

That is as good as it gets, unfortunately.

See also https://forums.opera.com/post/157572