Please help diagnose this WISP problem.

Hello,

I am having a fairly poor experience playing quakelive as of late. I am getting some very varied ping times in game that lead to a poor performance on my end and usually get kicked after everyone says I'm "lag scripting."

Here is a ping to a server:

Pinging 74.91.122.20 with 32 bytes of data:
Reply from 74.91.122.20: bytes=32 time=43ms TTL=52
Reply from 74.91.122.20: bytes=32 time=34ms TTL=52
Reply from 74.91.122.20: bytes=32 time=33ms TTL=52
Reply from 74.91.122.20: bytes=32 time=37ms TTL=52
Reply from 74.91.122.20: bytes=32 time=36ms TTL=52
Reply from 74.91.122.20: bytes=32 time=32ms TTL=52
Reply from 74.91.122.20: bytes=32 time=35ms TTL=52
Reply from 74.91.122.20: bytes=32 time=33ms TTL=52
Reply from 74.91.122.20: bytes=32 time=33ms TTL=52
Reply from 74.91.122.20: bytes=32 time=40ms TTL=52
Reply from 74.91.122.20: bytes=32 time=42ms TTL=52
Reply from 74.91.122.20: bytes=32 time=53ms TTL=52
Reply from 74.91.122.20: bytes=32 time=38ms TTL=52
Reply from 74.91.122.20: bytes=32 time=37ms TTL=52
Reply from 74.91.122.20: bytes=32 time=38ms TTL=52
Reply from 74.91.122.20: bytes=32 time=37ms TTL=52
Reply from 74.91.122.20: bytes=32 time=42ms TTL=52
Reply from 74.91.122.20: bytes=32 time=37ms TTL=52
Reply from 74.91.122.20: bytes=32 time=46ms TTL=52
Reply from 74.91.122.20: bytes=32 time=36ms TTL=52
Reply from 74.91.122.20: bytes=32 time=32ms TTL=52
Reply from 74.91.122.20: bytes=32 time=34ms TTL=52
Reply from 74.91.122.20: bytes=32 time=45ms TTL=52
Reply from 74.91.122.20: bytes=32 time=51ms TTL=52
Reply from 74.91.122.20: bytes=32 time=37ms TTL=52
Reply from 74.91.122.20: bytes=32 time=36ms TTL=52
Reply from 74.91.122.20: bytes=32 time=35ms TTL=52
Reply from 74.91.122.20: bytes=32 time=45ms TTL=52

Ping statistics for 74.91.122.20:
Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 53ms, Average = 38ms


And here is a tracert to the same server:

Tracing route to v-74-91-122-20.unman-vds.premium-chicago.nfoservers.com [74.91.122.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.5.1
2 4 ms 11 ms 3 ms 10.11.41.1
3 9 ms 12 ms 12 ms 10.11.10.25
4 8 ms 12 ms 18 ms 67.221.142.229
5 60 ms 65 ms 58 ms 67.221.141.222
6 * 16 ms * 165.254.239.185
7 25 ms 24 ms 36 ms ae-11.r22.dllstx09.us.bb.gin.ntt.net [129.250.6.44]
8 30 ms 11 ms 9 ms ae-2.r07.dllstx09.us.bb.gin.ntt.net [129.250.3.41]
9 13 ms 17 ms 25 ms ae19.dal33.ip4.gtt.net [173.205.60.201]
10 41 ms 40 ms 41 ms xe-4-2-0.chi12.ip4.gtt.net [89.149.185.86]
11 36 ms 42 ms 46 ms internap-gw.ip4.gtt.net [77.67.70.2]
12 37 ms 34 ms 37 ms border10.po1-bbnet1.chg.pnap.net [64.94.32.22]
13 37 ms 36 ms 38 ms inap-b10.e5.router.chicago.nfoservers.com [64.74.97.254]
14 38 ms 61 ms 39 ms v-74-91-122-20.unman-vds.premium-chicago.nfoservers.com [74.91.122.20]

Trace complete.

Is there anything that jumps out with these results? I ping fairly well in cmd prompt, but get huge variance in game.

Please see images for lagometer examples, the green is your ping in game:
http://imgur.com/a/dDUjT

I have a WISP, 15/5 service, get great download speeds and upload speeds most of the time.
Looking for any help whatsoever, thanks. I have had a WISP in the past and had no problems with this before, but recently switched and am looking for any guidance on what may be the problem with mine or WISP's configuration.

Thanks!