NTL bad pings

wideband

Connections has been like this for me about afortnight now in the tallaght area....no joy with customer care :mad:

Anyone else have difficulties and reported them??

Tracing route to www.jolt.co.uk over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.2.2
2 66 ms 197 ms 54 ms 10.135.55.254
3 50 ms 83 ms 39 ms dbln-cam-1b-ge02-101.inet.ntl.com [82.9.147.9]
4 41 ms 71 ms 88 ms dbln-t2core-b-ge-210-0.inet.ntl.com [82.9.145.129]
5 69 ms 33 ms 74 ms dbln-bb-b-ge-230-0.inet.ntl.com [213.105.174.57]
6 54 ms 187 ms 61 ms man-bb-a-so-500-0.inet.ntl.com [213.105.174.45]
7 89 ms 59 ms 58 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 147 ms 119 ms 81 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
9 79 ms 422 ms 154 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
10 266 ms 117 ms 57 ms tele-ic-2-so-110-0.inet.ntl.com [62.253.185.74]
11 94 ms 156 ms 63 ms lon1-10.nildram.net [213.208.106.169]
12 75 ms 82 ms 48 ms 84.12.225.130
13 72 ms 55 ms 158 ms jolt-gw.nildram.net [195.149.20.126]
14 70 ms 67 ms 81 ms 82.133.85.65
Trace complete.

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from : bytes=32 time=129ms TTL=50
Reply from : bytes=32 time=71ms TTL=50
Reply from : bytes=32 time=93ms TTL=50
Reply from : bytes=32 time=114ms TTL=50

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

causal

Umm I wouldn't post your internal IP addresses if I were you - delete the first few entries from your traceroute

ping www.jolt.co.uk

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=74ms TTL=50
Reply from 82.133.85.65: bytes=32 time=65ms TTL=50
Reply from 82.133.85.65: bytes=32 time=28ms TTL=50
Reply from 82.133.85.65: bytes=32 time=27ms TTL=50

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

ping www.boards.ie

Pinging www.boards.ie [82.195.136.36] with 32 bytes of data:

Reply from 82.195.136.36: bytes=32 time=56ms TTL=47
Reply from 82.195.136.36: bytes=32 time=66ms TTL=47
Reply from 82.195.136.36: bytes=32 time=44ms TTL=47
Reply from 82.195.136.36: bytes=32 time=47ms TTL=47

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

That's in D.16 on ntl750:128
Your pings are a tad high.
causal

lee_baby_simms

Tue, 03 May 2005 21:18:36 GMT
1st 128K took 1512 ms = 86688 Bytes/sec = approx 721 kbits/sec
2nd 128K took 4777 ms = 27438 Bytes/sec = approx 228 kbits/sec
3rd 128K took 1632 ms = 80314 Bytes/sec = approx 668 kbits/sec
4th 128K took 1472 ms = 89043 Bytes/sec = approx 741 kbits/sec

Im on the 750 package in cabinteely.

mad m

Pinging www.jolt.co.uk with 32 bytes of data:

Request timed out.
Reply from 82.133.85.65: bytes=32 time=29ms TTL=51
Reply from 82.133.85.65: bytes=32 time=25ms TTL=51
Reply from 82.133.85.65: bytes=32 time=26ms TTL=51

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 29ms, Average = 26ms


Kimmage area.750k also

causal

^^^^^ 1 packet lost! That's unusual for ntl

causal

mad m

@causal

Well just ran the ping again and still one packet loss.You dont want to see my Tracert to jolt.Maybe its bad weather in UK with the rain,or there upgrading the network to the new speeds?.Seen couple of blokes outside house friday and this morning from a Communications company.

causal

I just ran mine again and they're better than earlier:

TIME - AvgPing - Destintation
21:27 - 48ms - www.jolt.co.uk
21:27 - 53ms - www.boards.ie
23:59 - 26ms - www.jolt.co.uk
23:59 - 39ms - www.boards.ie

ping www.jolt.co.uk

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=26ms TTL=50
Reply from 82.133.85.65: bytes=32 time=27ms TTL=50
Reply from 82.133.85.65: bytes=32 time=25ms TTL=50
Reply from 82.133.85.65: bytes=32 time=27ms TTL=50

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

ping www.boards.ie

Pinging www.boards.ie [82.195.136.36] with 32 bytes of data:

Reply from 82.195.136.36: bytes=32 time=37ms TTL=47
Reply from 82.195.136.36: bytes=32 time=39ms TTL=47
Reply from 82.195.136.36: bytes=32 time=41ms TTL=47
Reply from 82.195.136.36: bytes=32 time=39ms TTL=47

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

So it seems that it's something local to your connection - the dreaded 'blokes working on...'

causal

mad m

well here you go see what you think now,

Pinging www.boards.ie [82.195.136.36] with 32 bytes of data:

Reply from 82.195.136.36: bytes=32 time=41ms TTL=48
Reply from 82.195.136.36: bytes=32 time=42ms TTL=48
Reply from 82.195.136.36: bytes=32 time=51ms TTL=48
Reply from 82.195.136.36: bytes=32 time=36ms TTL=48

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


Horah!

causal

Maybe they heard us and fixed it
Well you've no choice now but to test those pings with some online gaming

causal

wideband

causal wrote:

Umm I wouldn't post your internal IP addresses if I were you - delete the first few entries from your traceroute
[

made it up