My VPN expired. Back to rubberbanding when the servers are busy.

[Jmeat]

I play with a few people that have this issue, they are also on Verizon FIOS. They pretty much don't login anymore and when they do they have to use a VPN service that they pay for. I don't blame them for not wanting to play. It is frustrating neither side is interested doing anything to fix the offending node(s) (SE opening talks/VZ working with Level 3).

It has been like this since patch 2.1 went live. I've compared my trace routes with them and they hit the same nodes as me as the hops near SE's NA/EU datacenter and for some reason the 5th (Usually) from the last hop is the offending node. (4.69.141.1). This is the traceroute from my ISP that is not VZ FIOS (I don't have the issue). I'm sure if folks on FIOS did the same traceroute their ae-11-11.car2.Montreal2.Level3.net node would have insane ping times as the packets travel through the offending node and onto SE's servers.

 13    40 ms    40 ms    40 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
 14    41 ms    40 ms     *     ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
 15    40 ms    40 ms    41 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]