Quote:
|
Originally Posted by jonholyfield
My main problem her lies at the feet of NTL. The support people try. They really do. But they dont appear to have the tools to do the job. "Ah so you ar MR ***" No I'm an It techician and there is a latency problem on this line "So you cannot access the internet".
Sigh here we go again. Script city.
Try bbc.co.uk
Nice try lets take the most well cached site in the world for trouble shooting.
How about trying http://www.zmag.org/ instead.
Relying on cached info to prove it is not a problem verges on criminal.
I DO have problems with outsourcing this support work but that is irrelevant.
If you do send it to India or wherever you have to give them the tools to fix it.
At least a decent escalation procedure that is transparent to the consumer.
Having to threaten court action to get NTL to admit there is even a problem should NOT be common practice. |
Careful with the description of a latency issue on the line, browsing issues can't really be equated with latency issues.
BBC is a default choice because it's so well cached / mirrored, reduces the chances of a fault on a website's performance shiding a fault on the ntl network.
The rest of it I agree with though, proxy issues are something that's poorly dealt with not least because according to all metrics and readouts from the proxies they are performing well and are not overloaded in any way. (He says looking at the NetApp info).
Bet if you specify a proxy it resolves the issue?