Tag Archives: Http

In the first month of this fresh new year of 2009, I am here again to report the uptime record for January 2009. Before I go with the details, you can have a look at the table below. They represent the average uptime and critical time during January 2009 in all of our servers for FTP, HTTP, MySQL, SMTP, and POP services.

Service % Time OK % Time Critical
FTP 99.991% 0.009%
HTTP 98.996% 1.004%
MySQL 99.989% 0.011%
SMTP 99.990% 0.010%
POP 99.979% 0.021%

FTP Service
FTP, important issue! It is needed when you want to upload your files into your websites. So, I clearly understand that you will find it annoying to find your FTP unaccessible. Anyway, our January’s FTP service uptime record showed that we reached 99.991% “okay” time and only 0.009% critical time reported. We gladly report that we met what you’ve expected.

HTTP Service
We also realize HTTP service is also significant for your website. We understand how inconvenient for you if your website is unaccessible by your visitors, especially when your site is critical and very important for your business.

For HTTP service in January, we reached 98.996% uptime and 1.004% critical time reported. We are really sorry that we didn’t meet 99.99% uptime guarantee for HTTP in January. It was caused from our scheduled maintenance to improve the performance of our servers for your further satisfaction.

MySQL Service
MySQL service is very important for dynamic website with MySQL database. As database records your customers’ registration data, e-commerce data, or archived materials; it is crucial to have the service available.

In January 2009, our MySQL service was 99.989% up and 0.011% critical time only. It means we actually have a rounded 99.99% uptime for MySQL service and we are glad that we met your expectations.

SMTP and POP Service

E-mails service is very important as with e-mails, you contact and get contacted by people. In delivering e-mail services, we report two records, SMTP and POP services. For SMTP service, we delivered 99.990% uptime and 0.010%. We are happy that we didn’t disappoint you in delivering the service.

And for POP service, we performed 99.979% uptime and there was 0.021% critical time in January for POP service. It showed that our okay time for POP was around 99.98% last month and we regret that we performed 0.02% critical time rather than just equal to or less than 0.01% critical time as there was regular maintenance to provide better performance in the future.

Last, we’d like to thank you for your kind understanding, patience, and loyalty towards our service and also we thank you for the time you have spent to read this uptime record. We’ll be back again next month as usual for February 2009 uptime.

Regards,
Gabrielle

As it has been done for the last two months, we are now here again to report completely our uptime fact in December 2008. Averagely, the uptime record has been listed as below:

Service % Time OK % Time Critical
FTP 99.98% 0.02%
HTTP 99.99% 0.01%
MySQL 99.29% 0.71%
SMTP 99.29% 0.71%
POP 99.28% 0.72%

FTP

Averagely, for FTP service, we reached 99.98% uptime, meaning that we had 0.02% critical time. This was 0.01% less than guaranteed and we apologize for the inconveniences that might have been caused. The critical time was caused by schedule maintenance in our server.

HTTP

Our website service (HTTP) uptime fact in December 2008 meets the uptime guarantee of 99.99%. There was only 0.01% critical time as estimated in the uptime guarantee. And we proudly inform that we met the reliability standard here.

MySQL, SMTP, and POP

Unfortunately, our MySQL, SMTP, and POP service in December showed a little below the standard guarantee. MySQL and SMTP reached out 99.29% okay time in the server averagely while our POP service was around 99.28% up.

This means that we had about 0.71% critical time for MySQL and SMTP. Furthermore, there was 0.72% critical time for the POP service. We realize this must have been an awful situation for your website. We are really sorry and apologize for the inconveniences as the regular scheduled maintenance affected the server.

However, we constantly improve our service in each moment and our admins are always there to help out. We will never let you down and we will never do nothing to improve as customer satisfaction has been our first priority since we started. Thank you once again for your loyalty and attention.

Regards

Basically nowadays, since http 1.1, one IP address can host many domain names. For examples: abc.com, def.com, ghi.com, etc are shared in one IP address like 77.898.232.10. This has been common and transparent to most users.

To know how many domains are hosted in one IP, you can reverse your IP address and use domain check. Reversing IP is the easiest way to find all the .com, .net, .org, .biz, .us, and .info domains hosted on one IP address. Enter an IP address and you will get the list of domains hosted on the same IP.

What is actually the purpose of it? It is definitely because shared IP, used for many domains, affects  your site from the purpose of SEO and website filtering issue. How is it so?

From SEO Purpose

One method done by popular search engines like google, yahoo, msn, etc of detecting a website is based on its IP address. Usually, if websites are in the same IP address, search engines will consider that it is most likely they are operated by the same individual.

So unfortunately, search engines will devalue links from web sites pointing to other web sites hosted on the same IP address. On the contrary, search engines will highly value links from web sites hosted on different IP addresses as they consider the domains are operated by different individuals.

However, an outstanding Search Engine Optimizer will be able to ensure that all of their domains are registered under different registrars with different registrants. They do not use the same template on more than one web site and erase all traces showing that their sites are operated by the same individual.

But anyway, it will be better to prepare for precautions right?!

And from Website Filtering Issue,

Usually, many domain names that are hosted within the same IP address (shared IP) will  also gain problems when there is website filtering based on IP address. Why? It is because when a website is blocked based on its IP address, it will result on overblocking of the other websites hosted under the same IP too. Shared IP host many domain names. That means if one website is blocked based on its IP, the others will get blocked too as they share the same IP.

Take as an example when abc.com contains adult contents in the websites. And when there’s website filtering to block adult sites based on IP address, the other websites in the same IP will also be blocked. No matter they have no pornography at all, they will also get the effect from overblocking as they share the same IP. I am sure you have no willing of this happening to your website.

So What?

Well, if you think your site is unimportant, then no need to consider about it. However, if your website is very critical and all your life is in it, I suggest that reversing IP is very necessary to be done to find out what other domains are hosted under that same IP, IF your site is hosted within a shared IP address.

~Gabrielle Capstick~