New Server!
NetworkSince several people had complained about downtime and connection problems, again, I decided to look deeper into the problem and uncover the true source of the downtime.

It turned out there was a hop along the traceroute that most people followed that was causing the error. One of the hops nearest to the server would be fine for a while, then for no apparent reason, would time out or go to really high ping rates, then go back to normal. The ping rate spiking would cause CloudFlare to think the server was offline, which showed you the offline page, then once the ping rate recovered, it would show like normal.

My host has put in a support ticket with the network that supplies that server to solve the issue.

In the meantime, we've been moved to a new server to, more or less, avoid the issue. We're on newer hardware, a newer server stack, a completely different section of the host's network, and should not be seeing any of the recent problems we had been.

I've been with this hosting company for about 8 years now in various hosting plans and had never had a problem until a couple of months ago when I was moved to the "s" server stack. We're now on the "p" server stack and should see a difference in performance.
No Comments have been Posted.
Post Comment
Please Login to Post a Comment.
Rating is available to Members only.

Please login or register to vote.

No Ratings have been Posted.