Ping spikes all over when connecting to a certain ip

My ping to this gaming server I manage is normally 30-40. It is now spinking nearly double. How are you able to correct this? Since upgrading to gigabit, we have had nothing but lag, lag and more lag. Traceroute is as follows:

C:\WINDOWS\system32>pathping 51.81.48.224

Tracing route to ns1003428.ip-51-81-48.us [51.81.48.224]
over a maximum of 30 hops:
0 DESKTOP-N6I9THO.hsd1.tn.comcast.net [10.0.0.234]
1 10.0.0.1
2 96.120.108.57
3 69.139.205.53
4 68.85.206.121
5 162.151.94.93
6 be-33112-cs01.56marietta.ga.ibone.comcast.net [96.110.43.81]
7 be-1112-cr12.56marietta.ga.ibone.comcast.net [96.110.34.210]
8 be-301-cr11.chicago.il.ibone.comcast.net [96.110.37.162]
9 be-1111-cs01.chicago.il.ibone.comcast.net [96.110.36.17]
10 be-1112-cr12.chicago.il.ibone.comcast.net [96.110.36.34]
11 be-301-cr13.350ecermak.il.ibone.comcast.net [96.110.38.209]
12 be-1213-cs02.350ecermak.il.ibone.comcast.net [96.110.35.37]
13 be-2204-pe04.350ecermak.il.ibone.comcast.net [96.110.37.38]
14 chi-1-a9.il.us [142.44.208.125]
15 be100-1316.ash-1-a9.va.us [198.27.73.87]
16 vl1332.was1-vin1-g1-nc5.wa.us [178.32.135.211]
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-N6I9THO.hsd1.tn.comcast.net [10.0.0.234]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 96.120.108.57
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 69.139.205.53
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% 68.85.206.121
0/ 100 = 0% |
5 24ms 0/ 100 = 0% 0/ 100 = 0% 162.151.94.93
0/ 100 = 0% |
6 30ms 0/ 100 = 0% 0/ 100 = 0% be-33112-cs01.56marietta.ga.ibone.comcast.net [96.110.43.81]
0/ 100 = 0% |
7 39ms 0/ 100 = 0% 0/ 100 = 0% be-1112-cr12.56marietta.ga.ibone.comcast.net [96.110.34.210]
0/ 100 = 0% |
8 38ms 0/ 100 = 0% 0/ 100 = 0% be-301-cr11.chicago.il.ibone.comcast.net [96.110.37.162]
0/ 100 = 0% |
9 39ms 0/ 100 = 0% 0/ 100 = 0% be-1111-cs01.chicago.il.ibone.comcast.net [96.110.36.17]
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% be-1112-cr12.chicago.il.ibone.comcast.net [96.110.36.34]
0/ 100 = 0% |
11 38ms 0/ 100 = 0% 0/ 100 = 0% be-301-cr13.350ecermak.il.ibone.comcast.net [96.110.38.209]
0/ 100 = 0% |
12 31ms 0/ 100 = 0% 0/ 100 = 0% be-1213-cs02.350ecermak.il.ibone.comcast.net [96.110.35.37]
0/ 100 = 0% |
13 39ms 0/ 100 = 0% 0/ 100 = 0% be-2204-pe04.350ecermak.il.ibone.comcast.net [96.110.37.38]
100/ 100 =100% |
14 --- 100/ 100 =100% 0/ 100 = 0% chi-1-a9.il.us [142.44.208.125]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% be100-1316.ash-1-a9.va.us [198.27.73.87]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% vl1332.was1-vin1-g1-nc5.wa.us [178.32.135.211]

Trace complete.

C:\WINDOWS\system32>tracert 51.81.48.224

Tracing route to ns1003428.ip-51-81-48.us [51.81.48.224]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 10 ms 8 ms 11 ms 96.120.108.57
3 12 ms 9 ms 28 ms 69.139.205.53
4 18 ms 15 ms 12 ms 68.85.206.121
5 30 ms 20 ms 30 ms 162.151.94.93
6 31 ms 28 ms 37 ms be-33112-cs01.56marietta.ga.ibone.comcast.net [96.110.43.81]
7 30 ms 28 ms 28 ms be-1112-cr12.56marietta.ga.ibone.comcast.net [96.110.34.210]
8 37 ms 37 ms 37 ms be-301-cr11.chicago.il.ibone.comcast.net [96.110.37.162]
9 42 ms 39 ms 38 ms be-1111-cs01.chicago.il.ibone.comcast.net [96.110.36.17]
10 39 ms 38 ms 38 ms be-1112-cr12.chicago.il.ibone.comcast.net [96.110.36.34]
11 39 ms 39 ms 41 ms be-301-cr13.350ecermak.il.ibone.comcast.net [96.110.38.209]
12 40 ms 39 ms 36 ms be-1213-cs02.350ecermak.il.ibone.comcast.net [96.110.35.37]
13 40 ms 38 ms 37 ms be-2204-pe04.350ecermak.il.ibone.comcast.net [96.110.37.38]
14 58 ms 59 ms 59 ms chi-1-a9.il.us [142.44.208.125]
15 60 ms 60 ms 67 ms be100-1316.ash-1-a9.va.us [198.27.73.87]
16 61 ms 62 ms 63 ms vl1332.was1-vin1-g1-nc5.wa.us [178.32.135.211]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 61 ms 59 ms 61 ms ns1003428.ip-51-81-48.us [51.81.48.224]

Trace complete.