Jeff,
Have you got the latest Chairman's address?
Ta
Broadband
Every ISP has a problem from time to time with DNS. Which is why it is always good to have a backup. Hence OpenDNS.maturin wrote:I understand (I think) how open DNS works, but just can't understand why a third-party solution should be so much better than BT's own systems. Why on earth can't BT's DNS work?
I also need guaranteed access and while Zen has never let me down - a power cut has! So I have a dongle and a '3' PAYG SIM just in case. That gives me 1Gbps for a tenner which will tide me over any incident. And you don't pay it till you need it!maturin wrote:This past 3 1/2 weeks has taught me that I can't afford to have any downtime on my business. So for the future I want belt and braces.
As soon as I get my Mac code from BT I'm off. I see from your e-mail you use Zen. Can you recommend them? I've heard some very good things about Be There.
Zen is very good but not cheap. Bethere always seems to get good reports too. Bethere provide the O2 service - so if you have an O2 contract you might get a very good deal.
Admin
Update (Thursday 7am) ......
I was out all day yesterday so I do not know whether they carried out the work. No downtime on the router. They will be ringing me after 11am this morning giving an update.
The problem is STILL there, if not worse than before.
Using OpenDNS does not solve the problem. When using a tracert the problem is clearly at the exchange or when it just leaves it.
Below I have shown two tracerts, the first is when it works
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mine>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.246.159]
over a maximum of 30 hops:
1 76 ms 99 ms 99 ms BThomehub.home [192.168.1.254]
2 24 ms 24 ms 23 ms 217.32.146.167
3 24 ms 32 ms 24 ms 217.32.146.206
4 23 ms 24 ms 28 ms 213.120.177.50
5 35 ms 24 ms 24 ms 213.120.176.62
6 24 ms 24 ms 23 ms 213.120.176.182
7 24 ms 24 ms 24 ms 213.120.176.129
8 23 ms 24 ms 23 ms core1-gig10-0-0.faraday.ukcore.bt.net [62.172.10
2.133]
9 27 ms 25 ms 25 ms core3-pos0-1-1-0.ealing.ukcore.bt.net [62.6.204.
77]
10 25 ms 25 ms 26 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
11 131 ms 215 ms 210 ms 194.74.65.42
12 24 ms 25 ms 25 ms 212.58.238.129
13 26 ms 26 ms 26 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
14 26 ms 26 ms 25 ms 212.58.255.12
15 26 ms 25 ms 26 ms fmt-vip02.cwwtf.bbc.co.uk [212.58.246.159]
Trace complete.
_____________________________________________________
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mine>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.244.140]
over a maximum of 30 hops:
1 37 ms 99 ms 99 ms BThomehub.home [192.168.1.254]
2 23 ms 23 ms 23 ms 217.32.146.167
3 * * * Request timed out.
4 23 ms 24 ms 24 ms 213.120.177.50
5 24 ms 24 ms 24 ms 213.120.176.62
6 24 ms 23 ms 24 ms 213.120.176.182
7 23 ms 24 ms 24 ms 213.120.176.137
8 * * * Request timed out.
9 25 ms 25 ms 25 ms 62.172.103.29
10 26 ms 25 ms 26 ms core1-pos1-0-0.telehouse.ukcore.bt.net [62.6.201
.82]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 25 ms 25 ms 25 ms 212.58.251.43
15 25 ms 25 ms 24 ms fmt-vip01.telhc.bbc.co.uk [212.58.244.140]
Trace complete.
I was out all day yesterday so I do not know whether they carried out the work. No downtime on the router. They will be ringing me after 11am this morning giving an update.
The problem is STILL there, if not worse than before.
Using OpenDNS does not solve the problem. When using a tracert the problem is clearly at the exchange or when it just leaves it.
Below I have shown two tracerts, the first is when it works
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mine>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.246.159]
over a maximum of 30 hops:
1 76 ms 99 ms 99 ms BThomehub.home [192.168.1.254]
2 24 ms 24 ms 23 ms 217.32.146.167
3 24 ms 32 ms 24 ms 217.32.146.206
4 23 ms 24 ms 28 ms 213.120.177.50
5 35 ms 24 ms 24 ms 213.120.176.62
6 24 ms 24 ms 23 ms 213.120.176.182
7 24 ms 24 ms 24 ms 213.120.176.129
8 23 ms 24 ms 23 ms core1-gig10-0-0.faraday.ukcore.bt.net [62.172.10
2.133]
9 27 ms 25 ms 25 ms core3-pos0-1-1-0.ealing.ukcore.bt.net [62.6.204.
77]
10 25 ms 25 ms 26 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
11 131 ms 215 ms 210 ms 194.74.65.42
12 24 ms 25 ms 25 ms 212.58.238.129
13 26 ms 26 ms 26 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
14 26 ms 26 ms 25 ms 212.58.255.12
15 26 ms 25 ms 26 ms fmt-vip02.cwwtf.bbc.co.uk [212.58.246.159]
Trace complete.
_____________________________________________________
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mine>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.244.140]
over a maximum of 30 hops:
1 37 ms 99 ms 99 ms BThomehub.home [192.168.1.254]
2 23 ms 23 ms 23 ms 217.32.146.167
3 * * * Request timed out.
4 23 ms 24 ms 24 ms 213.120.177.50
5 24 ms 24 ms 24 ms 213.120.176.62
6 24 ms 23 ms 24 ms 213.120.176.182
7 23 ms 24 ms 24 ms 213.120.176.137
8 * * * Request timed out.
9 25 ms 25 ms 25 ms 62.172.103.29
10 26 ms 25 ms 26 ms core1-pos1-0-0.telehouse.ukcore.bt.net [62.6.201
.82]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 25 ms 25 ms 25 ms 212.58.251.43
15 25 ms 25 ms 24 ms fmt-vip01.telhc.bbc.co.uk [212.58.244.140]
Trace complete.
Further update (Thursday 4pm) ..............
Apparently they went to the exchange yesterday and they now do not think it is a problem with the dslam card. They believe the problem lies elsewhere within the exchange or the network or their monitoring equipment, so it has now been passed back to BT retail for them to investigate. NO timescales were given when I can expect it to be sorted.
Might be a good time to get the MP to deal with it
Apparently they went to the exchange yesterday and they now do not think it is a problem with the dslam card. They believe the problem lies elsewhere within the exchange or the network or their monitoring equipment, so it has now been passed back to BT retail for them to investigate. NO timescales were given when I can expect it to be sorted.
Might be a good time to get the MP to deal with it
Here is my traceroute:
192.168.16.1 is my router and connects directly to the Zen (my ISP) gateway and hence on to the BBC in 6 hops. Your traceroute does seem to take an unnecessary tour of a lot of BT routers. Remember the pathway from my gateway to Zen's may be passing through the same slam as you.
Does it suggest a BT routeing problemo?
traceroute to www.bbc.co.uk (212.58.246.159), 30 hops max, 60 byte packets
1 local.gateway (192.168.16.1) 4.595 ms 4.584 ms 4.578 ms
2 losubs.subs.dsl2.th-lon.zen.net.uk (62.3.84.21) 35.817 ms 37.531 ms 37.580 ms
3 ae0-114.cr1.th-lon.zen.net.net (62.3.84.185) 39.220 ms 39.270 ms 40.911 ms
4 82.71.254.134 (82.71.254.134) 49.286 ms 49.287 ms *
5 212.58.238.129 (212.58.238.129) 45.836 ms 45.884 ms 45.879 ms
6 te12-1.hsw0.cwwtf.bbc.co.uk (212.58.239.222) 47.528 ms * *
7 * * *
8 * * *
9 * * *
10 * * *
11 fmt-vip02.cwwtf.bbc.co.uk (212.58.246.159) 27.558 ms 27.560 ms 29.206 ms
192.168.16.1 is my router and connects directly to the Zen (my ISP) gateway and hence on to the BBC in 6 hops. Your traceroute does seem to take an unnecessary tour of a lot of BT routers. Remember the pathway from my gateway to Zen's may be passing through the same slam as you.
Does it suggest a BT routeing problemo?
traceroute to www.bbc.co.uk (212.58.246.159), 30 hops max, 60 byte packets
1 local.gateway (192.168.16.1) 4.595 ms 4.584 ms 4.578 ms
2 losubs.subs.dsl2.th-lon.zen.net.uk (62.3.84.21) 35.817 ms 37.531 ms 37.580 ms
3 ae0-114.cr1.th-lon.zen.net.net (62.3.84.185) 39.220 ms 39.270 ms 40.911 ms
4 82.71.254.134 (82.71.254.134) 49.286 ms 49.287 ms *
5 212.58.238.129 (212.58.238.129) 45.836 ms 45.884 ms 45.879 ms
6 te12-1.hsw0.cwwtf.bbc.co.uk (212.58.239.222) 47.528 ms * *
7 * * *
8 * * *
9 * * *
10 * * *
11 fmt-vip02.cwwtf.bbc.co.uk (212.58.246.159) 27.558 ms 27.560 ms 29.206 ms
The Eagle,
It seems like I just had the same phone call. The story now goes something like this (paraphrased):
"... we are aware of your original fault (March 17) and engineers have been working hard, but unsuccessfully, to fix this. We now I admit (reluctantly) that this fault is shared by many other people in your area.
We know you, other customers, and our engineers told us about this fault, but frankly it's cheaper to employ Indian call centre workers than it is to fix it.
However, there is now a BRAND-NEW FAULT affecting numbers beginning with 676, 659, 778 and about half a dozen other prefixes served by the Sydenham exchange. Frankly, we haven't a clue what to do about this. We don't know what's gone wrong, and we have no idea how long it will take to fix it.
Sorry about that."
I can't wait to my virgin media installation, and I've already spoken to the sales team at BeThere about switching from BT.
It seems like I just had the same phone call. The story now goes something like this (paraphrased):
"... we are aware of your original fault (March 17) and engineers have been working hard, but unsuccessfully, to fix this. We now I admit (reluctantly) that this fault is shared by many other people in your area.
We know you, other customers, and our engineers told us about this fault, but frankly it's cheaper to employ Indian call centre workers than it is to fix it.
However, there is now a BRAND-NEW FAULT affecting numbers beginning with 676, 659, 778 and about half a dozen other prefixes served by the Sydenham exchange. Frankly, we haven't a clue what to do about this. We don't know what's gone wrong, and we have no idea how long it will take to fix it.
Sorry about that."
I can't wait to my virgin media installation, and I've already spoken to the sales team at BeThere about switching from BT.
They are digging up the road opposite the B&Q center again... this is just round the corner from the exchange..I wonder if this has any bearing on the problem...
Virgin media is begining to look more attractive....
A friend commented to me that BT's problems are typical of technology based companies who seem to have more sales persons than engineers.....
Virgin media is begining to look more attractive....
A friend commented to me that BT's problems are typical of technology based companies who seem to have more sales persons than engineers.....
Correction: Only BT Broadband customers on these exchanges. Other customers using BT Openreach equipment at the same BT exchanges appear to be unaffected. Migration to one of these should take about 7 days.maturin wrote:However, there is now a BRAND-NEW FAULT affecting numbers beginning with 676, 659, 778 and about half a dozen other prefixes served by the Sydenham exchange.
I have much respect for real BT Telephone engineers. Quite a different kettle of fish from BT B'band.
Admin (in sympathy)
As I understand it - BT Openreach provide the telecommunications from your phone/router to the ISP's gateway. Basically the copper, exchange and a pipe. An ISP provides the link between that gateway and the internet.
BT Broadband is an ISP. They can contract BT Openreach services in exactly the same way as any other ISP. Indeed Ofcomm insists there are Chinese Walls between the two BT divisions so independent ISPs are put to no disadvantage.
Many independent ISPs have no problem in Sydenham and hence with BT Openreach. BT Broadband evidently does. I will leave it to you to judge where BT B'band think the problem lies.
HTH
Admin
BT Broadband is an ISP. They can contract BT Openreach services in exactly the same way as any other ISP. Indeed Ofcomm insists there are Chinese Walls between the two BT divisions so independent ISPs are put to no disadvantage.
Many independent ISPs have no problem in Sydenham and hence with BT Openreach. BT Broadband evidently does. I will leave it to you to judge where BT B'band think the problem lies.
HTH
Admin
Yes they 'now' THINK it is a BT Broadband routing problem or the equipment that they put on the line to monitor your usage etc.admin wrote:Here is my traceroute:
192.168.16.1 is my router and connects directly to the Zen (my ISP) gateway and hence on to the BBC in 6 hops. Your traceroute does seem to take an unnecessary tour of a lot of BT routers. Remember the pathway from my gateway to Zen's may be passing through the same slam as you.
Does it suggest a BT routeing problemo?
I've just spoken to BT (again), having gone through the numerous phone calls, engineer visit etc.
I was told Wednesday evening that engineers were working on the problem and everything should be fine. Yesterday all was good. However this morning I have had the same problems with the internet dropping out.
Apparently the BT engineers are still at the site and are now "replacing the network". Not sure what this means but its going to take about 12 hours.
I won't be holding my breath...
I was told Wednesday evening that engineers were working on the problem and everything should be fine. Yesterday all was good. However this morning I have had the same problems with the internet dropping out.
Apparently the BT engineers are still at the site and are now "replacing the network". Not sure what this means but its going to take about 12 hours.
I won't be holding my breath...
We have had the exact same problem since March 17 as well. It's driving us crazy and making us lose money.
Yesterday's morning and for a while today it was better, but as soon as I say, "finally!" it drops and just keeps trying to load sites forever.
It's terribly annoying because sometimes it works well, fast enough etc, and then when you need it the most (in between payments for instance) it fails to load ('the server is not responding').
Like you guys I've tried phone calls, emails, DMs to @BTCare on Twitter. They just refer you to basic measures that are useless.
To us no one from BT has accepted it has nothing to do with changing wireless channels or our computers ('is your computer on?') but with a major network fault on their end.
Yesterday's morning and for a while today it was better, but as soon as I say, "finally!" it drops and just keeps trying to load sites forever.
It's terribly annoying because sometimes it works well, fast enough etc, and then when you need it the most (in between payments for instance) it fails to load ('the server is not responding').
Like you guys I've tried phone calls, emails, DMs to @BTCare on Twitter. They just refer you to basic measures that are useless.
To us no one from BT has accepted it has nothing to do with changing wireless channels or our computers ('is your computer on?') but with a major network fault on their end.
The Eagle's traceroutes appear to indicate exactly where the problem is. That should be obvious to anybody who sees them. That BTB CS don't look (or understand the basics of an internet connection) is frightening. Unfortunately I have experienced this so many times before both personally and through clients that one has to say it is a systemic issue.
Frankly if you want a robust internet connection - then BTB is not going to deliver it. If you have a connection or routeing problem and need someone who can understand it before you can have any hope of a solution. BTB CS appear to simply work to scripts. Scripts that are designed to help the idiot user rather than address internal BT Broadband issues.
I say again. The solution to your problems need only be 7 days away. Migrate to an ISP with a decent reputation. Life is too short.
Admin
Frankly if you want a robust internet connection - then BTB is not going to deliver it. If you have a connection or routeing problem and need someone who can understand it before you can have any hope of a solution. BTB CS appear to simply work to scripts. Scripts that are designed to help the idiot user rather than address internal BT Broadband issues.
I say again. The solution to your problems need only be 7 days away. Migrate to an ISP with a decent reputation. Life is too short.
Admin
My 18mth contract doe's not run out until June... So I suppose I have few month more, before I can walk away from this nonsense. I'm too skint to run 2 ISP'sadmin wrote: I say again. The solution to your problems need only be 7 days away. Migrate to an ISP with a decent reputation. Life is too short.
Admin