Originally posted by Kat on a Hot Tin Roof:
That seemed to be a pretty simple explanation for me. Tickets.com didn't see it coming (smart move there....)
I do not understand all this whining and complaining - the tickets were gone in 35 seconds, is it a wonder most of us didn't get tickets. it was a lucky hit, even if you tried at 4:00:10.... People at 4:00 GOT tickets. The system didn't crash, unable to sell tickets sitting there.
As for tickets.com, you do not build a system for the absolute peak usage, which may occur once or twice a year. If you want them to do that -- to build enough server capacity for 10,000 hits simultaneously in 30 seconds, you better be prepared to pay for it. This should make ticket service charges more like $30, $40 or $50 per ticket instead of $5. Because you have to pay to sustain all that server capacity that's idle 99.4% of the time [note to literalists, the numbers here are EXAMPLES, they serve as an ILLUSTRATION of building out the tickets.com system for peak capacity).
Some folks got tickets, some didn't. This is life. Get over it.
JohnnyBlades, does it not occur to you that by getting passwords from SO many email lists that you should then multiply the number of recipients getting passwords as well? With three venues giving out the password, as well as having it posted on the internet at a free concert site, it was bound to happen the way it did.
I tried to get Simon & Garfunkel tickets, through TICKETMASTER, not Tickets.com, and though I was dialing in on a T1 line at the time the tickets went on sale -- surprise, I didn't get tickets! Out of thousands, but there were that many more people trying. Do I blame Ticketmaster? No, I blame the 15,000 other people trying to get tickets too.