Server Loads, Marketing and Web Hosting Realities, Part Two
A working knowledge of the site features and programming decisions is warranted. The technical contact should know when a service upgrade or account increase is approved before the crisis. Pings, traceroutes, and timing of browser refreshes can test the reported performance of a site’s servers. Shared hosting in particular has downtimes if the account technical details are not monitored. Ongoing maintenance and testing for every web site and domain portal should be compared to weekly and monthly norms. Support that cannot answer immediate server and hosting problems is a drawback to even the best of technical loads and package plans.
Hosting Notifications
Hosting notifications can be warning signs a hosting plan is not too conservative. There is usually a time limit set by the hosting service until the restore or resume functions can no longer be commenced. A web hosting customer can in turn open a support ticket if there is a question of technical server failover or internal hosting error. This may get more prompt customer support than an emailed request to a crisis management team.
Key contacts listed on the account must overlap availability when expected site loads and bandwidth overages may occur. Web hosting account closure should be a planned, slowly implemented staging from server to new hosting account, not a decision made in haste or emergency conditions. The pressure to solve the problem and bring the emergency to a close can often end in a suggested up sell or account level upgrade. But the technical contact must be able to assess quickly where the error actually occurred.