Today is the first day I've experienced severe lag spikes in game or even going LD. Three times in succession. Ideas?

Tracing route to uthgard.game-server.cc [88.198.56.21]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 7 ms 7 ms L100.NRFLVA-VFTTP-28.verizon-gni.net [173.71.xxx.x]
3 8 ms 6 ms 7 ms G0-3-3-2.NRFLVA-LCR-21.verizon-gni.net [130.81.183.40]
4 50 ms 49 ms 46 ms so-0-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.22.40]
5 18 ms 16 ms 17 ms 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
6 14 ms 15 ms 14 ms ae17.edge1.washingtondc12.level3.net [4.68.62.137]
7 18 ms 16 ms 16 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
8 17 ms 17 ms 16 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
9 99 ms 99 ms 99 ms ae-44-44.ebr2.Paris1.Level3.net [4.69.137.61]
10 107 ms 106 ms 106 ms ae-45-45.ebr1.Frankfurt1.Level3.net [4.69.143.133]
11 134 ms 111 ms 106 ms ae-71-71.csw2.Frankfurt1.Level3.net [4.69.140.6]
12 153 ms 116 ms 145 ms ae-2-70.edge3.Frankfurt1.Level3.net [4.69.154.71]
13 * 139 ms 111 ms HETZNER-ONL.edge3.Frankfurt1.Level3.net [212.162.40.206]
14 116 ms 117 ms 164 ms hos-bb1.juniper1.rz13.hetzner.de [213.239.240.240]
15 113 ms 111 ms 112 ms hos-tr2.ex3k11.rz13.hetzner.de [213.239.224.44]
16 112 ms 111 ms 117 ms uthgard.game-server.cc [88.198.56.21]

Trace complete.

I also ran a ping -t to the server and watched it for a bit. I occasionally saw some time spikes or time-outs.


Pinging 88.198.56.21 with 32 bytes of data:
Reply from 88.198.56.21: bytes=32 time=109ms TTL=112
Reply from 88.198.56.21: bytes=32 time=110ms TTL=112
Reply from 88.198.56.21: bytes=32 time=113ms TTL=112
Reply from 88.198.56.21: bytes=32 time=115ms TTL=112
Reply from 88.198.56.21: bytes=32 time=139ms TTL=112
Reply from 88.198.56.21: bytes=32 time=253ms TTL=112
Reply from 88.198.56.21: bytes=32 time=277ms TTL=112
Reply from 88.198.56.21: bytes=32 time=113ms TTL=112
Reply from 88.198.56.21: bytes=32 time=112ms TTL=112
Reply from 88.198.56.21: bytes=32 time=109ms TTL=112
Reply from 88.198.56.21: bytes=32 time=115ms TTL=113
Request timed out.
Request timed out.
Reply from 88.198.56.21: bytes=32 time=118ms TTL=112
Reply from 88.198.56.21: bytes=32 time=109ms TTL=112
Reply from 88.198.56.21: bytes=32 time=115ms TTL=113

Ping statistics for 88.198.56.21:
Packets: Sent = 126, Received = 124, Lost = 2 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 277ms, Average = 116ms



And a longer sample of ping -t. I imagine the "destination unreachable" would be where I'd of gone LD.


Reply from 88.198.56.21: bytes=32 time=154ms TTL=112
Reply from 88.198.56.21: bytes=32 time=256ms TTL=112
Request timed out.
Reply from 88.198.56.21: bytes=32 time=113ms TTL=112
Reply from 88.198.56.21: bytes=32 time=109ms TTL=112
Reply from 88.198.56.21: bytes=32 time=115ms TTL=113
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: Destination host unreachable.
Reply from 192.168.1.1: Destination host unreachable.
Reply from 192.168.1.1: Destination host unreachable.
Reply from 88.198.56.21: bytes=32 time=1116ms TTL=112
Reply from 88.198.56.21: bytes=32 time=114ms TTL=113Reply from 88.198.56.21: bytes=32 time=110ms TTL=112
Reply from 88.198.56.21: bytes=32 time=118ms TTL=112
Request timed out.

Ping statistics for 88.198.56.21:
Packets: Sent = 601, Received = 593, Lost = 8 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 1116ms, Average = 118ms

I had red squares this evening (PST US), and a lot of lag. A lot more than usual. No LD's though. I am in Nevada.

my performance meter was a constant pair of gunshot wounds

Pingplotter image below. Can anyone point out where the problem might be? My intial hop (Hop 2) to verizon? That starts the initial 3% packet loss more or less i'm thinking. My Latency obviously jumps once I cross the pond at Hop 9, but it looks like the only standout packet loss %'s are 10, 11, 13 as they are in the 4%+. Regardless, going LD blows. So I think my initial problem might be stemming from my very first hop out of my house at Hop 2. No? If so I can coordinate with my ISP as it's verizon and maybe I can get it fixed.

Disagree? Or does my hop path just generally suck? I wish I had a sample from before ld'ing started 2 nights ago to compare.