Originally Posted by
Bariaus
Chile here. Had the same issue back then, same ISP, and the problem is located in the hops within Europe, specifically in Spain and some jumps between Netherlands/France post SE servers migration. This is weird and back then my guess it was that it's still related to SE. Why? Because pre migration, jumps within Europe - which were still present - didn't yield this extra +150 ms, and it was like so because the route it took to, consequentially reach US to Canada servers was a different one, with less jumps and different hosts hops. Post migration, everyone seems to be tied to NTT nodes, which also affect our ISP routing, and it's definitely the culprit here. One can say "Well it's your ISP fault for choosing that way" or "Well it's SE's fault for switching its servers, knowing about this node changes issue", but let's be honest: None of them were/are aware of this and also they don't give an f about this issue, because when you put this in balance, the earnings of the company are much more than what they're losing by this issue.
We all know the alternative solution so I suggest you to go with what I told you on that other sub-- er unnofficial forum..sub.
Edit: There was a margin of time (months) where those 3XXms went down to 220 or so, but still, not optimal to play even casually. Now yes, it's back to the numbers you're stating.