The thing is though, it could still happen even if the servers are put in a different location. The issues aren't cropping up and isolated to Montreal. It's rearing it's ugly head at various routing points within the US. We're talking places like Atlanta, Dallas, LA, San Jose, San Diego, Seattle, Chicago, Milwaukee, Jersey, DC, Virginia... others I'm sure I'm forgetting. But they do have something fairly in common: a short list of Internet Service Providers who are unable to efficiently manage the traffic load on their lines. That kind of problem doesn't necessarily disappear just because you move your server. Granted, it has a lot of potential for success in theory---but a lot more is involved here than just moving the server. SE has to have dedicated connections to Japan in the background as well. The NA datacenter is not a standalone farm--it HAS to be in contact with the JP center as well in real time. So, if you start splitting this up into multiple locations now, it becomes a massive logistics nightmare.
More and more it looks like when the communications are good from player to the endpoint, the game runs well. When that communication breaks down, players have issues. Those breakdowns for the most part are happening in the middle, where SE likely can neither identify or address them directly--but the players have a means to at least sniff out clues as to where they may be, and that information can be very useful for the right person to investigate further.
As for the tracert data being posted in here, it is only useful for SE to conduct an investigation if it is sent up the chain. Unfortunately, that doesn't happen often in the user forum sections. The users can forward it through proper channels with the bug reporting pages and sites for both SE and an ISP though. Just because detailed info on a problem is posted here in this forum it doesn't automatically follow that it gets escalated to an actionable phase. That is not how SE intended this forum to function.