Quote:
|
Originally Posted by Florence
What do you expect when they cut back on engineers and only employ sales staff  suppose after December the only way is downhill fast for the northwest. Lets see if NTL can prove us wrong and employ some BB engineers as withjout them the network will be bad and the customers will leave |
Sorry to say this but Bill C, who I assume you are referring to, is not a network engineer, nor do broadband engineers maintain and service the local networks in the North West.
---------- Post added at 22:09 ---------- Previous post was at 22:04 ----------
Quote:
|
Originally Posted by th'engineer
just when you think that you would escape the recent problems
Sun, 4 Dec 2005 19:50:16 UTC
1st 128K took 532 ms = 246376 Bytes/sec = approx 2050 kbits/sec
2nd 128K took 531 ms = 246840 Bytes/sec = approx 2054 kbits/sec
3rd 128K took 562 ms = 233224 Bytes/sec = approx 1940 kbits/sec
4th 128K took 3172 ms = 41322 Bytes/sec = approx 344 kbits/sec
A load of bobbins again 
Target Name: www.ntlworld.com
IP: 212.250.162.47
Date/Time: 04/12/2005 19:53:37
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.123.254]
2 6 ms 15 ms 7 ms 8 ms 6 ms 6 ms 11 ms * 7 ms 16 ms [10.23.48.1]
3 28 ms 12 ms 16 ms 52 ms 12 ms 102 ms 9 ms * 16 ms 8 ms oldh-t2cam1-b-v115.inet.ntl.com [80.5.164.189]
4 12 ms 29 ms 7 ms 10 ms 8 ms 71 ms 13 ms 10 ms 12 ms 11 ms manc-t3core-1b-ge-111-0.inet.ntl.com [213.104.242.205]
5 24 ms 15 ms 9 ms 8 ms 65 ms 40 ms 12 ms 18 ms 9 ms 24 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
6 13 ms 18 ms 16 ms 13 ms 44 ms 18 ms 28 ms 18 ms 17 ms 17 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
7 21 ms 22 ms 14 ms 20 ms 17 ms 14 ms 114 ms 15 ms 15 ms 18 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]
8 15 ms 24 ms 19 ms 18 ms 20 ms 13 ms 100 ms 15 ms 21 ms 19 ms www.ntlworld.com [212.250.162.47]
this might help |
You missed a 102ms spike in hop 3, a 71ms and a 29ms variation in hop 4, a 40ms spike to hop 5, a 28ms spike to hop 6, a 114ms spike to hop 7 and coloured a 21ms response in hop 8 but missed a 24ms one.
If this was done via wireless to your USR router try it wired instead or check signal for variations, alternatively supply something a little more concrete as far as proof of this affecting service, I note no packet loss to end destination indicating no ongoing packet loss and just drops to routers here and there.
Some variation with regard to latency is sadly an inevitable part of speed upgrades, and aspects of the upgrades aren't complete anywhere in the country. When all is done this might well stabilise your service.
Alternatively follow standard troubleshooting procedures for yourself and start calling directors of ntl
---------- Post added at 22:18 ---------- Previous post was at 22:09 ----------
Code:
Packets Pings
Hostname %Loss Rcv Snt Last Best Avg Worst
4. tele-ic-1-ge-200-205.inet.ntl.com 0% 51 51 1 0 2 10
5. nth-bb-b-so-600-0.inet.ntl.com 0% 51 51 6 3 6 26
6. lee-bb-a-so-600-0.inet.ntl.com 0% 51 51 6 6 10 74
7. lee-bb-b-ae0-0.inet.ntl.com 0% 51 51 10 6 11 61
8. man-bb-a-so-700-0.inet.ntl.com 0% 50 50 10 7 9 32
9. glfd-bam-1-atm403-1.inet.ntl.com 0% 50 50 8 7 9 24
10. oldh-t2cam1-a-ge-wan32.inet.ntl.com 0% 50 50 9 7 12 73
11. ubr01roch.inet.ntl.com 2% 49 50 10 8 10 15
--- ubr01roch.inet.ntl.com ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 8.090/10.302/15.299/1.504 ms
Looks like the baby is deprioritising rather than having a genuine issue.
Might be a local fault, however people are all in generally different networks with no real crossover points at the *access* level.
Core level appears at a very casual inspection to be ok.