PDA

View Full Version : Is this normal ....

dunkyb
23-06-2006, 16:39
Ok,

Ive been battling my connection for ages now, and am still seeing completely unstable pings... Someone at NTL network tech told me this was due to QoS etc on the routers.. Fair enough, so pinging the uBR isnt a good test. So i've pinged ntlworld.com on his recommendation, and am getting:

Pinging ntlworld.com [212.250.162.47] with 32 bytes of data:
Reply from 212.250.162.47: bytes=32 time=33ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=27ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=15ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=16ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=18ms TTL=121
Reply from 212.250.162.47: bytes=32 time=17ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=14ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=25ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=15ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=14ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=18ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=36ms TTL=121
Reply from 212.250.162.47: bytes=32 time=26ms TTL=121
Reply from 212.250.162.47: bytes=32 time=17ms TTL=121
Reply from 212.250.162.47: bytes=32 time=20ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=13ms TTL=121
Reply from 212.250.162.47: bytes=32 time=24ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=19ms TTL=121
Reply from 212.250.162.47: bytes=32 time=36ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121

Ok so the actual responses are OK, it's not yet hit peak time... but they're all over the place? Is this all i can expect on cable, or do I have a problem like noise ingress somewhere?

Sometimes they peak into the 100ms ranges.

Cheers

Duncan
dunkyb
23-06-2006, 17:10
Is this normal on an NTL cable connection?

