Why did Blizzard underestimate Classic?

Clearly they thought everything would run smoothly if they confidently asked people to give them a $15 to reserve 3 character names.

Yet, If today shows anything its that Blizzard wasn’t ready for the amount of people looking to login and simply make a character name.

GL on launch day.

6 Likes

You don’t provision for 30 minutes. You provision for the first few weeks, and keep your head down in the first 4 hours.

7 Likes

They underestimated nothing. Anyone with half an ounce of intelligence could see that having millions of people login simultaneously was going to have bumps in the road.

Blizzard likely even foresaw the sh*tposts and whines from a minority upset that their highly unoriginal name was taken.

If anything, I tip my hat to Blizzard. Compared to other times in WoW history where there has been millions of simultaneous logins, this was pretty smooth.

5 Likes

That’s a matter of perspective.

Desire to avoid the obvious truth that everyone prefers the original product over the new one.

1 Like

They literally never said anything like that. Reserving your character name early was a perk given to current subscribers. Just because you decided to subscribe for this ONE day, it doesn’t mean that Blizzard asked you to. Take some responsibility for your choices rather than blaming everyone else for how you spend your money.

What exactly does “ready” mean to you? The servers aren’t meant to sustain the ENTIRE population of each realm being online all at once. Literally the only time that happens is on launch days, and if you had taken a hint from WoW’s 15-year lifespan, you’d know that this is an inevitable issue every single time.

Stop crying.

2 Likes

That’s not true at all. It is 100% avoidable if you have good code, good servers, and are actually prepared.

What should they have done? Increase their server capacity by 10x just to handle a one-hour rush of traffic that will taper off and never be that big ever again? This kind of thing was inevitable.

1 Like

That is literally what AWS was made for.

Regarding the topic: Why did Blizzard underestimate Classic?.

Answer: They didn’t. It’s players who cannot get their way, when they want, at the time they want it, that are the ones trying to say there is a problem.

2 Likes

Goodness the derp in this thread.

1 Like

By all means, we would like to see your game.

2 Likes

Population will drop by a third after the first month.

1 Like

which blizz employee are you?

Well, in the words of a black guy, turned white guy, turned ghoulish creature:

“All I want to say is, they don’t really care about us.” -MJ

There’s only 1 high pop server. There’s never going to be another time other than launch day where people are trying to all log in at the exact same time.

1 Like

I didn’t even bother logging on as I knew this would happen so I’m simply waiting till tonight for all of this to blow over.

But from what I can see this was a poorly planned reservation event that has affected a lot of people in different ways.

It was actually a brilliant move by Blizzard to allow name creation. It literally gave them a snap shot of how many accounts to expect and what the server size needed to be to accommodate those accounts. Sure we have layering, but with that also dictates how big the server needs to be to add more layers.

1 Like

I agreed, this is lack of preparation. They have the infrastructure and have done how many stress tests? and they couldn’t get the name reservation working correctly?

I’m not sure if anyone designs their online services to handle 100% of their customer base at the same time