You’re simply connecting to two different places. Just because you connect to East Coast on both doesn’t mean you are connecting to the same place. It’s also not a problem. As someone who works in IT, seeing someone complain about a 30ms difference in latency makes me cringe.
The normal latency on my original Classic east-coast labeled server was 66-67. The normal latency on my new Classic west-coast server that I decided to restart on the other night was a constant 32-34. I’m in Phoenix, AZ. No, I didn’t restart & change servers because of that, but I did notice that difference when comparing the UI display values.
Huge difference from having 20-30 and then jumping to 60 where spikes put it at 80 to 100… You work in IT and act like that isn’t a big deal for serious pvp’rs gaming…
If you were anything but a call center IT dude you would be wondering WHY there is a difference considering how warcraft servers are structured. Its not just some random lagg here and there it is the Permanent state of the latency guy.
The only fix is to find the data centers for each Classic realm and reroll on the realm type of your preference in the data center with the best latency.
What’s amazing to me is that even though I’m playing with 50-70ms all the time now, in 2005 I had 180ms and it still felt more responsive than classic does. They messed something up.
I am a network engineer and I don’t wonder why. I know exactly why. I told you why. You are connecting to two different places. The server you normally play on is closer to you geographically. It’s that simple.
Blizzard has servers in New York and Chicago and they are both considered “East Coast”. You live closer to one than the other. The End.
Anything less than 150ms is acceptable, especially with the spell batching.
I remember in vanilla my ping was 175 on my first server over a 3mb DSL connection, and in TBC i changed to horde and my ping was 270 to that server on a 10mb cable line. I had no real issues playing.