UPDATE: issue resolved as of 09:00 September 11. It was an ISP routing failure (not this site’s server).
This site is inacessible for some Comcast users (including me, I have dual internet connections one of which is Comcast). That explains strangely low traffic today.
It’s now at Comcast Level III support. It appears to be some general routing failure handoff between Comcast and qwest.net, or wider. Nothing I can do except hope that their Level III support team fixes it ASAP. Even Comcast.com seems to be down too through another ISP, thought AT&T internet works to Comcast.com.
The issue is apparently affecting other sites too. For example, I am unable to reach https://blog.macsales.com. That could be a coincidence; I can’t be sure. It appears to be a bi-directional problem, which makes it even more confusing.
The site is up and functional through other service providers such as A&T which I’ve confirmed myself (internet via iPhone cell connection), and also confirmed via one reader.
diglloyd$ traceroute diglloyd.com
traceroute to diglloyd.com (184.108.40.206), 64 hops max, 52 byte packets
1 192.168.1.129 (192.168.1.129) <== diglloyd comcast link
2 * * *
3 c-73-170-32-1.hsd1.ca.comcast.net (220.127.116.11)
4 te-0-3-0-8-sur04.santaclara.ca.sfba.comcast.net (18.104.22.168)
5 22.214.171.124 (126.96.36.199)
6 be-90-ar01.sfsutro.ca.sfba.comcast.net (188.8.131.52)
7 184.108.40.206 (220.127.116.11)
8 be-17-pe02.11greatoaks.ca.ibone.comcast.net (18.104.22.168)
9 snj-edge-03.inet.qwest.net (22.214.171.124)
10 svl2-cntr-01.inet.qwest.net (126.96.36.199) <=== black hole
11 * * *
12 * * *
13 * * *
14 * * * diglloyd$ ping 188.8.131.52 <== the black hole above
PING 184.108.40.206 (220.127.116.11): 56 data bytes
64 bytes from 18.104.22.168: icmp_seq=0 ttl=247 time=16.531 ms
64 bytes from 22.214.171.124: icmp_seq=1 ttl=247 time=17.519 ms
64 bytes from 126.96.36.199: icmp_seq=2 ttl=247 time=20.171 ms