Getting greeted by a 1,200-player queue when all you want to do is snag a spooky Mercy skin is a special kind of heartbreak. I booted up Overwatch 2 a few days ago, coffee in hand, ready to dive into the 2026 Halloween Terror event. Instead, the game welcomed me with a loading screen and a number that kept ticking up, not down. My excitement curdled into that familiar dread—you know, the kind we thought we left behind back in 2022.

I wish I could say Blizzard’s servers have learned their lesson, but here we are, four years later, and the same old ghost is haunting us. The moment the event went live, login queues ballooned. Players across North America and Europe started reporting waits ranging from a few hundred to over four thousand. A couple of my squad mates even got booted mid-game, right as we were about to capture the point on Eichenwalde. One of them just sighed over voice chat, "Yep, it's October again."

It doesn't take a detective to figure out what's going on. The Halloween event is the obvious culprit—a shiny new battle pass, limited-time skins, and those deliciously chaotic Junkenstein missions pull in a massive wave of players. The community forums are buzzing with theories, but the consensus is simple: the servers just can't handle the sudden spike. Back in the day, Blizzard blamed DDoS attacks for the launch-week queues, and while that might have been true then, this time they've stayed quiet. No statement, no acknowledgment, just the silent hum of overloaded matchmaking servers.

I'd like to think I'm a patient person. I can stare at a queue counter for a while, maybe scroll through my phone. But when that counter finally hits zero and the game spits out an "Unexpected Server Error"—well, let's just say my controller started looking very throwable. And I wasn't alone. On social media, you could practically hear the collective groan of thousands of players slamming into the same invisible wall. Some posted screenshots of queue positions in the five digits, others showed themselves staring at blank menu screens after getting kicked from a match. The whole situation felt like a tired rerun of a show nobody wanted to see again.

What stings even more is the quality of the matches once you finally squeeze in. Over the years, the switch to free-to-play has done wonders for the game's population, but it also opened the floodgates to something nastier. Toxicity seems to spike right alongside server load during these events. In my first match after a forty-minute wait, our tank spent the setup phase typing insults in all-chat before the doors even opened. The healer immediately muted voice and text chat—a reflex now, like putting on a seatbelt. I followed suit because honestly, I'm here to throw pumpkin bombs, not absorb vitriol. It's become a quiet ritual: log in, join a massive queue, get an error, finally connect, mute all chats, and hope your team manages to have fun despite the chaos.

The servers feel like they're breathing on their last legs—a tired old beast that groans every time the calendar flips to October. Blizzard has had years to beef up infrastructure, and while the day-to-day experience in Overwatch 2 has generally smoothed out since 2022, these seasonal events expose the cracks in the armor. Maybe next Halloween they'll surprise us. Maybe.

For now, I'm taking a different approach. I wait until the witching hour—literally, logging in late at night when the queue shrinks to something manageable. I've even rekindled my love for the versus AI mode in the meantime, where the only salt comes from the bots missing their shots. It's a patchwork solution, a way to chase that spooky Mercy skin without losing my mind. And fingers crossed, by the time you read this, the queues will have died down and we can all go back to complaining about balance patches instead. But deep down, I've already got that sinking feeling for next year's event. Some ghosts just refuse to stay buried.