[Synthetic]

Thanks SP

Interestingly, i'm no longer being routed to the VM cache, and everything is fine...

C:\Users\xx>tracert akadash0.akamaized.net

Tracing route to a1160.w10.akamai.net [88.221.87.131]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.88.1
2 12 ms 14 ms 8 ms 10.53.34.249
3 11 ms 12 ms 10 ms gate-core-2a-xe-501-0.network.virginmedia.net [82.2.240.105]
4 * * * Request timed out.
5 * * * Request timed out.
6 27 ms 24 ms 25 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
7 * * * Request timed out.
8 23 ms 23 ms 26 ms uk-lon03a-ri1-ae-2-0.aorta.net [84.116.135.46]
9 30 ms 24 ms 24 ms 213.46.174.130
10 24 ms 29 ms 26 ms ae8-xcr1.lnt.cw.net [195.2.24.130]
11 30 ms 29 ms 29 ms ae4-ucr1.mcr.cw.net [195.2.27.166]
12 30 ms 30 ms 30 ms 217.161.88.254
13 29 ms 29 ms 27 ms a88-221-87-131.deploy.static.akamaitechnologies.com [88.221.87.131]

Trace complete.

Not really sure what is going on here but pinning down is becoming a nightmare, the trend does seem to be the issue only appears when using the VM cache in particular, very strange.