Thread: [NA] Issues Occurring After Patch 2.16 and the Addressing Thereof (Mar. 5)
THey have actually been actively trying to address stability issues they've been able to identify on their end for a while now. The last few maintenances have included changes hoping to resolve some of them. Tonight's is another such attempt.
As to your in route latency... that is something for your ISP to address. And yes, they CAN address it. Getting them to investigate and take action is another story, but it actually is their responsibility. They set up the service agreements for third parties to carry your data off of their lines, and those agreements provide them with a means of enforcement when that third party's service goes south and begins to impact a client's quality of service. If your ISP did not enter into negotiations with these third parties to carry your data across to other networks, you would not be able to access content or even send email to someone using a different ISP--they have to pay someone to connect the dots for them, and with that comes a means to influence them to clean up their act.
The trick is in identifying the symptoms in your routing (tracerts) to your game server (Canada based NA/EU servers start with 199, not the web server starting with 184 that is plastered all over the web), as well as to other common services like Google/YouTube, Netflix, or even another game's server and then forwarding that data to your ISP's tier3 via their support portal/contacts. You may have to be persistent and lean on them.. but they CAN affect changes in your routing to get around some if not all of the congested paths. The fact that a VPN/proxy service can mitigate the issue is proof that such changes will work... and SE has no power over the decisions your ISP and their partners make in routing you from point A to point B. That is all dictated by your ISP and their partner(s) routing policies and analytics.