I don’t know if it’s the host, the database, or some content on the blog, but the last few days I’ve had spotty results finding my way into the wonderful world of Listics.
Maybe this trace route information tells it…
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Frank Paynter>tracert listics.com
Tracing route to listics.com [64.202.163.180]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.0.1
3 9 ms 9 ms 9 ms 76.210.67.254
4 10 ms 9 ms 9 ms dist1-vlan60.mdsnwi.ameritech.net [65.42.115.242]
5 9 ms 9 ms 9 ms bb2-g1-0.mdsnwi.ameritech.net [65.42.115.100]
6 14 ms 14 ms 13 ms 151.164.93.209
7 15 ms 14 ms 14 ms ex2-p9-0.eqchil.sbcglobal.net [151.164.42.141]
8 15 ms 14 ms 14 ms gar8-p390.cgcil.ip.att.net [12.122.79.89]
9 60 ms 59 ms 60 ms tbr2030801.cgcil.ip.att.net [12.122.99.66]
10 63 ms 64 ms 63 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
11 59 ms 59 ms 59 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
12 63 ms 62 ms 63 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
13 62 ms 61 ms 61 ms tbr2-cl1592.phmaz.ip.att.net [12.122.10.82]
14 60 ms 59 ms 59 ms 12.122.108.65
15 57 ms 57 ms 57 ms 12.122.255.106
16 57 ms 57 ms 57 ms mdf001c7613r0004-gig-12-1.phx1.attens.net [63.241.130.174]
17 * * * Request timed out.
18 59 ms 59 ms 58 ms linhost211.prod.mesa1.secureserver.net [64.202.163.180]
19 59 ms 62 ms 60 ms linhost211.prod.mesa1.secureserver.net [64.202.163.180]
Trace complete.
Why do they have to send me all around Robin Hood’s barn to get me to my domain? And who owns that node at number 17 and why is it timing out? Are others experiencing this problem?
(My question reminds me of the email administrator who send out the email to all his subscribers to tell them that the email system was down….)
{ Comments on this entry are closed }
