Cambridge outage - any more info?

[southa]

Hi,

Does anyone know what's happening with the Cambridge broadband service outage on the NTL status page. I've been getting intermittent service since the start of the year, and now it's been off completely for four days. The cable light on the modem (Terayon TeraJet) is either off or flashing at around 1/2 Hz. I've tried power cycling etc. and I've also tried the modem on the TV cable (TV is fine). No luck.

The weird thing is that a lot of the people around me have no problems. An NTL engineer once told me that these particular modems can have trouble finding service again if you move house. I'm wondering whether some sort of network reconfiguration has caused a similar problem.

Meanwhile I shall continue to spend my spare time in the call queue for broadband support, whilst watching telly/cooking/etc.

[Tezcatlipoca]

:welcome:


Whereabouts are you? I'm in CB2, & have had no problems at all. I also still use a Terayon.

[keitht]

I'm also having big problems - CM20 area. Sometimes it's ok but yesterday & today AAARRRGGG!!! Pages time out, email doesn't connect. It's take 20 mins to display this thread! I've called several times, twice to (I think) the indian call centre, once to UK faults. I was told that the line is noisy, and I should call the faults status line. This does not mention this fault.

Please tell me that there really is someone working on this fault. It is VERY annoying.

[Hom3r]

Somewhere on the BBC website it reported that there was a lot of solar activity and that this would intherfere with TV & communication in the UK so this may be why there are connection problems. so this is definitly something NTL cannot deal with.


I live in CM20 and have had some time delays.

[keitht]

This afternoon my connection has gone completely. It was ok this morning. I guess the sun spots were stronger in the afternoon.

ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.224.82] with 32 bytes of data:

Reply from 212.58.224.82: bytes=32 time=111ms TTL=246
Reply from 212.58.224.82: bytes=32 time=10ms TTL=246
Request timed out.
Request timed out.

Ping statistics for 212.58.224.82:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 111ms, Average = 30ms


tracert www.google.com

Tracing route to www.google.akadns.net [66.102.9.104]
over a maximum of 30 hops:

1 * * * Request timed out.
2 10 ms * 81 ms cmbg-t2cam1-b-v111.inet.ntl.com [80.1.202.181]
3 * * * Request timed out.
4 20 ms * 30 ms nth-bb-b-so-210-0.inet.ntl.com [62.253.188.197]

5 * * * Request timed out.
6 70 ms * * gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * 40 ms ^C

tracert www.google.com

Tracing route to www.google.akadns.net [66.102.9.104]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * 10 ms 80.1.201.165
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * 50 ms * 64.233.174.42
12 * * * Request timed out.
13 * * * Request timed out.
14 60 ms * * 66.102.9.104
15 * 40 ms * 66.102.9.104
16 * * * Request timed out.
17 90 ms 60 ms * 66.102.9.104
18 40 ms * 50 ms 66.102.9.104

Trace complete.


I've had to dig out my modem & post this via dialup.

[southa]

Well I got my broadband fixed. I phone up at around 5:30pm on Friday and the call was answered in about five minutes. "We'll send an engineer round - the earliest time we have is tomorrow morning", and sure enough the engineer turned up, jacked up the signal levels and fixed the problem. It's been fine ever since.

You're probably thinking this is too good to be true.

Yep, this would be NTL heaven, except that the gremlins were transferred to the set top box. I now have the dreaded picture stuttering problem on Sky One, E4, Channel 5, whereas BBC and a few others are fine. I remember this one from a year or two back. The page-up, page-down, blue diagnostic box is showing SNR around 26dB and 10E-4 Pre RS errors. So, I shall get on the blower again, and pray that it can be fixed before the next episode of Desperate Housewives.

Incidentally NTL said that there were no broadband problems in my area (CB4) on Friday.

[keitht]

Can anyone tell me if this traceroute is related to the ongoing problem or is it a different problem?

tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.224.115]
over a maximum of 30 hops:

1 10 ms * 40 ms 10.132.239.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 ^C

Thanks