Limitations of 96MB.com Low End VPS Reviews
I have been writing over a dozen of articles by now talk about good and bad things about VPS providers, so I think it is only fair for me to write something about the “bad” things related to 96MB Low End VPS Reviews.
First, the period I am reviewing the VPS is relatively short. For most of the review-only VPS that I have (i.e., VPS that I did not purchase for myself but just for the review), I will perhaps log into the VPS at most half a dozen times through the review, and collecting the data during this period. Therefore, unfortunately, I can not measure the consistency of the performance. Hence, a bad performance does not necessarily mean the host is using really cheap hardware, but it could just because some abuser(s) are on the node at the time I was taking my readings.
Also, although I have tried my best to register “just as another customer†by using my real name and my personal email address that has nothing to do with 96MB.com, and further hide the domain registration details recently, I can not guarantee that the hosts do not know the purpose I obtain the VPS from them and may possibly offer me some “preferential†treatments. However, most of the hosts these days use automated/instant set up, which, when they do not know exactly when I would sign up, would hopefully prevent them to specially put me on an empty node so that all the test results will be better.
Finally, there are also my own technical knowledge limitations when it comes to Linux and server set up. I am never a Linux nor server expert, and I will never pretend to be one. In fact, the entire idea of having a website up and running on a 96MB server was completely new to me until this post on LowEndBox.com. As such, I have been making many silly errors (as shown in here and here, for example) in some of the reviews that I wrote earlier, and as recent as last Saturday, 96MB.com was down for a good two hours partially due to yet another silly mistake on my end. To me, 96MB.com itself is a learning process, it is the first website that I have set up that have hundreds of visitors every day (and obviously the first web server I have set up that has so much load), the first blog that I have really been pushing myself to write something on every week, the first website that I was writing something that is somewhat serious knowledge that is completely irrelevant to my work and definitely the first one where I am happy to see that so many experts who I have never met are willing to jump in and help me out and makes everything here better. I truly appreciate each and everyone’s comments here and please, feel free to let me know if there is any way we could make 96MB.com better.
I guess my point here is, 96MB.com low end VPS reviews are good indicators of what you may get if you sign up with the VPS provider that was reviewed for. Although I have, to my best knowledge, to do a review that is as fair and as objective as possible, unfortunately we are not living in a perfect world and I am just another person. Therefore, please do not take this as a bible, instead, please use it at your own discretion, and together with many other tips that I have shared in Finding the Right Low End VPS Providers when searching for a VPS provider that is the best to you.
Wish everyone would find the VPS provider that they love!

Perhaps you should look into Nagios for monitoring them over a longer period of time
@lxape: Interesting website you have had in the signature section, is 69MB actually sitting on a VPS with only 69MB of RAM? Is it a full LNMP stack running?
No it’s not
It’s sitting on a shared hosting server with 12GB of RAM
@nice, I was wondering why it loaded up so fast for me haha
Back to Nagios, is it possible to monitor the PHP-FPM using Nagios? I was looking into that for a while and did not found a solution to monitor the PHP-FPM processes properly, unfortunately that is the process that is most likely to fail.
Take a look at http://goo.gl/1c7xp
I don’t think it can monitor the process you mentioned however it can monitor other things such as response times and uptime of the system.
It’s better than nothing I suppose.
If you’re wanting to monitor PHP then you could setup a PHP page on the system that will only work correctly (execute the code correctly) if PHP is running. Then setup a Pingdom monitor that will check the content and look for keywords which the code will produce when the process is running good and won’t produce/display then the code isn’t working/running good.
^Please let me know if you got that so I can further explain if you didn’t
@Ixape: Guess I was a bit too late, but seems I am having an access denied error on the link you sent, I guess it is based on Amazon EC3?
Check this link.
http://goo.gl/W03iX
Should work.