ping issue - any ideas

darkrage · 10-10-2007, 20:27

please dont say unplug your modem/router - every evening and most of the day i get constant packet loss no matter what server i go on so here is an example ping request and tracert to look at for a jolt.co.uk gaming server.

Pinging 82.133.85.25 with 500 bytes of data:

Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=52ms TTL=118
Reply from 82.133.85.25: bytes=500 time=24ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=44ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=36ms TTL=118
Reply from 82.133.85.25: bytes=500 time=55ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=24ms TTL=118
Reply from 82.133.85.25: bytes=500 time=35ms TTL=118
Reply from 82.133.85.25: bytes=500 time=40ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=46ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=41ms TTL=118
Reply from 82.133.85.25: bytes=500 time=31ms TTL=118
Reply from 82.133.85.25: bytes=500 time=39ms TTL=118
Reply from 82.133.85.25: bytes=500 time=35ms TTL=118
Reply from 82.133.85.25: bytes=500 time=42ms TTL=118
Reply from 82.133.85.25: bytes=500 time=43ms TTL=118
Request timed out.
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=30ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=54ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=55ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=55ms TTL=118
Reply from 82.133.85.25: bytes=500 time=45ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=30ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Request timed out.
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=41ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=34ms TTL=118
Reply from 82.133.85.25: bytes=500 time=30ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=29ms TTL=118
Reply from 82.133.85.25: bytes=500 time=57ms TTL=118
Reply from 82.133.85.25: bytes=500 time=43ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=44ms TTL=118
Reply from 82.133.85.25: bytes=500 time=41ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Request timed out.
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=30ms TTL=118
Reply from 82.133.85.25: bytes=500 time=33ms TTL=118
Reply from 82.133.85.25: bytes=500 time=55ms TTL=118
Reply from 82.133.85.25: bytes=500 time=34ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=44ms TTL=118
Reply from 82.133.85.25: bytes=500 time=49ms TTL=118
Reply from 82.133.85.25: bytes=500 time=44ms TTL=118
Reply from 82.133.85.25: bytes=500 time=42ms TTL=118
Reply from 82.133.85.25: bytes=500 time=32ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=30ms TTL=118
Reply from 82.133.85.25: bytes=500 time=26ms TTL=118
Reply from 82.133.85.25: bytes=500 time=32ms TTL=118
Reply from 82.133.85.25: bytes=500 time=25ms TTL=118
Reply from 82.133.85.25: bytes=500 time=43ms TTL=118
Reply from 82.133.85.25: bytes=500 time=35ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118
Reply from 82.133.85.25: bytes=500 time=28ms TTL=118
Reply from 82.133.85.25: bytes=500 time=31ms TTL=118
Reply from 82.133.85.25: bytes=500 time=27ms TTL=118

Ping statistics for 82.133.85.25:
Packets: Sent = 100, Received = 97, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 57ms, Average = 32ms

C:\Users\Reality>tracert 82.133.85.25

Tracing route to 82.133.85.25 over a maximum of 30 hops

1 6 ms 7 ms 7 ms *.*.*.*.*.*.*
2 8 ms 8 ms 10 ms bagu-t2cam1-a-v108.inet.ntl.com [80.5.162.33]
3 8 ms 10 ms 9 ms bagu-t2core-a-ge-wan63.inet.ntl.com [195.182.175
.9]
4 18 ms 9 ms 27 ms man-bb-a-so-710-0.inet.ntl.com [213.105.174.69]

5 24 ms 42 ms 24 ms gfd-bb-b-so-200-0.inet.ntl.com [62.252.192.94]
6 38 ms 23 ms 23 ms gfd-bb-a-ge-000-0.inet.ntl.com [213.105.172.5]
7 * 56 ms 39 ms pop-bb-b-so-010-0.inet.ntl.com [213.105.172.138]

8 22 ms 31 ms 23 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
9 22 ms 38 ms 14 ms 212.250.14.42
10 51 ms 46 ms 51 ms g2-48-5.ar01.tn5.bb.pipex.net [62.72.140.14]
11 29 ms 25 ms 25 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
12 42 ms 35 ms * 82.133.85.25
13 37 ms 28 ms 46 ms 82.133.85.25

Trace complete.

now looking at this ive got 3% loss over 100 pings transfer 500 bytes of data so if im on that server transfering alot more than this i expect higher loss with spikes - what i do get is constant 5-10% loss and random spikes of 50-100% loss.

now looking at the trace there is an issue at a couple of the servers i route thru (in red) any ideas how to sort this without ringing tech support.

here is a speed test just after the tracert.

Test 1: 1024K took 7140 ms = 143.4 KB/sec, approx 1182 Kbps, 1.15 Mbps
Test 2: 1024K took 7796 ms = 131.3 KB/sec, approx 1082 Kbps, 1.06 Mbps
Test 3: 1024K took 5658 ms = 181 KB/sec, approx 1491 Kbps, 1.46 Mbps
Test 4: 2048K took 13101 ms = 156.3 KB/sec, approx 1288 Kbps, 1.26 Mbps

Overall Average Speed = approx 1261 Kbps, 1.23 Mbps

btw im on 20m dl / 700 up so wtf it looks im restricted to 10% of my lines ability if this is the case then i will email tech support and ask for 90% of my money back each month it happens.