I'm happy to announce that RuneTrack has now moved to a faster, more reliable server with significantly increased uptime!
I'm aware that for the past couple months, the server has been continually sluggish from around 9:30am - 11:30am GMT. This downtime did not affect the majority of RuneTrack's users as it was during the early morning for those in the United States (5:30am - 7:30am Eastern US) and at about mid-day for Europeans. However, the downtime was unfortunately an issue for those in Australia, as it occurred during their peak playing hours in the evening (7:30pm - 9:30pm AEST). Additionally, other server slow-downs were causing minor errors to occur during some of the daily System Updates (though these were quickly fixed the next day).
So, in order to maintain RuneTrack's quick and efficient services, I have now moved RuneTrack.com to a new, more reliable server, which has fully solved the downtime issue.
I apologize for any trouble this downtime issue may have caused, but after extensive monitoring of the server, I'm happy to report that RuneTrack.com is now running at virtually 100% uptime for all timezones.
Furthermore, the server move has fixed those minor errors during system updates, such that all aspects of the daily System Update now function exactly as they should.
Additionally, the server move has also provided the site with a speed boost to allow for faster load times overall, as can be seen in an updated version of the Load Speed Improvement Chart (first used in the April 2, 2010
news post) below: Note: Average load time refers to the time it takes the server to process the page (displayed at the very bottom of every page).
As you can see, RuneTrack's system has become significantly faster from where it was at the beginning of the year, and even just a few months ago, to the point where the load speed really can't get any noticeably faster. With this new server in place, I'd like to reaffirm RuneTrack's promise of providing quick, efficient, and bug-free stat tracking.
Thanks again to everyone who's provided feedback about this issue to help solve it, and for all the continued support!