Monday, February 13, 2012

Interruptions in Service

This past week has been terrible in terms of up time. First, last week our server went down for over 4 hours due to a power failure at our host. Since then, we have gone down at least twice due to heavy traffic. While there is little we can do about either of these, due to our budget constraints, it is still disconcerting.

Sites go down regularly, all of them, so this doesn't bother us a great deal. It is important to learn from them and try to improve. As I mentioned, budget constraints make improvements difficult at this current time, but there is no question that we need to implement some form of redundancy in order to guarantee maximum up time, independent of our host. I am sure that in the upcoming decade, we will take on such measures.

One thing that we have learned from all of our down times over the years has been our traffic sources reactions to these down times. The most apparent difference in traffic when comparing before and after a prolonged downtime is Stumbleupon. Outside of search results, Stumbleupon is generally our largest source of traffic on a day to day basis. However, if Mizozo goes down for a prolonged time (several hours), Stumbleupon notices and over the course of the next few days we experience a significant drop in traffic from them. Hence, if you run a site similar to Mizozo, and you rely on Stumbleupon for a significant part of your traffic, it is in your best interest to try and maintain as much server up time as possible ... and that is our Tip of the Day for all you content providers.

No comments:

Post a Comment