it could be multiple things
a) yes it could be a virus eating up the connection (by using up most of your bandwidth) but you would tend to notice anomylous results such as
Pinging
www.bbc.net.uk [212.58.224.114] with 32 bytes of data:
Reply from 212.58.224.114: bytes=32 time=740ms TTL=245
Request timed out
Reply from 212.58.224.114: bytes=32 time=420ms TTL=245
Request timed out
this could be a virus or incorrectly configured Peer 2 Peer software (or a problem on the ntl network)
if you had something like this...
Reply from 212.58.224.114: bytes=32 time=22ms TTL=245
Request timed out
Reply from 212.58.224.114: bytes=32 time=23ms TTL=245
Request timed out
i wouldnt think there would be a virus using up your connection
it could be that a virus (if you do have one) or piece of software is using all your bandwidth and the connection is so slow that it is timing out on the ping... one way of doing this would be to use this ping statement
ping -t -w 5000
www.bbc.co.uk
this would then make the ping request wait 5000ms before timing out
i wouldnt be too concerned with AVG not updating as recently the AVG free version servers have been under so much load that it does take a lot to update its definitions, something that has been mentioned here in the last few months.
there are however a number of things on the ntl network which could also cause these problems (such as a low SNR) but without further investigation it would be hard to tell (and we assume that the tech support agent has checked this)