News

Our SP1 (Special 1) server (from http://nolimitshost.info/hosting/dedicated-servers/) is limited in stock. We currently have only 2-3 of those server configuration and as this is only a special server, we will no longer offer this server configuration after we have used up all our stock.

So if you are interested to buy SP1, it will be on a first-come first-served basis.

Thank you for your continued support.

We have purchased a new server and we are targeting to start with the set up of the new server, cPanel installation, server hardening and account transfers starting tomorrow, February 26 and may last up to February 29.

By tomorrow, we are going to start with the following:

- set up of our new server
- installation of pertinent scripts
- build Apache with required modules
- harden the security of the server
- if time permits we might be able to begin with the account transfer by tomorrow

February 27
- migrate all accounts to the new server
- installation of softaculous and whmphp
- hook up the server to our offsite backup server to perform daily and weekly backups
- set up our Nagios monitoring system to monitor the new server

February 28
- set up of our Nagios monitoring system to monitor the new server

By tomorrow, we are going to update this post with the new server IPs. Please watch out for the updates

Thank you very much for all your cooperation regarding this matter.

The new server is Core2Quad Q9550 with 12MB of L2 cache, 8 GB RAM and 1 TB HDD.

Results as shown by cpubenchmark.net

click image to enlarge

EDIT: February 26, 2010

We are now compiling the apache of the new server Q66001. In a short while, we are going to begin transfer of accounts. To avoid losing updates to your sites, please avoid making updates until we have completed the transfer. Thank you

EDIT: ‎February ‎26, ‎2010, ‏‎11:36 PM EST (Eastern Standard Time)

All accounts with usernames up to letter p have been restored in the new server. Account names from q to z are being restored

Here’s the new IPs for your custom nameservers:

ns1 = 64.191.56.229
ns2 = 64.191.56.230

Please make sure you update your custom nameservers. By tomorrow we are going to suspend all accounts in our old server to make sure you are not updating in the wrong server. If you are using our nameservers then you don’t have to do anything as we have already taken care of that. Thank you.

EDIT: ‎February ‎27, ‎2010, 01:41 AM EST (Eastern Standard Time)

All accounts have been transferred to our server Q66001. We are now going to start migrating WHMPHP over. Please stand by for updates.

EDIT: ‎February ‎27, ‎2010, 02:27 AM EST (Eastern Standard Time)

WHMPHP has been successfully migrated to the new server. We are now setting up our daily offsite backup.

If you are using our nameservers, it should already resolve to server q66001. You can check this by logging to your cPanel and check the IP address. It should be 64.191.56.229.

To avoid losing updates, make sure you clear your browser’s cache, cookies and saved pages before making updates to your sites. Thank you for all your cooperation.

EDIT: ‎February ‎28, ‎2010, 12:15 AM EST (Eastern Standard Time)

As announced in our Twitter, we have now started to suspend all accounts from the old server Quad1. If you are seeing your site as suspended then it’s either you have not changed your nameservers yet or the changes to nameserver IPs have not yet been propagated to your internet provider’s DNS cache. In any case, we have no control over domain propagation and you just have to wait for the domain name to fully propagate. Domain propagation sometimes can take up to 1 week depending on your ISP (internet provider). Thank you

Hello Dear clients and readers,

We just thought of publishing this news as it has been affecting internet connection supplying several datacenters throughout U.S.A.

Apparently, on 2/11 New York time, a radio shack on 6th avenue exploded and after investigating the incident, it was found out that the cause of the explosion was a “manhole explosion” that “sparked a transformer fire”. The explosion or fire cut several fiber optics connection from different bandwidth providers. So until everything has been restored by the internet / bandwidth backbone providers, you might experience some slack in accessing several servers throughout the world connecting through New York fiber optics.