[graf_von_anonym]

Just because one ping in a tracert spikes doesn't necessarily mean there's a problem. The ping can be high because the unit is busy. That's why I'm recommending you try a pathping.

Also, are you directly connected to the modem? I know you've said that you have, but that tracert runs through 192.168.1.1, which is a Netgear Router.

Using tools.virginmedia.com I can ping your 10.*.*.* IP address without incident. That's a ping originating within the VM network. The odds of oversubscription are pretty slender since you're on 50Mb, so the possible causes are: signal, which I think we can discount because you're seeing slow speeds rather than packet loss; routing, which is not entirely under VM's control; DNS delay; misinterpretation of test results.

You've been told that equipment within the network is often busy routing data rather than responding to ping requests, and that can produce high spikes in the results. You'll notice that the spikes within the network are higher than the ping times to your target site. If network routing equipment responded to ping requests or tracert requests as a first priority that would negatively affect everybody's speeds, so it's not going to do that. That's one reason why you could be seeing those spikes. This is why I would recommend using the pathping command. It gives us more details to try and help you.

Finally, while it may not matter what server you ping, the fact that you're going through VM is not the only common factor. Your DNS, PC, router, they are all still the same, and any of those could be having an influence. It's bad practise to start with a solution and then find evidence to support it.

So, again, try a pathping. I'd also recommend posting your modem signal levels, though if you're the newsgroup poster I think you are someone has had a look at those for you. Could you use ipconfig/all in the command prompt and tell us your DNS entries?