I have noted that our server goes down regularly on your tracker every day during peak hours of use.

After speaking with some technically inclined programmers it has been discovered that the standard method of returning the remote statusing information will not work because the packets returning cannot contain all the information from the server in one go.

This is not a firewall or server issue.

My server, The World of Warcraft Public Vent, is without a doubt the largest and most active voice over ip server in the world with user peaks as high as 980 users. Shortly we will be upgrading to an unheard of 1,500 slots to accommodate an ever growing userbase.

One of our coders has developed a personal means of tracking the user capacity through packet returns and calls to the server, and did this inside 30 minutes of playing around for fun. Essentially that is all we need or desire.

Due to the extreme activity our average user count is much lower than it actually is due to the failure on your current method to call a remote status/capacity function.

I love your graphing feature for measuring activity for the servers here, I just wish/hope that you will update your means of accomplishing this for our server. Thank you GT.

Rathamus, Founder of the World of Warcraft Public Vent

From my understanding, the issue with this is typically the large server takes too long to return the response from the query. As a result GT, determines it to be timed out. I don't believe there are any plans to globally increase this.

Sad day.