Please Reopen NA East Servers

I cant keep playing at 80 ping on my “home” server, which is chicago, I hate playing there and I hate playing at CA, Please reopen the NA East Servers, you have plenty of money. when the chips are down you guys sell a genji, widow or mercy skin, and make lots of money on heros you nerf to the ground. PLEASE i want my 42 ms latency back.

3 Likes

NA East only opened for patches/new expansion launches to alleviate server load, which isn’t necessary now. Also, Blizzard changed hosts since then, so I don’t know if that location will be available in the future.

On the contrary, it is necessary, because this ruins my player experience, I live really far from Chicago, and the lag I get to play Overwatch2 in is unbearable, i contacted my ISP they told me to contact you guys, i play at 80-100MS playing from Miami FL to chicago and 120ms to CA, meanwhile I was running 48ms to the Washington DC server. With those kind of number changes YES its necessary

2 Likes

Honestly I agree with this sentiment 100%. It’s insane that an area that has a large player base population doesn’t have their own server. So instead we’re relegated to a server that’s closest, central. We end up with a much higher ping.

I had 15ms on the Washington DC server before they removed the it and now I play on 60 - 120 ms depending on the server node I get routed to.

Of course I think Nicole is the only one that reads this forum, and she’s not a Blizzard employee. So it’s not like she can do anything about it even if we plead. As helpful as she is with most topics here, she cannot help us with this one.

1 Like

We live in the same area. My ping to Chicago is 72ms and my connection to Las Vegas (the LA server moved to LV many months ago) is 86ms.

Keep in mind, LAT (latency) is actually Ping + RTT. So the values are about 10–12ms higher than your ping would be.

Taking this into account my latency to Overwatch is the same as my WoW connections — 62ms to Illidan/Chicago and 76ms to Hyjal/Las Vegas.

There may be a Level3 or Equinix quick hop between Miami and DC. I’m not sure.

Which ISP are you using? Can you run a PingPlotter to the game server you’re landing on (IP can be found in the netgraph: Ctrl + Shift + N)?


Edit:

Thank you. I will try though. We’re making progress on the PSN account disconnection bug.

1 Like

I think having servers for an entire half of the country is a pretty big deal…

Multi billion dollar company and forces half the country into awful ping, because they refuse to have servers for it. Genuinely the ONLY multiplayer video game I have ever played where I’m just forced to be hard locked at 80+ ping and it feels like garbage to play.

Obviously you are not someone who can do something about it, I’m just responding to this hilarious sentiment blizzard has of “oh no patches / new expansion? welp time to turn off the servers for half of one of the main countries that plays our games!”

5 Likes

I understand what you’re saying, but Blizzard has only offered 2 permanent NA servers for over 15 years. They also changed hosting companies, so that’s part of the reason I don’t think it’s coming back.

I use Xfinity for my ISP
my pingplotter shows i get 90% packetloss running the route that they route to battle.net, the solution is a dedicated east server. most of us live on the east side, and valorant has servers in georgia where i get 15 ms latency, surely blizzard could do something similar.

2 Likes

Wasn’t meant to be disparaging in any way btw. I honestly really appreciate your assistance on the forum.

Did they change hosting companies approximately 2 years ago? Wasn’t the Washington DC server a permanent server for OW1? I’m only asking because it makes zero sense that in-game ping would jump from 15-20ms to 80-90ms, would that even be explained by the switch of ping to RTT?

1 Like

Are you looking at a node configured to ignore ICMP requests (that’s how PingPlotter tests the connection)?

If it was a 90% loss, you’d never be able to login.

Didn’t take it that way :slight_smile:

No, last year.

Nope, only 2 permanent servers since OW beta.

That switch happened a long, long time ago. The cause is likely really poorly optimized internet routes. As a whole, internet in the U.S. has become much worse in the last 7 or so years. Source: Me. I worked in telecom for more than a decade.

For instance, my ping to Chicago for all games hosted there used to be low 50ms, sometimes even 45ms. Now it’s 56ms to 58ms all the time.

1 Like

Today was at 40% packet loss, definitely blizzard needs to open that Virginia/Washington dc permanently I can’t get my alt accounts past what is considered low rank on dps and I refuse to play tank or support. Another 90 Ms game thanks to their refusal to open the servers back up

We’re connecting from the same place and likely using the same route. Would need to see your connection test to know where the packet loss is happening.

Is it not Google Cloud anymore? I didn’t see PR about them moving to Azure

It is Google Cloud, they have a server in LV.

how do i post that without errors i tried already

Put it on Pastebin, paste the link here, highlight, click </> on the text editor bar.

I was only wondering because of when I noticed the severe jump in latency, which was at the start of OW2. If it was merely because they switched to RTT it would make more sense. Although 20ish ms should be 40ish ms RTT, not 80-90ms.

I’m Canadian, and where I live we have a duopoly. Our internet service isn’t great either because of over population in a small urban center. I wouldn’t be surprised if the poorly optimized routes were entirely because of my ISP, at least in the instance we were discussing. It’s just too weird that it would coincide with a game update, but sometimes coincidences are just that I guess. I’m far from being an expert in this field.

As a side note, do you by any chance know where the Las1 server is located? I noticed that when I have higher latency I’ve been connecting to that server cluster instead of Ord1. But the people in those lobbies that have given me a straight answer appear to be in my time zone. High latency to Las1 is 116 - 140 ms RTT.

They also removed IP address from the Netgraph in-game so I’m not sure it can be run any longer in pingplotter.

Sorry this turned out to be a larger reply than I had originally intended. I appreciate your responses.

1 Like

Packetloss

LAS1 is Las Vegas, the new location of the west coast server. Previously it was located in Los Angeles.

ORD1 is Chicago (ORD is the location identifier for Chicago O’Hare International Airport).

That does seem to be the case. The documentation for WinMTR and PingPlotter were retired over a month ago, so anonymizing the IP for the server make sense if they aren’t reading those tests anymore.

That test is showing 20% packet loss on your local ISP node (like in your neighborhood block) and really high ping to it. I would probably call the ISP about this; those values aren’t in the acceptable limit.