I've been unsuccessfully trying to connect to
http://www.grc.com - "Is it down now" reports it down for all and has been for 10+ hours.
Tracert tests expire long before getting anywhere near GRC's subnets. Tests on adjacent addresses take differing routes but fail part way through the 'journey'.
| Quote |
C:\Users\Kevin>nslookup
Default Server: dsldevice.lan
Address: 192.168.1.254
> set type=any
> grc.com
Server: dsldevice.lan
Address: 192.168.1.254
Non-authoritative answer:
grc.com
primary name server = grc.com
responsible mail addr = dns2005.grc.com
serial = 2014061905
refresh = 14400 (4 hours)
retry = 300 (5 mins)
expire = 5184000 (60 days)
default TTL = 60 (1 min)
grc.com nameserver = ns4.customer.level3.net
grc.com nameserver = ns6.customer.level3.net
grc.com internet address = 4.79.142.200
grc.com MX preference = 10, mail exchanger = grc.com
grc.com text =
"v=spf1 ip4:4.79.142.192/28 a:client.grc.com a:grc.com ?all"
> |
| Quote |
C:\Users\Kevin>tracert 4.79.142.200
Tracing route to grc.com [4.79.142.200]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms dsldevice.lan [192.168.1.254]
2 34 ms 33 ms 34 ms 195.166.130.221
3 46 ms 39 ms 32 ms link10-central10.pcl-gw02.plus.net [84.93.249.210]
4 35 ms 34 ms 41 ms 195.99.126.182
5 35 ms 33 ms 34 ms core3-te0-10-0-15.faraday.ukcore.bt.net [213.121.193.180]
6 33 ms 33 ms 32 ms peer2-et-10-3-0.faraday.ukcore.bt.net [62.6.201.199]
7 35 ms 40 ms 35 ms 213.137.183.98
8 * * * Request timed out.
9 * * * Request timed out.
10 * ^C
|
| Quote |
C:\Users\Kevin>tracert 4.79.142.192
Tracing route to grctech.com [4.79.142.192]
over a maximum of 30 hops:
1 45 ms 1 ms 3 ms dsldevice.lan [192.168.1.254]
2 33 ms 32 ms 57 ms 195.166.130.221
3 34 ms 32 ms 32 ms link9-central10.pcl-ag07.plus.net [84.93.249.209]
4 33 ms 34 ms 34 ms 195.99.126.138
5 35 ms 43 ms 35 ms core3-te0-0-0-14.faraday.ukcore.bt.net [213.121.193.160]
6 33 ms 33 ms 44 ms peer2-et-3-3-0.faraday.ukcore.bt.net [62.6.201.193]
7 33 ms 33 ms 33 ms 213.137.183.96
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * ^C |
| Quote |
C:\Users\Kevin>tracert 4.79.143.1
Tracing route to 4.79.143.1 over a maximum of 30 hops
1 43 ms 3 ms 2 ms dsldevice.lan [192.168.1.254]
2 52 ms 48 ms 32 ms 195.166.130.221
3 33 ms 35 ms 33 ms link9-central10.pcl-ag07.plus.net [84.93.249.209]
4 33 ms 34 ms 32 ms 195.99.126.138
5 44 ms 37 ms 33 ms core3-te0-0-0-14.faraday.ukcore.bt.net [213.121.193.160]
6 33 ms 33 ms 36 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.195]
7 34 ms 33 ms 33 ms 213.137.183.96
8 * * * Request timed out.
9 * ^C
#Microsoft Windows [Version 10.0.10586]
#14/02/2016-15:56:28.48
C:\Users\Kevin>tracert 4.79.144.1
Tracing route to ae3-276.bar1.Orlando1.Level3.net [4.79.144.1]
over a maximum of 30 hops:
1 49 ms 1 ms 2 ms dsldevice.lan [192.168.1.254]
2 32 ms 33 ms 32 ms 195.166.130.221
3 32 ms 33 ms 32 ms link10-central10.pcl-gw02.plus.net [84.93.249.210]
4 36 ms 35 ms 34 ms 195.99.126.182
5 37 ms 34 ms 33 ms core3-te0-2-0-15.faraday.ukcore.bt.net [213.121.193.176]
6 42 ms 36 ms 38 ms peer2-et-3-3-0.faraday.ukcore.bt.net [62.6.201.193]
7 33 ms 34 ms 34 ms 213.137.183.96
8 40 ms 35 ms 34 ms 10-1-1.ear2.London2.Level3.net [212.187.139.177]
9 125 ms 129 ms 131 ms ae3-276.bar1.Orlando1.Level3.net [4.79.144.1]
Trace complete.
|
Looking at the routing reports, they all seem to go wrong beyond 213.137.183.* which appears to be the edge of the BT network.
Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.
