If it's not on when it's regularly scheduled, then it's an unreliable master server. If there's not a specific reason for why it exists, that's probably even worse. What you need is a master server that people know how to get to, when it's on, and what it's for. Redundancy is terrible; purpose is necessary.
Let me give a few examples. You've got the main master server; it's on all the time. You decide to make a master so people can visit it. You haven't ensured it'll be on when you say it will, and you don't have any key features that differentiate your MS's purpose from the main. This is wrong.
Then, you've got the main master server, but the host only keeps it on during weekends. You decide to make a master server so people can visit it. It's on only during weekDAYS, and you can ensure it'll be up all that time. This is right.
So, let's see where we're at. We have the main master server, which is very unstable because when it's supposed to be on all the time, it's been increasingly having downtime on random intervals. It also has certain rules to it that restrict certain kinds of netgames. What if someone created a master server that they could ensure was up all the time? What if someone made a master server that purposely doesn't have the restrictive rules that the main master server has? Would that be right?
I had an idea recently. I've got a website, right? I can surely create my own master server, but there's no way that either of my two computers would be able to run it 24/7. So, instead of using my IP, why not use my website's IP? I'd compile the source code, upload it to my website, and get the master server running on that website. Simple. But there's a few problems with that.
First off, how would I activate a master server that's on somebody else's computer? I mean, I've got the administrative capabilities, I'm sure; my control panel has a shell interface that might be of use.... Would I activate the master server by using the shell program? Or do I have to ask my service provider to activate it for me?
And if I did get it running, what about those "memory leaks"? More specifically, what are they and what do they do to the master server? If I have to restart the master server every now and then, that would be inconvenient - I'd rather have the master server restart itself somehow... perhaps, every midnight it automatically runs some sort of script?
And lastly, but certainly not least, how exactly would I display the master server page? I mean, I know I'd add the php page to the website and crap... but where? Does it have to be on the index of the site, or the same directory as the master server?... Does the master server have to be on the index of the site?
The second problem I listed probably wouldn't be too important, but if I could just get those other two problems solved, then I think we could seriously benefit all around from another reliable master server.