Oh... and just for comparison sake, here is a ping to that same address, but instead of using the IP address I used the URL of one of the sites that points you to the same IP:

Code:
C:\Windows\System32>ping www.justcause2.com -n 10

Pinging www.justcause2.com [184.107.107.176] with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=44ms TTL=49
Reply from 184.107.107.176: bytes=32 time=42ms TTL=49
Reply from 184.107.107.176: bytes=32 time=46ms TTL=49
Reply from 184.107.107.176: bytes=32 time=44ms TTL=49
Reply from 184.107.107.176: bytes=32 time=45ms TTL=49
Reply from 184.107.107.176: bytes=32 time=42ms TTL=49
Reply from 184.107.107.176: bytes=32 time=44ms TTL=49
Reply from 184.107.107.176: bytes=32 time=44ms TTL=49
Reply from 184.107.107.176: bytes=32 time=44ms TTL=49
Reply from 184.107.107.176: bytes=32 time=42ms TTL=49

Ping statistics for 184.107.107.176:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 46ms, Average = 43ms
In that short test, the average jitter was again just under 2ms (1.8) for around 4% of the average (4.19%), and again the average falls close to the middle of the Min/max range. Still would prefer it to be a bit tighter, but it is still much more manageable.