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….)
{ 12 comments… read them below or add one }
Frank,
I ran it from my system and got these systems at the end:
14 49 ms 41 ms 42 ms mdf001c7613r0004-gig-12-1.phx1.attens.net [63.24
1.130.174]
15 41 ms 81 ms 41 ms 63.241.142.126
16 43 ms 42 ms 66 ms linhost211.prod.mesa1.secureserver.net [64.202.1
63.180]
17 44 ms 63 ms 44 ms linhost211.prod.mesa1.secureserver.net [64.202.1
63.180]
I’d suspect your hosting service but AT&T could be having routing problems as well.
Frank,
Yesterday I got many Wordpress errors that stated that your blog could not connect to 31mysql.secureserver.net.
I’d suspect hosting environment problems. I also suspect that you’ve been notified of their issues… :^)
I hope your site stabilizes soon.
Frank
I have had trouble loading your site too
Tracing route to listics.com [64.202.163.180]
over a maximum of 30 hops:
1
weird I put a full tracert into that comment above. In any event Frank the timeout on hop 17 for you is the network edge firewall for your host, secureserver.net
They have acknowledged that the problem is a server issue on their end and they have said that they’d inform when it was fixed. I haven’t heard that it’s fixed yet, but at least the site is back. It still loads slow though.
Sometimes ISPs and hosting dudes entertain themselves by rerouting… because they can. Bet I can gen more hops than you can… or something of the like…
Whatever the cause, bottom line is same: frustrated you, frustrated us…
Frank,
It was painful to hit your URL and NOT see even your stale posts… I hope they get it fixed.
I tracked your ISP and it looks like a technology house in the Parsons Group (GoDaddy, etc) in Arizona.
In a parallel world… Jeneanne wrote that Wordpress.com was also having problems. No coorelation… I hope it clears up before your 10 year event.
before I forget… did you get a free laptop fom Microsoft? Jeneane wants you to give it to her if you do.
Sadly, for Jeneane… I’ll bet you didn’t make that list of market savy bloggers like Arrington, et al. Because you MIGHT hand that baby down the line to a blogger in need.
Wouldn’t that make an interesting meme:
1. Would you take a free “review” computer?
2. Would you keep it, return it or pass it on and to whom?
There’s a whole bundle of ethics behind this one… a sea of disclosure (financial and social).
Sciurophilia, Frank, running rampant in the management of your hosting company.
I couldn’t afford a free Vista enabled laptop, McD.
Appears now that my blog is back on line and performing as well as it ever did. I made Godaddy send me an email yesterday acknowledging that this was a hosting failure and not some lamer “user problem.” Didn’t get it fixed any faster butput a finger on who’s to blame. Not Wordpress, not MySQL/php, not yours truly… no, Bob Parsons’ thin infrastructure is what messed me up ON MY BIRTHDAY. Ahhh, well… another case of getting what you pay for.
On your birthday? Dang, that is so unfair.
Happy birthday, FP. And many happy returns of your gorgeous blog.
I have some kind of WordPress special feature that has me pinging everyone on the planet. I’ve upgraded to the latest and greatest, but … I dunno?