I'm not sure why you felt compelled to accuse me of lying. You obviously know I would have no visibility inside your facilities, but the traceroute shows that traffic was not flowing past your border router. So, whether it was a cut line, a switch inadvertently flipped or malfeasance on the part of an employee is irrelevant. From the outside, you had a problem.virtbiz wrote:Ever played that game "2 Truths & A Lie"? :)
Um.... nope and nope. No router problem.baldeagle wrote:There was a router problem at virtbiz.com (used to be CI Host).
traceroute to texaschlforum.com (208.77.216.52), 64 hops max, 40 byte packets
And our only affiliation with the above mentioned former provider is we've rescued PLENTY of their former customers. That place was a pit.
Real story of the outage????? Not hardly. Please don't try to game an old pro.virtbiz wrote:If you'd like to get our real story, it's on our website here:
http://www.virtbiz.com/about/
Wow! So you're going to blame Charles for the problems? Is that what passes for customer service in your world? You'd have been a lot better off by beginning with an apology for the outage, followed by taking full responsibility for it and for getting it fixed. Then, if there were things Charles could do to help, you should have addressed those privately with Charles, not here in an open forum.virtbiz wrote:Correct. I monitor our support ticket system and as has been mentioned, our techs are "on it." There are some issues with regard to the loading of the database and overall optimization. Many of the issues could best be handled via some site administration, and as the site has grown, so too has the overhead. And yes, gzip is recommended, and can be turned on with a little .htaccess work. Our techs have consulted on it and provided some feedback, and that's about what I feel is appropriate for posting in that regard.However, when I look at the site on Web Page Test the TTFB (Time To First Byte) is pretty high (over 3 seconds which is about 10 times what it should be.) They also don't have compression enabled on the web server, which would help speed up the response.
Charles knows where to reach us (or me) if/when needed. If we can be of assistance to anyone else, just holler.
BTW, all you would have to do is configure your servers to compress files in the httpd.conf file, and the customers wouldn't have to learn .htaccess syntax and dive into areas they might not be familiar with. That should not even be a site-configurable option if you care about performance.
After all, Charles is a lawyer. You guys are supposed to be the IT tech experts.