Kitz Forum
Internet => Web Browsing & Email => Topic started by: Chrysalis on November 09, 2016, 01:42:17 PM
-
Can anyone test this site for me please, preferably sky broadband users.
http://www.history.army.mil/books/wwii/100-11/ch3.htm#Conditions
on my sky connection it pauses for about a minute then times out. Yet on any of my proxies loads instantly.
Telnet diagnostics is the same, failure to telnet to the web server from any device on my lan, but no problems from other isp's.
-
Worked fine for me.....
Stuart
-
Also displayed properly for me . . .
Of course both Stuart and I have services from TalkTalk, not Sky.
-
From SSE(Daisy), I get the timeout as well ....
Would post a tracert, but it is not terribly helpful in this case i.e. cannot really tell if last few hops just don't respond, or if my ip range is blocked.
-
Times out for me as well on Plusnet....
-
Fine here, using PlusNet.
-
Times out for me on BT
-
Times out on John Lewis aka Plusnet :(
-
Not working on AAISP
-
BTW:
C:\Users\Admin>tracert www.history.army.mil
Tracing route to history.ahp.us.army.mil [147.248.13.163]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BTHUB6 [192.168.1.1]
2 * * * Request timed out.
3 11 ms 11 ms 11 ms 31.55.187.177
4 10 ms 11 ms 10 ms 31.55.187.176
5 11 ms 11 ms 11 ms core1-hu0-7-0-1.southbank.ukcore.bt.net [195.99.127.180]
6 11 ms 11 ms 11 ms 62.172.103.23
7 11 ms 11 ms 11 ms t2c3-et-3-1-0-0.uk-lon1.eu.bt.net [166.49.211.236]
8 120 ms 78 ms 78 ms ixp1-xe-0-1-0-0.us-nyc.eu.bt.net [166.49.208.137]
9 85 ms 85 ms 85 ms nyc2-brdr-01.inet.qwest.net [63.146.27.193]
10 * * * Request timed out.
11 103 ms 103 ms 103 ms 65.158.208.218
12 * * * Request timed out.
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.
-
I can get to it OK on Gigaclear FTTP.
-
Timing out on Zen unfortunately as well. Looking at underzone's tracert, I am reaching the same location in the tracert.
Tracing route to history.ahp.us.army.mil [147.248.13.163]
over a maximum of 30 hops:
1 <1 ms 3 ms <1 ms 192.168.0.1
2 26 ms 17 ms 130 ms losubs.subs.bng1.th-lon.zen.net.uk [62.3.80.17]
3 17 ms 16 ms 18 ms ae1-177.cr2.th-lon.zen.net.uk [62.3.80.38]
4 19 ms 151 ms 166 ms xe-8-2-2.lon10.ip4.gtt.net [77.67.66.225]
5 97 ms 95 ms 95 ms xe-7-0-0.nyc24.ip4.gtt.net [89.149.181.218]
6 141 ms 145 ms 258 ms as209.nyc24.ip4.gtt.net [199.229.229.206]
7 119 ms 118 ms 118 ms chr-edge-03.inet.qwest.net [67.14.35.50]
8 157 ms 170 ms 171 ms 65.158.208.218
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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.
Trace complete.
-
Timed out for me to, Plusnet using Google DNS servers
PS. Works fine on my mobile via Three
-
Not working here. Plusnet using OpenDNS.
-
I think it is worth noting that in this case DNS does not matter. The IP is being resolved correctly, it is more the route that your ISP is pushing your packets through to reach the destination.
-
PS. army.mil is OK, just the subdomain history.army.mil that wont load.
-
The last hop wont be pingable even if the site loads, forgot to mention that.
Is odd the inconsistencies.
Thanks guys.