Interestingly my ping has now fallen back to my original 50 ms. Seems that whatever the issue was with the servers I was being routed through has been resolved. The ae7 has significantly decreased latency now, so that may have been the issue. Glad to have more normal ping back, for now anyway lol.

Tracing route to 204.2.229.106 over a maximum of 30 hops

1 1 ms * 2 ms [192.168.0.1]
2 * * * Request timed out.
3 10 ms 9 ms 11 ms rc3ar-be105-1.ed.shawcable.net [64.59.186.57]
4 11 ms 20 ms 17 ms 66.163.70.129
5 13 ms 14 ms 13 ms rc3no-be6.cg.shawcable.net [66.163.64.69]
6 29 ms 29 ms 29 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
7 28 ms 29 ms 30 ms ae-7.a00.sttlwa01.us.bb.gin.ntt.net [168.143.229.41]
8 29 ms 28 ms 28 ms ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
9 28 ms 28 ms 29 ms ae-5.r23.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
10 47 ms 47 ms 46 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
11 53 ms 53 ms 53 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
12 * * * Request timed out.
13 56 ms 56 ms 57 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 56 ms 55 ms 57 ms 204.2.229.234
15 50 ms 49 ms 48 ms 204.2.229.106

Trace complete.