[Chrysalis]

yep thats too high in my book. Sorry if you disagree but when I last had jitter that high it accompanied speed issues. The way VM run their network I dont think you would get that high jitter without speed issues.

mine below 2 mins ago taken.

C:\>ping -n 10 bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=16ms TTL=117
Reply from 212.58.224.138: bytes=32 time=13ms TTL=117
Reply from 212.58.224.138: bytes=32 time=15ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=19ms TTL=117
Reply from 212.58.224.138: bytes=32 time=12ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=17ms TTL=117

---------- Post added at 21:32 ---------- Previous post was at 21:32 ----------

for the dns server.

C:\>ping -n 10 194.168.4.100

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=8ms TTL=252
Reply from 194.168.4.100: bytes=32 time=9ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=8ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=6ms TTL=252

Ping statistics for 194.168.4.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 9ms, Average = 7ms