High ping to Virginia servers while residing in Virginia.

This problem has happened once again where all of my traffic is being routed through Marietta Georgia and xfinity refuses to help me until I create this exact same post for the 3rd time. So here it is:

My latency to Virginia servers used to be anywhere around 15-18 ms (im 45 minutes away from the server) Over the past 2 weeks I have noticed that the ping has nearly doubled when connecting to virginia servers(nearly 35-40 ms) This is due to all my traffic being inefficiently routed through Georgia:  7    29 ms    35 ms    30 ms  be-31532-cs03.56marietta.ga.ibone.comcast.net [96.110.43.201].

This was taken from a trace route to a Virginia AWS server. Im not sure why this inefficient route is being taken but it makes overall performance while gaming extremely annoying due to the higher ping and packet loss that has become extremely consistent due to this change.  Im hoping someone can give me an ETA on when the actual efficient route to Virginia servers will be restored. 

FYI I am a network technician and have worked with many ISP's before, I am fully confident that my own hardware and network are not the issue. The issue is all my traffic is being force routed through georgia causing high ping to my nearest server (Ashburn VA).
Here is an update to date trace route showing while removing the first 3 hops: 4 14 ms 21 ms 15 ms ae-96-ar02.staplesmllrd.va.richmond.comcast.net [96.108.140.121] 5 13 ms 11 ms 12 ms 68.86.172.249 6 23 ms 24 ms 22 ms be-31542-cs04.doraville.ga.ibone.comcast.net [96.110.43.205] 7 24 ms 23 ms 27 ms be-2211-pe11.56marietta.ga.ibone.comcast.net [96.110.32.26] 8 * * * Request timed out. 9 26 ms 25 ms 28 ms 172.253.71.61 10 24 ms 23 ms 29 ms 209.85.243.24 11 25 ms 24 ms 25 ms 108.170.229.138 12 38 ms 37 ms 36 ms 142.250.226.241 13 37 ms 36 ms 42 ms 142.250.212.202 14 40 ms 39 ms 38 ms 192.178.99.243 15 37 ms 34 ms 36 ms 108.170.232.201 16 38 ms 36 ms 36 ms mia07s60-in-f14.1e100.net [142.250.217.174]
Furthermore here is a traceroute to an AWS ashburn server when the routes ARE CORRECT and NOT routing through georgia: 

Tracing route to ec2-54-172-63-252.compute-1.amazonaws.com [54.172.63.252] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms  2 9 ms 8 ms 8 ms  10 ms 9 ms 9 ms po-301-1210-rur02.warrenton.va.richmond.comcast.net [69.139.186.229] 4 9 ms 8 ms 8 ms po-2-rur01.warrenton.va.richmond.comcast.net [96.108.140.117] 5 10 ms 20 ms 13 ms ae-96-ar02.charlvilleco.va.richmond.comcast.net [162.151.163.161] 6 10 ms 14 ms 14 ms 96.110.203.233 7 13 ms 14 ms 13 ms be-31522-cs02.beaumeade.va.ibone.comcast.net [96.110.42.133] 8 13 ms 13 ms 13 ms be-3212-pe12.ashburn.va.ibone.comcast.net [96.110.34.118] 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 14 ms 14 ms 14 ms ec2-54-172-63-252.compute-1.amazonaws.com [54.172.63.252] Trace complete. Notice how I am not being routed through georgia in order to ping a virginia server that is physically 45 mins away