Thank you DS and MikeZ for explaining. I thought it was a transparent proxy. Thanks for clearing that up and I'm glad it is something I can opt out of!!
Not too sure on the technicalites involved, however my local council website is inaccessiible as is my charity's website. Odd. If I hop onto my bt openzone connection however all is fine.
I've just checked here :-
and there seems to be quite a bit going on. This may have a bearing.
However when this problem started (Thursday night) there was only a notice of problems in 2 exchanges and both were in completely different parts of the country from me.
My exchange is Tetbury in Gloucestershire.
Same problem here since yesterday. Some websites only working partially or not at all for me both on a Mac connected via Ethernet to the BT Home Hub and on an iPad connected to same hub via WiFi . The same sites work fine over the independent 3G connection on the iPhone.
It's slashdot.org, dreamwidth.org and flickr.com (partially) for me today. Definitely not a DNS problem (all resolve OK) and also not browser specific (tried both Safari and Firefox)
Something with BT's routing/peering is seriously up the spout.
I was wondering if its the transparent proxy, but I get a problem accessing IMAP to my company email as well. Would the IMAP ports also go via this proxy?
Transparent proxy ? There isn't one.
There seems to be. I have noticed that when I make a typo with URLs I get a BT search page coming up. Yet my browser search default was set to Bing. I noticed this a few months ago.
Try putting rubbish in the URL such as
and see what you get!
Hi again. As others have said, it's the incorrect URL "interception" system. See my shortcuts option 17 which I added almost 6 months ago. It has been known to cause user problems, e.g. with VPN access.
wikipedia isn't loading for me now either.
Seems to be getting worse rather than better. I wonder if anyone at BT is actually even looking into this.
Just run a TRACERT to btyahoo.com:
Tracing route to btyahoo.com [18.104.22.168]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms api.home [192.168.1.254]
2 25 ms 27 ms 25 ms 22.214.171.124
3 25 ms 25 ms 24 ms 126.96.36.199
4 31 ms 31 ms 32 ms 188.8.131.52
5 31 ms 31 ms 30 ms 184.108.40.206
6 32 ms 32 ms 31 ms 220.127.116.11
7 31 ms 31 ms 31 ms 18.104.22.168
8 38 ms 37 ms 39 ms acc1-10GigE-11-2-0.sf.21cn-ipp.bt.net [109.159.2
9 41 ms 38 ms 39 ms core2-te0-4-0-2.ilford.ukcore.bt.net [109.159.25
10 41 ms 44 ms 41 ms core2-pos7-3.bletchley.ukcore.bt.net [22.214.171.124
11 42 ms 41 ms 41 ms vhsaccess1-pos8-0.bletchley.fixed.bt.net [62.6.1
12 42 ms 41 ms 41 ms ftip002637372.vhsaccess1.bletchley.fixed-nte.bt.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Hope this helps
At the very least, shouldn't this problem be listed in BT's service status updates? If you look there, it claims everything's hunky-dory.