I think this might explain it? It sounds like various systems have decided that your Tailscale exit node is in Mexico, and something needs to happen to convince them that it isn't.
Various companies including Google have systems to determine a phone or computer's location via WiFi. To do this they have a table of the approximate locations of routers worldwide.
How does that table get updated? In part it's due to cell phone traffic. If a cell phone's location is determined in some other way (such as via the cell phone network), they will assume any visible router is nearby. So, for example, this would be a way of finding out where a coffee shop's WiFi is.
If, say, a mobile phone is in Mexico (determined via the cell network or GPS) and it's using an exit node in a different country, the inferred router location is going to be wrong. Ironically, using the VPN from Mexico is probably what broke it.
One way to fix it might be to change the exit node somehow. Or maybe connecting to the VPN while at home, using a cell phone, would fix it?
Various companies including Google have systems to determine a phone or computer's location via WiFi. To do this they have a table of the approximate locations of routers worldwide.
How does that table get updated? In part it's due to cell phone traffic. If a cell phone's location is determined in some other way (such as via the cell phone network), they will assume any visible router is nearby. So, for example, this would be a way of finding out where a coffee shop's WiFi is.
If, say, a mobile phone is in Mexico (determined via the cell network or GPS) and it's using an exit node in a different country, the inferred router location is going to be wrong. Ironically, using the VPN from Mexico is probably what broke it.
One way to fix it might be to change the exit node somehow. Or maybe connecting to the VPN while at home, using a cell phone, would fix it?