Have you checked the service issues page on BT?
Since, Thursday evening I have had an issues with some websites not loading bbc, hotmail and pistonheads for example. This website took too long to respond.
TZ and home.bt.com loads OK.
E-mails are slow to appear on tablet.
Tried on multiple devices iPad, android phone, desktop and laptop running Windows 7. Tried phone and tablet at work and works fine.
Can run Speedtest app on iPad and get good results Ping 8 ms, Jitter 0.76 ms, Upload 72 Mbs, Download 19 Mbs. However, cannot access speedtest and BT speed test check websites.
I have restarted BT hub 5, reset it. Changed to a brand new Hub 6 with new filter. In Hub manager status I connected and light is blue on the router.
Tried Safari and Chrome on iPad and Firefox and Opera on PC.
Sky Box does not download and can't stream via Amazon Firestick.
BBC app slow to update and photos not always displayed on news story.
Inserted into BT test socket.
Have tried with Ethernet cable from router to laptop same issues. Changed to Google and Open DNS no change.
Called BT and they run various test, but can't find any problem. Suggestion, was to book an engineer, which may result in a charge.
Any ideas and what to try next?
Thanks
Have you checked the service issues page on BT?
If you lived local, I'd pop round with my network analyser and have a look. And drink your beer.
Sent from my [device_name] using TZ-UK mobile app
Have you used the tracert command before?
Sent from my [device_name] using TZ-UK mobile app
Ive seen their DNS helper break stuff before - maybe try turning it off?
http://preferences.webaddresshelp.bt.com/selfcare/
Try setting your DNS server to 8.8.8.8
bbc.co.uk loads very slowly or does not load and tz loads OK.
Ping and Tracert results below.
>ping www.bbc.co.uk
Ping request could not find host www.bbc.co.uk. Please check the name and try again.
>ping www.forum.tz-uk.com
Pinging forum.tz-uk.com [77.72.3.159] with 32 bytes of data:
Reply from 77.72.3.159: bytes=32 time=9ms TTL=51
Reply from 77.72.3.159: bytes=32 time=9ms TTL=51
Reply from 77.72.3.159: bytes=32 time=9ms TTL=51
Reply from 77.72.3.159: bytes=32 time=10ms TTL=51
Ping statistics for 77.72.3.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 10ms, Average = 9ms
>tracert bbc.co.uk
Tracing route to bbc.co.uk [151.101.64.81]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms BTHUB [192.168.1.254]
2 * * * Request timed out.
3 * 7 ms 6 ms 31.55.187.177
4 8 ms 7 ms 8 ms 31.55.187.184
5 8 ms 8 ms 7 ms core2-hu0-10-0-0.southbank.ukcore.bt.net [195.99.127.170]
6 10 ms 8 ms 7 ms peer8-et-0-1-5.telehouse.ukcore.bt.net [109.159.252.102]
7 7 ms 6 ms 6 ms 195.99.126.83
8 7 ms 7 ms 6 ms 151.101.64.81
tracert forum.tz-uk.com
Tracing route to forum.tz-uk.com [77.72.3.159]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms BTHUB [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 6 ms 6 ms 6 ms 31.55.187.180
5 7 ms 8 ms 7 ms 194.72.31.166
6 12 ms 7 ms 8 ms peer1-et-2-1-0.telehouse.ukcore.bt.net [62.172.103.25]
7 7 ms 6 ms 11 ms lon-tel-01gw.voxility.net [195.66.226.180]
8 12 ms 7 ms 7 ms lon-tel-01c.voxility.net [5.254.107.85]
9 19 ms 14 ms 24 ms lh30518.voxility.net [185.5.172.166]
10 7 ms 7 ms 7 ms 77.72.0.19
11 12 ms 9 ms 9 ms server.timefactors.com [77.72.3.159]
Trace complete.
The fact you can't ping www.bbc.co.uk by name looks like some DNS issue. I'll have a check on my router as I have BT Infinity too. Once I've got out of bed. It is Christmas after all!
Sent from my ONEPLUS A3003 using TZ-UK mobile app
are you on windows ??
Try - RUN CMD ipconfig /displaydns
then
ipconfig /flushdns
I do this periodically. Sometimes BT do switching when doing maintenance -- I fiond that this helps.
B
BT Engineer booked, because the issue remains and they can't see any issues after doing some further testing.
I'd be astonished if it was anything to do with the line.
It does have all the hallmarks of a DNS issue. At the risk of asking a silly question, do you have DNS settings on your router that might be worth changing?
It's difficult to diagnose remotely. The OP mentioned that he had swapped hubs so unless he had manually changed DNS on both hubs, at least one should be automatically set to the correct address. In my experience with work, Openreach engineers are great at fixing physical issues (at least they are in my local area) but not so hot with internet routing etc. Could be a job for Teamviewer and coffee.
Did you check the BT DNS helper yet?
This is almost definitely DNS related. When you say you're changing your DNS, where are you making the change? At router or adapter level?
Which model is the hub? Ie hub 3, hub 5, business hub? I couldn't tell you how off the top of my head but if you Google "change DNS home hub 3" it should give you the result you need.
Sent from my [device_name] using TZ-UK mobile app
What happens if you type "http://212.58.244.56/" into your web browser? Does the BBC News site come up? is it any different to when you type "http://www.bbc.co.uk/news"?
If you open a Command Window ("<Win>-R" and then "cmd") and type "ipconfig / flushdns", can you then access the problematic web sites?
BBC News does appear however, it is slow to load and photos are not displayed. If I use http://www.bbc.co.uk/news photos are displayed. But, when I click on Health section photos are not displayed and when I refresh the site does not load.
Did the flush command. Tried some other websites and receive the message "This site can’t be reached"
https://www.flyertalk.com/forum/index.php
https://www.avforums.com/
Using the following DNS on the wireless connection for the PC.
Preferred: 8.8.8.
Alternate: 192.168.1.254
Hmm - like others, i had also thought that it sounded very much like a DNS issue. But if you are getting equally slow loading when you use the IP address, then that would tend to rule out DNS.
I assume you mean 8.8.8.8 as your primary DNS server. It might be worth also trying 9.9.9.9.
What's 192.168.1.254? Is this the (LAN) address of your router (It's a non-routable address, so it will be something local to you, and this address might be the cause of your problems). I would try removing it (you only need a second DNS address as a backup in case the primary one is unavailable, but normally both would be external - personally, I use 9.9.9.9 and 8.8.8.8).
Also, in a command window could you try both "tracert www.avforums.com" and "tracert 176.56.60.158"? The results might help show where the issue is.
Last edited by PhilipK; 27th December 2017 at 23:54.
I believe 192.168.1.254, is the DNS on the BT Hub.
Have changed Primary and Secondary DNS to 9.9.9.9 and 8.8.8.8 on the wireless connection on my desktop.
Tracert results below.
tracert www.avforums.com
Tracing route to www.avforums.com [176.56.60.158]
over a maximum of 30 hops:
1 8 ms 3 ms 3 ms BTHUB [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 9 ms 7 ms 7 ms 31.55.187.180
5 7 ms 6 ms 6 ms 213.121.192.102
6 8 ms 7 ms 7 ms peer6-hu0-11-0-1.telehouse.ukcore.bt.net [195.99.127.13]
7 10 ms 7 ms 7 ms linx-gw1.thn.ncuk.net [195.66.224.240]
8 124 ms 74 ms 11 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
9 8 ms 8 ms 8 ms 80.249.107.162
10 12 ms 8 ms 14 ms 176.56.60.158
Trace complete.
tracert 176.56.60.158
Tracing route to 176.56.60.158 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms BTHUB [192.168.1.254]
2 * * * Request timed out.
3 * * 8 ms 31.55.187.181
4 11 ms 7 ms 8 ms 31.55.187.180
5 7 ms 7 ms 7 ms 213.121.192.102
6 8 ms 8 ms 8 ms peer6-hu0-11-0-1.telehouse.ukcore.bt.net [195.99.127.13]
7 8 ms 19 ms 6 ms linx-gw1.thn.ncuk.net [195.66.224.240]
8 7 ms 6 ms 7 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
9 8 ms 7 ms 8 ms te1-50-157.core-rs3.vt.nimbushosting.co.uk [80.249.107.162]
10 8 ms 8 ms 8 ms 176.56.60.158
Trace complete.
Update, the BT Engineer has come and can't find any issues with the line. This type issue has occurred in the past with the solution being to cease the line and then reinstate it.
Hopefully, that will work?
Does he mean reset the line? It sounds like there is an issue between your hub and the local DP, especially since the engineer has referred to it. It will affect the line speed, possibly taking you back to the days of 28.8K modems.
Did you ever get to the bottom of this?