But how did I end up getting mislocated by 2,500 km and to the entirely wrong country? These screenshots contain a hint. Notice that the geolocation information thinks I'm on T-Mobile's network. But then notice that the other screenshot thinks I'm on the Rogers network. I'm roaming. Rogers and T-Mobile have (directly or indirectly, again, it's complicated) an agreement such that when T-Mobile's customers are in Rogers' service area, they can connect to Rogers towers. (Actually, it's even more complicated than this, I'm on Google Fi which is not even it's own network, it's a virtual one that runs on T-Mobile plus other providers and ... well you can see why I'm not going to get into it.) There are multiple ways to connection roaming customers' data traffic with the Internet. The simplest one is called "local breakout": my data traffic goes over the air to the Rogers tower, enters the Rogers core network, goes to a Rogers UPF, and exits somewhere locally, almost certainly in Canada, maybe even in Calgary. That's not what's happening here. They are using another strategy here, specifically it appears that they are using Home Routing: my traffic is going into the Rogers network, getting routed back to my "home" network, then using a UPF *there* to connect to the Internet. Carriers often do this because, even though it's a pretty inefficient way to route packets, they want to maintain policy and charging control over their customers' traffic. But that's a subject for another ... paper 😉 @mugaizzo@discuss.systems Why Texas, and not someplace else in T-Mobile's service area? No idea. It might not actually even be in Texas, could be a wrong guess by the geolocation provider. But, that's why I'm an honorary Texan this week. Yeehaw. (Or maybe Yahoo!?)