Encountering the same stuff again this morning. I did the pingpath test and a tracert test also. The ping meter on the minimap was fluctuating and more than once it went into the red at almost 3000ms. The character would run into an invisible boundary that only dissipates with the latency spike. Not less than an hour beforehand, I was streaming 1080p video from youtube for a short while without a hiccup. Unfortunately it looks like pathping isn't detecting/recording anything beyond the first ISP router hop.
C:\WINDOWS\system32>pathping -n 159.153.65.151
Tracing route to 159.153.65.151 over a maximum of 30 hops
0 192.168.1.2
1 192.168.1.1
2 70.110.24.1
3 130.81.220.228
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.2
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 70.110.24.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% 130.81.220.228
Trace complete.
C:\WINDOWS\system32>tracert 159.153.65.151
Tracing route to 159.153.65.151 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 7 ms 6 ms L100.WASHDC-VFTTP-99.verizon-gni.net [70.110.24.1]
3 10 ms 13 ms 8 ms G1-6-4-2.WASHDC-LCR-21.verizon-gni.net [130.81.220.228]
4 * * * Request timed out.
5 10 ms 9 ms 9 ms 0.ae3.BR2.IAD8.ALTER.NET [140.222.227.195]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 12 ms 11 ms 12 ms 4.79.23.202
11 12 ms 11 ms 12 ms 159.153.92.82
12 9 ms 9 ms 9 ms 159.153.65.151
Trace complete.
Any idea? I will try out wtfast the next time i'm playing and its happening