As per an earlier reply, you need to state where you are trying to reach - what is the target for the traceroute?
The statement you received that everything from VM is routed via New York is nonsense, although each of the big organisations could have servers or data centres across the globe.
For examples, I used bbc.co.uk as suggested in another earlier reply. That's not very specific as it could point, did a look up, to various servers.
It resolved to using IP address 151.101.64.81 which is in the US (since the BBC use some services from Fastly including their CDN solutions I believe) - and that routed from my router to some servers apparently in the US via some VM servers.
I then used 212.58.224.0 as the specific target as this is said to be a BBC IP address. That routed me via some VM servers listed as being in Scotland to an IP address of 132.185.249.10 which is listed as being for the BBC in the UK (Maidenhead). Pretty reasonable - no mention of New York whatsoever! See below
traceroute to 212.58.224.0 (212.58.224.0), 64 hops max, 40 byte packets
1 dlinkrouter (192.168.0.1) 1.222 ms 0.679 ms 0.624 ms
2 10.53.39.125 (10.53.39.125) 7.928 ms 10.226 ms 10.307 ms
3 80.255.195.186 (80.255.195.186) 12.651 ms 12.277 ms 11.955 ms
4 * * *
5 80.255.204.81 (80.255.204.81) 12.731 ms 13.235 ms 15.404 ms
6 cpc2-macc3-2-0-gw.1-3.cable.virginm.net (213.104.12.1) 12.754 ms 17.984 ms 16.285 ms
7 ae0.pr01.eqsl.bbc.co.uk (132.185.249.10) 37.897 ms 15.412 ms 17.380 ms
8 132.185.249.12 (132.185.249.12) 14.465 ms 15.899 ms 14.388 ms
Note that the physical location for servers might not be as they seem - it's how they are registered by their owners and so on....
So, what site are you trying to access and seeing these higher latency figures for? What else might have changed following your upgrade? Post a traceroute with a target of 212.58.224.0