As TechCrunch traffic continues to grow, a problem is popping up more and more often – the traffic we send to a site when we write about it on its launch day can (and often does) take it down. It’s not that TechCrunch traffic is that massive, but it’s enough that if there’s a bug somewhere in application that wasn’t noticed with small traffic testing, it can be exploited and quickly take the site down. The last week, we’ve averaged one site down per day.
Another problem is that the traffic doesn’t last. See this Alexa chart for Spotplex as an example. There’s a spike, and then most of the people never come back. Hopefully a few stick around, register and tell their friends, but building an application to scale to handle a TechCrunch post is a long term solution to a short term problem.
Startups are noticing, too. Occasionally a new startup tells us they don’t want us to write about them yet, because they aren’t ready for too many eyeballs. We comply, of course. But I hate not being able to write about something that I like.
I’m not sure what to do about this. One solution is to start a new blog to focus on really young startups that haven’t had to deal with any traffic load, and write about them on TechCrunch later. But I like to write about things on TC before anyone else has heard of them, so it isn’t a great solution.
Anyone have any ideas?