pings to jolt.co.uk

topher

topher

topher

Soldato
Joined
3 Jan 2003
Posts
3,737
guys what is you responce time to jolt.co.uk
I am getting the below

22
35
51
17

virgin media 4mb

I play fifa 08 online on my PS3 and I used to get 3 green lines, for the last 3/4 weeks I always get 2 yellow lines. Meaning response time has risen. Also playing cod4 (PC) used to get 40ms, now getting 70/85 on the same server.

Virgin wont look into because my ping to virginmedia.com is not more than 500ms !!!!! that is what they told me yesterday.
 
Last edited:
Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=21ms TTL=53
Reply from 82.133.85.65: bytes=32 time=21ms TTL=53

Virgin Media 20mbit.
 
mine with ukfsn....
Code: 
Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=21ms TTL=56
Reply from 82.133.85.65: bytes=32 time=20ms TTL=56
Reply from 82.133.85.65: bytes=32 time=20ms TTL=56
Reply from 82.133.85.65: bytes=32 time=18ms TTL=56

Ping statistics for 82.133.85.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 21ms, Average = 19ms

no doubt someone will be along in a minute with a ping from their datacenter server at <1ms..... :rolleyes: :p
 
Entanet via Aquiss
C:\Users\Trifid>ping jolt.co.uk

Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=13ms TTL=56
Reply from 82.133.85.65: bytes=32 time=12ms TTL=56
Reply from 82.133.85.65: bytes=32 time=13ms TTL=56
Reply from 82.133.85.65: bytes=32 time=12ms TTL=56

Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms

(SE Essex)
 
Mine with VM cable:
Code: 
Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=13ms TTL=54
Reply from 82.133.85.65: bytes=32 time=12ms TTL=54
Reply from 82.133.85.65: bytes=32 time=12ms TTL=54
Reply from 82.133.85.65: bytes=32 time=14ms TTL=54

Ping statistics for 82.133.85.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 14ms, Average = 12ms

If you're experiencing high latency try tracerts and see if you can establish where the latency is being incurred, just pinging it isn't going to tell you a whole lot.
 
Yeah I know m8 just wonder what other people where getting.. did a trace route for VM tech supp yesterday, then they told nothing they can do unless 1 hop is 500ms or more!

Tracing route to jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 49 ms 8 ms 10 ms 10.137.240.1
3 8 ms 23 ms 55 ms bagu-t2cam1-b-v115.inet.ntl.com [80.5.162.189]
4 48 ms 9 ms 17 ms bagu-t3core-1b-ge-011-0.inet.ntl.com [195.182.17
5.29]
5 10 ms 11 ms 18 ms lee-bb-b-so-130-0.inet.ntl.com [80.5.161.157]
6 18 ms 10 ms 25 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 14 ms 44 ms 31 ms pop-bb-b-as1-0.inet.ntl.com [62.253.185.238]
8 13 ms 22 ms 23 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
9 22 ms 35 ms 15 ms 212.250.14.42
10 15 ms 16 ms 53 ms gi2-48-5.ar01.tn5.bb.gxn.net [62.72.140.14]
11 34 ms 24 ms 39 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
12 65 ms 36 ms 31 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.
 
PING jolt.co.uk (82.133.85.65): 56 data bytes
64 bytes from 82.133.85.65: icmp_seq=0 ttl=55 time=33.417 ms
64 bytes from 82.133.85.65: icmp_seq=1 ttl=55 time=34.338 ms
64 bytes from 82.133.85.65: icmp_seq=2 ttl=55 time=34.312 ms
^C
--- jolt.co.uk ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 33.417/34.022/34.338/0.428 ms
 
topher said:
Yeah I know m8 just wonder what other people where getting.. did a trace route for VM tech supp yesterday, then they told nothing they can do unless 1 hop is 500ms or more!

Tracing route to jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 49 ms 8 ms 10 ms 10.137.240.1
3 8 ms 23 ms 55 ms bagu-t2cam1-b-v115.inet.ntl.com [80.5.162.189]
4 48 ms 9 ms 17 ms bagu-t3core-1b-ge-011-0.inet.ntl.com [195.182.17
5.29]
5 10 ms 11 ms 18 ms lee-bb-b-so-130-0.inet.ntl.com [80.5.161.157]
6 18 ms 10 ms 25 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 14 ms 44 ms 31 ms pop-bb-b-as1-0.inet.ntl.com [62.253.185.238]
8 13 ms 22 ms 23 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
9 22 ms 35 ms 15 ms 212.250.14.42
10 15 ms 16 ms 53 ms gi2-48-5.ar01.tn5.bb.gxn.net [62.72.140.14]
11 34 ms 24 ms 39 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
12 65 ms 36 ms 31 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.
Click to expand...

The first few hops are a bit inconsistent so it looks like a local issue. How does your connection perform otherwise, for instance what kind of download speeds do you get? If your area is oversubscribed and your UBR is underperforming that would account for the fluctuating latency.
 
jolt-trace.png
 
The 10.137 etc IP is in one of the RFC1918 ranges - have you got two routers or something?

The problem with latency to each hop is that most machines process ICMP Echo Requests at a low priority, so if they're dealing with any other traffic you're bound to get a poor response time...
 
Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=15ms TTL=54
Reply from 82.133.85.65: bytes=32 time=17ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54

Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 17ms, Average = 16ms


Virgin 20Mb cable thats being binned for BE Value (9.2Mb/1.2Mb sync), no STM and oversubscribing of UBR's....
 
Virgin Media 20Mb Stockport/Manchester while downloading at 2.4 MB/s constant.

Seq Address RX Bytes TTL RTT (ms) +/- (ms)
0 jolt.co.uk (82.133.85.65) 64 54 18.10
1 jolt.co.uk (82.133.85.65) 64 54 15.70 -2.40
2 jolt.co.uk (82.133.85.65) 64 54 17.90 2.20
3 jolt.co.uk (82.133.85.65) 64 54 15.30 -2.60
4 jolt.co.uk (82.133.85.65) 64 54 14.60 -0.70

Round-Trip: 14.6 min, 16.3 avg, 18.1 max (ms)
Packets: 5 transmitted, 5 received, 0% lost
 
VM (blueyonder)

Code: 
Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=15ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=15ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53

Ping statistics for 82.133.85.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 17ms, Average = 15ms
 
You must log in or register to reply here.
Back
Top Bottom