Now, if this mention is unexpected, that's one thing. However, if you've done something to generate publicity, that's quite another. If you've intentionally generated the publicity you had better ensure that your webserver can take the heat. Radio Rickshaw didn't do this.
Recently, Rickshaw Boy’s Radio Rickshaw web site went down due to technical problems. Unfortunately, the web site went down shortly after a major press release had been sent out. Now the site and PodCast feed are fully up and running again along with all of the rickshawboy.com and radiorickshaw.com e-mail addresses.
We've all heard the adage that it costs more to create a new customer than it does to keep an existing one. In essence, Radio Rickshaw attempted to create a bunch of new customers via a press release, and then lost most of them because their server went up in smoke. Fixing the problem and releasing another press release, while logical, still amounts to attempting to regain those lost customers from the first fiasco.
This situation is much more likely in podcasting than in normal web hosting. Podcast files are big and it takes an awful lot of server space and bandwidth to server them up. Don't be a Radio Rickshaw. Ensure that your server's robustness is on the list of things to check before launching any major marketing efforts.
