The Burning Crusade: Lag and Instability

The vast amount of coverage I have seen on The Burning Crusade rollout has been positive. I'm having very negative experiences. For the first time since I started playing Warcraft I got to bed early last night. Not because a raid got cancelled, or because I was tired, but because I couldn't actually do anything.

Every quest spawn in Outlands was camped. As a warlock, I'd typically get a couple DoT's on a mob, and some warrior would charge it. DoT's don't tag mobs until they do damage. It was taking, oh, 20-30 seconds for DoT's to tick because of the breathtaking lag. So I'd do about half the damage on the mob, the warrior would do the other half and get all the quest credit. Excellent. At least I was still out mana for the cast.

So I rolled a new Draeni. Every quest spawn in the Draeni starting zone was camped. As a mage, I'd typically get 8 seconds into a 10 second frostbolt cast (did I mention it was laggy?) and a shaman would earth shock the mob, and I'd kill it half and get no credit. Nobody wanted to group, because of the XP penalty.

The Outlands and the new starting zones are all on the same server. How do I know that? They all crash together.

So I went back to my warlock, back to Outlands, and decided to get a guild group together to try the Ramparts. We zone in, the server crashes. Twice. Before the first pull.

Then I get clever. I go to bed early, use flextime for the early in-early out and get home at 4. That would give me 3 hours of playtime before prime time. And they rebooted the servers this afternoon. I got 20 minutes in before the waves of crashes started again.

I'm moving one of my level 60's over to a different server. A server that isn't crashing the outlands over and over and over again. Maybe I'll hit 70 there. Because it's not happening on my main server. So far this patch has been a uniformly horrible experience for me.

Anyone else having bad experiences? Vent (but keep it civil) below.