Verzion lag issue is still in the building (probably)

[Suggestion]

Edit, my data is not correct to support this thread, forgive me for my ignorance. I still hope that some true salvation from server lag will be attained in the near future and that the only way to address it is to keep talking about it.

I say this because after SE acknowledged that a large portion of their customers were lagging do to P2p Throttling (i think that was the term) the following 3 days after that, lag progressively showed up later and later. Becoming nonexistent during peak hours. Which was awesome and amazing and i thought about making a thread that dedicated thanks to the dev lords for finally (to my knowledge addressing the issue).

But as of the past two days the lag has returned during peak hours and im forced with a decision to doom fellow dungeon mates with a laggy SMN or log off and call it a night... er afternoon.

Anyroad! This is a trace route from my isp to Zaleras server that i took because i wanted to be sure i was right, even if it was just my computer



Tracing route to 199.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [000.000.0.0]
2 7 ms 4 ms 4 ms L100.DLLSTX-VFTTP-58.verizon-gni.net [173.71.9.1
]
3 11 ms 12 ms 8 ms G0-14-2-3.DLLSTX-LCR-22.verizon-gni.net [130.81.
223.166]
4 * * * Request timed out.
5 6 ms 6 ms 8 ms 0.ae2.BR2.DFW13.ALTER.NET [140.222.225.53]
6 10 ms 9 ms 11 ms ix-20-0.tcore1.DT8-Dallas.as6453.net [66.110.56.
17]
7 67 ms 69 ms 68 ms 64.86.78.5
8 69 ms 67 ms 73 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
1]
9 67 ms 78 ms 68 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
10 112 ms 118 ms 110 ms 66.198.96.50
11 65 ms 66 ms 65 ms 192.34.76.2
12 64 ms 67 ms 76 ms 199.91.189.234
13 * * * Request timed out.