I include another screenshot that shows that I can access another site and also do a tracert on other sites with my ntl connection
This is results of tracert on google
Tracing route to
www.google.akadns.net [66.102.9.104]
over a maximum of 30 hops:
1 9 ms 7 ms 5 ms 10.14.0.1
2 7 ms 7 ms 8 ms bagu-t2cam1-b-ge-wan51-118.inet.ntl.com [80.5.162.201]
3 6 ms 7 ms 8 ms bagu-t2core-b-ge-wan64.inet.ntl.com [80.5.161.141]
4 15 ms 9 ms 8 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 9 ms 9 ms 11 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 14 ms 13 ms 18 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 37 ms 21 ms 24 ms amst-ic-1-so-100-0.inet.ntl.com [62.253.185.254]
8 25 ms 22 ms 22 ms core1.ams.net.google.com [195.69.144.247]
9 24 ms 25 ms 27 ms 216.239.43.92
10 26 ms 25 ms 25 ms 216.239.43.93
11 55 ms 40 ms 31 ms 64.233.175.246
12 33 ms 31 ms 30 ms 216.239.46.173
13 60 ms 58 ms 69 ms 216.239.49.254
14 58 ms 57 ms 58 ms 216.239.48.50
15 59 ms 63 ms 57 ms 64.233.175.185
16 71 ms 66 ms 61 ms 64.233.174.18
17 60 ms 74 ms 59 ms 66.102.9.104
Trace complete.
I have also included another tracert for
www.tucows.com
I have only had this problem since the data centre issue ntl had last week, I can still access the site via the same computer on a different connection, surely that points to the ntl connection