That's not entirely true (see below) but even it it were, why couldn't they handle the volume?
Not enough time to prepare?
Not enough taxpayer money invested?
Exchange agencies walk back high-traffic hype:
Other exchanges have had to pare down their initial statistics. Covered California, that state’s subsidized insurance exchange, initially claimed that its website had received 5 million hits on October 1. They later had to revise that number down 87 percent, to 645,000. KUSI-TV in San Diego is reporting that not one policy has yet been sold on the California exchange.
According to Megan McArdle, high traffic alone doesn’t explain why the federal healthcare.gov website is having so many issues. For example, the drop-down boxes for security questions aren’t working, which shouldn’t be a traffic-related problem. “The drop-down thing is mystifying,” a programmer source told McArdle. It “could very easily be because deadline pressure caused them to take some shortcuts that impacted their ability to scale.”
Five outside technology experts interviewed by Reuters, however, say they believe flaws in system architecture, not traffic alone, contributed to the problems.
For instance, when a user tries to create an account on HealthCare.gov, which serves insurance exchanges in 36 states, it prompts the computer to load an unusually large amount of files and software, overwhelming the browser, experts said.
If they are right, then just bringing more servers online, as officials say they are doing, will not fix the site.
“Adding capacity sounds great until you realize that if you didn’t design it right that won’t help,” said Bill Curtis, chief scientist at CAST, a software quality analysis firm, and director of the Consortium for IT Software Quality. “The architecture of the software may limit how much you can add on to it. I suspect they’ll have to reconfigure a lot of it…”
One possible cause of the problems is that hitting “apply” on HealthCare.gov causes 92 separate files, plug-ins and other mammoth swarms of data to stream between the user’s computer and the servers powering the government website, said Matthew Hancock, an independent expert in website design. He was able to track the files being requested through a feature in the Firefox browser.
Of the 92 he found, 56 were JavaScript files, including plug-ins that make it easier for code to work on multiple browsers (such as Microsoft Corp’s Internet Explorer and Google Inc’s Chrome) and let users upload files to HealthCare.gov.
It is not clear why the upload function was included.
“They set up the website in such a way that too many requests to the server arrived at the same time,” Hancock said.
He said because so much traffic was going back and forth between the users’ computers and the server hosting the government website, it was as if the system was attacking itself.
Hancock described the situation as similar to what happens when hackers conduct a distributed denial of service, or DDOS, attack on a website: they get large numbers of computers to simultaneously request information from the server that runs a website, overwhelming it and causing it to crash or otherwise stumble. “The site basically DDOS’d itself,” he said.
http://www.forbes.com/sites/theapot...eral-exchange-so-far-is-in-the-single-digits/