Friendster is an obvious example that comes to mind:
http://www.nytimes.com/2006/10/15/business/yourmoney/15frien...
As Friendster became more popular, its overwhelmed Web site became slower. Things would become so bad that a Friendster Web page took as long as 40 seconds to download. Yet, from where Mr. Lindstrom sat, technical difficulties proved too pedestrian for a board of this pedigree. The performance problems would come up, but the board devoted most of its time to talking about potential competitors and new features, such as the possibility of adding Internet phone services, or so-called voice over Internet protocol, or VoIP, to the site.
Of course that's stupid.
Maybe if they had thought about scaling from the very beginning (like so many startups supposedly waste time doing), they would have had a plan in place to address it without having to bring it up at board meetings.
When Friendster finally hired Joyce Park to lead a reimplementation of the site (in PHP instead of Java) there was so much conflict over this inside the company that they fired her immediately after she finished, ostensibly for blogging. Imagine what Friendster could have done if user-focused, practical people like Joyce were honored and listened to, instead of tossed out like trash.
(I know Joyce. I'd even say she's a friend of mine, and I hope she'd agree.)
http://troutgirl.wordpress.com/2004/06/29/friendster-goes-ph...
Incidently, the blogger above was fired for posting about the release, so it would seem they had some other serious corporate issues beyond performance.
I could not name a single company that folded because they could not handle the luxury problem of scaling. Because really, when scaling is your problem, you have no problem, you've figured out a way to beat the odds on all that other stuff so scaling will be solved as well, one way or another.