@Ashover: I don't give in that easy, if I did then NTL win! They can then sit back and afford to lose customers without doing a damn thing about the problems. I intend to make sure I'm not going to get messed about with lame excuses and ensure someone knows it!!
@DeadKenny:
Traceroute through deafult proxy:
Code:
Tracing route to www.ntlworld.com [62.253.162.30]
over a maximum of 30 hops:
1 253 ms 246 ms 240 ms 10.175.71.254 <-- I assume this is the UBR?
2 129 ms 114 ms 115 ms nott-t2cam1-b-v108.inet.ntl.com [80.4.46.145]
3 230 ms 165 ms 153 ms nott-t2core-b-ge-wan74.inet.ntl.com [80.1.79.201]
4 247 ms 210 ms 163 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
5 165 ms 194 ms 191 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
6 261 ms 196 ms 142 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98]
7 255 ms 244 ms 208 ms win-bb-a-so-500-0.inet.ntl.com [213.105.172.129]
8 196 ms 224 ms 258 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]
9 260 ms 101 ms 13 ms www.ntlworld.com [62.253.162.30]
Trace complete.
Using 'ping -t 10.175.71.254' seems OK though:
Code:
Reply from 10.175.71.254: bytes=32 time=218ms TTL=255
Reply from 10.175.71.254: bytes=32 time=110ms TTL=255
Reply from 10.175.71.254: bytes=32 time=182ms TTL=255
Reply from 10.175.71.254: bytes=32 time=248ms TTL=255
Reply from 10.175.71.254: bytes=32 time=173ms TTL=255
Reply from 10.175.71.254: bytes=32 time=184ms TTL=255
Reply from 10.175.71.254: bytes=32 time=238ms TTL=255
Reply from 10.175.71.254: bytes=32 time=193ms TTL=255
Reply from 10.175.71.254: bytes=32 time=228ms TTL=255
Reply from 10.175.71.254: bytes=32 time=217ms TTL=255
Reply from 10.175.71.254: bytes=32 time=110ms TTL=255
Reply from 10.175.71.254: bytes=32 time=210ms TTL=255
Reply from 10.175.71.254: bytes=32 time=233ms TTL=255
Reply from 10.175.71.254: bytes=32 time=203ms TTL=255
Reply from 10.175.71.254: bytes=32 time=225ms TTL=255
Reply from 10.175.71.254: bytes=32 time=224ms TTL=255
Reply from 10.175.71.254: bytes=32 time=247ms TTL=255
Reply from 10.175.71.254: bytes=32 time=44ms TTL=255
Reply from 10.175.71.254: bytes=32 time=128ms TTL=255
Reply from 10.175.71.254: bytes=32 time=209ms TTL=255
Reply from 10.175.71.254: bytes=32 time=166ms TTL=255
Reply from 10.175.71.254: bytes=32 time=191ms TTL=255
Reply from 10.175.71.254: bytes=32 time=226ms TTL=255
Ping statistics for 10.175.71.254:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 248ms, Average = 191ms
Upstream from Surfboard 4100:
Code:
Channel ID: 4
Frequency: 36821684 Hz Ranged
Ranging Service ID: 82
Symbol Rate: 2.560 Msym/s
Power Level: 57 dBmV
and a 'netstat -s -p tcp'
Code:
TCP Statistics for IPv4
Active Opens = 2309
Passive Opens = 1085
Failed Connection Attempts = 0
Reset Connections = 194
Current Connections = 10
Segments Received = 369460
Segments Sent = 255882
Segments Retransmitted = 235
Not sure if this info helps but I do know I have to use the refresh button on web pages more than I used to. Trying to preview this message has also resulted in several time outs causing 'The page cannot be displayed' error! I'm having to copy the entire message before previewing in case the page craps out!!
If this were Southpark it would be "NTL!! OMG they've killed broadband!!"