Pinging www.ntlworld.com (http://www.ntlworld.com) [212.250.162.47] with 32 bytes of data:
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=18ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=23ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=16ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=45ms TTL=121
Reply from 212.250.162.47: bytes=32 time=15ms TTL=121
Reply from 212.250.162.47: bytes=32 time=36ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=21ms TTL=121
Reply from 212.250.162.47: bytes=32 time=28ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=21ms TTL=121
Reply from 212.250.162.47: bytes=32 time=8ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=47ms TTL=121

Ok response times are OK, but they are completely sporadic.... I am pinging from a completely idle connection.

I even get stable pings to it from AMERICA.....

PING www.ntlworld.com (http://www.ntlworld.com) (212.250.162.47) 56(84) bytes of data.
64 bytes from www.ntlworld.com (http://www.ntlworld.com) (212.250.162.47): icmp_seq=1 ttl=110 time=98.4 ms
64 bytes from www.ntlworld.com (http://www.ntlworld.com) (212.250.162.47): icmp_seq=2 ttl=110 time=97.3 ms
64 bytes from www.ntlworld.com (http://www.ntlworld.com) (212.250.162.47): icmp_seq=3 ttl=110 time=99.8 ms
64 bytes from www.ntlworld.com (http://www.ntlworld.com) (212.250.162.47): icmp_seq=4 ttl=110 time=98.1 ms
64 bytes from www.ntlworld.com (http://www.ntlworld.com) (212.250.162.47): icmp_seq=5 ttl=110 time=97.3 ms
64 bytes from www.ntlworld.com (http://www.ntlworld.com) (212.250.162.47): icmp_seq=6 ttl=110 time=97.5 ms

How can they tell me there's no issue with the connection, I'm on the NTL network and they definitely aren't!

Am i just sniffing large upstream congestion or something here, or do you recon there's noise ingress or something else causing an issue?

Cheers.
MovedGoalPosts
23-06-2006, 17:15
I've merged your posts - no need for two separate threads on the same issue.

As for whether it's OK or not. I'll leave that to a technical bod ;)
dunkyb
23-06-2006, 17:22
I didn't mean to post twice, not entirely sure what happened there....
The technical bods high up are telling me I don't have a problem and it's all to do with QoS etc, but I'm less than convinced.

I'd like to know the stability of other's ping times? .........

Feel free to paste your pings to ntlworld.com here please!!
Bill C
23-06-2006, 17:27
I didn't mean to post twice, not entirely sure what happened there....
The technical bods high up are telling me I don't have a problem and it's all to do with QoS etc, but I'm less than convinced.

I'd like to know the stability of other's ping times? .........

Feel free to paste your pings to ntlworld.com here please!!


Here you go

NTL 10 meg in Warrington


Pinging www.ntlworld.com [212.250.162.47] with 32 b

Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=17ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=16ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=36ms TTL=1
Reply from 212.250.162.47: bytes=32 time=16ms TTL=1
Reply from 212.250.162.47: bytes=32 time=20ms TTL=1
Reply from 212.250.162.47: bytes=32 time=15ms TTL=1
Reply from 212.250.162.47: bytes=32 time=15ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=31ms TTL=1
Reply from 212.250.162.47: bytes=32 time=31ms TTL=1
Reply from 212.250.162.47: bytes=32 time=17ms TTL=1
Reply from 212.250.162.47: bytes=32 time=15ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=15ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=28ms TTL=1
Reply from 212.250.162.47: bytes=32 time=16ms TTL=1
Reply from 212.250.162.47: bytes=32 time=15ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=18ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=18ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=17ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=16ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=14ms TTL=1
Reply from 212.250.162.47: bytes=32 time=16ms TTL=1
Reply from 212.250.162.47: bytes=32 time=13ms TTL=1
Reply from 212.250.162.47: bytes=32 time=18ms TTL=1
Reply from 212.250.162.47: bytes=32 time=56ms TTL=1

Ping statistics for 212.250.162.47:
Packets: Sent = 40, Received = 40, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 56ms, Average = 17ms
Graham M
23-06-2006, 17:32
4 Meg in Poole, BH14

Pinging www.ntlworld.com [212.250.162.47] with 32 bytes of data:

Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=25ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=14ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Request timed out.
Reply from 212.250.162.47: bytes=32 time=10ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=15ms TTL=121
Reply from 212.250.162.47: bytes=32 time=9ms TTL=121
Reply from 212.250.162.47: bytes=32 time=12ms TTL=121
Reply from 212.250.162.47: bytes=32 time=18ms TTL=121
Reply from 212.250.162.47: bytes=32 time=19ms TTL=121
Reply from 212.250.162.47: bytes=32 time=14ms TTL=121
Reply from 212.250.162.47: bytes=32 time=11ms TTL=121
Reply from 212.250.162.47: bytes=32 time=16ms TTL=121
Reply from 212.250.162.47: bytes=32 time=25ms TTL=121
Reply from 212.250.162.47: bytes=32 time=17ms TTL=121
Reply from 212.250.162.47: bytes=32 time=18ms TTL=121
Reply from 212.250.162.47: bytes=32 time=26ms TTL=121
Reply from 212.250.162.47: bytes=32 time=16ms TTL=121

Ping statistics for 212.250.162.47:
Packets: Sent = 28, Received = 27, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 26ms, Average = 14ms
dunkyb
23-06-2006, 17:38
Looks like others are in the same boat then and I dont have a case!

Guess that's what we can expect on cable then?

Cheers guys.

---------- Post added at 17:38 ---------- Previous post was at 17:37 ----------

Also:

Fri, 23 Jun 2006 16:24:04 UTC
1st 512K took 1142 ms = 448.3 KB/sec, approx 3694 Kbps, 3.61 Mbps
2nd 512K took 2884 ms = 177.5 KB/sec, approx 1463 Kbps, 1.43 Mbps
3rd 512K took 2163 ms = 236.7 KB/sec, approx 1950 Kbps, 1.9 Mbps
4th 512K took 2133 ms = 240 KB/sec, approx 1978 Kbps, 1.93 Mbps
Overall Average Speed = approx 2271 Kbps, 2.22 Mbps

May as well downgrade to 2Mbit i think!
AbyssUnderground
24-06-2006, 14:42
No such thing as 2Mbps anymore. Its all going to be 1Mbps, 4Mbps or 10Mbps now.
Chrysalis
25-06-2006, 12:46
its normal for ntl I think yeah, some lucky people wont have that varation, and for me it was much much worse I had spikes up to 3 figures.

Pinging ntlworld.com [212.250.162.47] with 32 bytes of data:

Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=18ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=18ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116

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

thats from nildram, but ntlworld.com is responding fine.
dunkyb
27-06-2006, 11:23
yeah every other ISP seems to have decent latency ...

Cheers for the replies, glad It's not something affecting my connection solely then.
jtwn
27-06-2006, 12:20
How do you propose it is affecting your connection?