176 karma · joined July 18, 2019
To further validate our assumptions - try to use google maps daily for at least 2 weeks while in Seattle using that exit IP. Logic tells me that it should update once more to the new location (I'd think it's unlikely to be a once off update due to the dynamic nature of IP).
in my case I have a family member sharing my VPN endpoint (DNS blocking does wonders on iOS) - which was part of the initial puzzle as I didn't use any google services at that point.
Not a path forward but a workaround - rotate the IP periodically and start "fresh".
Something to note though - in my post I never mentioned the "real IP" - all tests were done to change the geoIP data of the VPN IP - and that always works as expected.
It's definitely updated on GeoIP as it's device independent (eg: a laptop using the same exit IP will automatically be redirected to that country when it changes).
This actually happened to me. I'm using a persistent VPN (50% to access my private infrastructure and 50% because I have a hostile ISP).
I mostly don't use any Google services (maybe one google search a month and the occasional google map search but I avoid when I can) and I was very surprised when once I did a google search and saw my postal code at the end of the page. The IP address was for a VPS (in the same city but with a different post code). I found it unusual but didn't pay too much attention. A few months later I moved places (different post code) and after a while google had my new post code at the end of their search page. That's when I found it troubling and assumed that a family member's iPhone was using Google Maps and based on the 'directions' usage they figured out that that IP address has a home address for those GPS coordinates. (The iPhone in question is reasonably 'hardened' with background updates off and location services only 'when app opened' and disabled for most system services). That was the only plausible correlation between IP address and location google could have done automatically - neither I nor the said family member no longer login to old google accounts we had many years back.
That's when I started rotating IP daily (which is trivial in my case as I use lightsail, I issue a shutdown from a different server and then a power on, AWS rotates the IP automatically out of a very large pool - so far I haven't gotten the same IP twice).
The only problem I have with lightsail is that I often get a 'dirty' IP so I rotate 4-5 times before getting a good one (I test this by going a curl on a website that sends google captcha on dirty IPs but lets the 'good' ones straight in).
I periodically (every 10 minutes) rsync everything across to another VPS (different provider). (you can use mysql replication, mysqldump, etc)
Every hour I run an rsync with --link-dest to a storage VPS and once a month I tar everything up (I take the midnight backup of each day) and it goes to long term storage. The resulting archive is only marginally (10-20%) more than the real size on disk as it mostly contains diffs on top of the actual data. I can failover easily between instances if the primary one goes down so it's reasonably highly available.
If you want less complexity you can use the S3 backend (IIRC nextcloud supports encrypted data at rest) and just ensure that's backed up regularily. Nextcloud itself has versioning for changed data.