[Pacific Northwest] You have been disconnected. (WOW51900328)

Okay I don’t count another Blizzard game with issues as truly a “non-wow problem”. Have you had any issues with any games that have nothing to do with battle.net? I have not, but admittedly I haven’t tried to play too many other things.

I did a quick test on my end. I used a VPN to connect to WoW. I then switched from a US East server to a US West server. Disconnected my VPN and tried again. No problem at all logging into a US West server. Unfortunately, all my real characters are on US East.

You CANNOT seriously tell me this isn’t an issue on Blizzard’s end.

1 Like

It’s a classic blame the other guy, kick the can down the road scenario. Why bother spending the resources investigating the issue if you can just blame someone else for it? Blizzard is gonna lose subs over this if it doesn’t get fixed, whereas people aren’t generally going to change their entire ISP. So one of these companies has more incentive than the other…but then again we all know Blizz isn’t too concerned about a handful of west coast subs.

I can’t log into classic but I can retail. So weird

According to Astound Broadband (Wave G) customer chat, service outages in my area (N Seattle) has been resolved. I am able to visit websites that were previously not available. I am still experiencing this “You have been disconnected. (WOW51900328)”.

Are you buy chance playing on a west coast server in retail but east coast in classic? I can’t test this out myself cuz retail isn’t installed on my computer and I don’t want to do that. But I can play on a west coast server in classic, just not east coast.

Status as far as blizzard is concerned is, not their internet, not their issue. You’d think Microsoft had more pull, but I guess not these days.

My only problem with the blizzard explanation is they only let you pathping west coast or central, and both find blizzards server six-blizzardonline-net at 206"period"82"period"82"period"122, its after that they diffe. Central dies right there, west makes it several more hops. So it resolves correctly, and its seeming more like blizzard is not handling the traffic correctly from this ISP now, rather than some transport path is wrecking it.

from this website - us"period"battle"period"net/support/en/article/7871

Central

C:\Users\Tech9>pathping 24"period"105"period"62"period"129

Tracing route to 24"period"105"period"62"period"129 over a maximum of 30 hops

0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
1 192"period"168"period"86"period"1
2 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
3 agg1-pohe-a-be150"period"bb"period"as11404"period"net [174"period"127"period"182"period"18]
4 be6"period"cr1-pohe-b"period"bb"period"as11404"period"net [174"period"127"period"148"period"177]
5 be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
6 six"period"blizzardonline"period"net [206"period"81"period"81"period"122]
7 * * *
Computing statistics for 150 seconds"period"“period”“period”
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192"period"168"period"86"period"1
0/ 100 = 0% |
2 31ms 0/ 100 = 0% 0/ 100 = 0% 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
0/ 100 = 0% |
3 27ms 0/ 100 = 0% 0/ 100 = 0% agg1-pohe-a-be150"period"bb"period"as11404"period"net [174"period"127"period"182"period"18]
0/ 100 = 0% |
4 30ms 0/ 100 = 0% 0/ 100 = 0% be6"period"cr1-pohe-b"period"bb"period"as11404"period"net [174"period"127"period"148"period"177]
0/ 100 = 0% |
5 34ms 0/ 100 = 0% 0/ 100 = 0% be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
100/ 100 =100% |
6 — 100/ 100 =100% 0/ 100 = 0% six"period"blizzardonline"period"net [206"period"81"period"81"period"122]

Trace complete.

=====================================================================

West

C:\Users\Tech9>pathping 137"period"221"period"105"period"2

Tracing route to 137"period"221"period"105"period"2 over a maximum of 30 hops

0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
1 192"period"168"period"86"period"1
2 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
3 174"period"127"period"183"period"70
4 be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
5 six"period"blizzardonline"period"net [206"period"81"period"81"period"122]
6 ae1-br01-eqse2"period"as57976"period"net [137"period"221"period"73"period"33]
7 xe-0-0-0-1-br01-eqsv5"period"as57976"period"net [137"period"221"period"65"period"40]
8 et-0-0-29-br02-eqsv5"period"as57976"period"net [137"period"221"period"65"period"117]
9 xe-0-0-1-1-br02-eqla1"period"as57976"period"net [137"period"221"period"65"period"6]
10 et-0-0-29-br01-eqla1"period"as57976"period"net [137"period"221"period"65"period"0]
11 * * *
Computing statistics for 250 seconds"period"“period”“period”
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-JE1FG14"period"lan [192"period"168"period"86"period"29]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192"period"168"period"86"period"1
0/ 100 = 0% |
2 30ms 0/ 100 = 0% 0/ 100 = 0% 24-113-64-1"period"wavecable"period"com [24"period"113"period"64"period"1]
0/ 100 = 0% |
3 27ms 0/ 100 = 0% 0/ 100 = 0% 174"period"127"period"183"period"70
0/ 100 = 0% |
4 31ms 0/ 100 = 0% 0/ 100 = 0% be4"period"cr2-sea-b"period"bb"period"as11404"period"net [174"period"127"period"137"period"16]
0/ 100 = 0% |
5 — 100/ 100 =100% 100/ 100 =100% six"period"blizzardonline"period"net [206"period"81"period"81"period"122]
0/ 100 = 0% |
6 59ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqse2"period"as57976"period"net [137"period"221"period"73"period"33]
0/ 100 = 0% |
7 56ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-0-1-br01-eqsv5"period"as57976"period"net [137"period"221"period"65"period"40]
0/ 100 = 0% |
8 50ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-29-br02-eqsv5"period"as57976"period"net [137"period"221"period"65"period"117]
0/ 100 = 0% |
9 61ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-1-1-br02-eqla1"period"as57976"period"net [137"period"221"period"65"period"6]
0/ 100 = 0% |
10 225ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-29-br01-eqla1"period"as57976"period"net [137"period"221"period"65"period"0]

Trace complete.

i dunno, that looks more like Blizzard needs to check something on their end. You can’t ping their server either way, but one way goes past their first server and one does not, none of them are losing packets to that server though and it resolves correctly. Granted i do not work for blizzard, or their server hosts, or Astound, but something seems off.

Note these forums wont let me post a URL even though I just pasted text from a tool and their OWN diagnostic website. If you need something from here, copy all, paste into notepad, and set “period” to be replaced by .

You can’t fix stupid but you can work around it sometimes…

1 Like

I still get the same error on Classic, TBC classic, and Retail. I can however access the PTR go figure.

I am extra annoyed that the “resolution” is “go pay for a VPN so you can access the game you pay for on the internet service you pay for”

I play on an east coast server. I can’t even log in to change my server either

1 Like

My twitter is borked :frowning: btag is Jhenipher#1829 if you want to add me tho

Yeah I couldn’t either. I had to connect to a VPN first to switch servers and then disconnect it to test out.

Update: As of 1:47 pst i was able to log into Dalaran, whatever changed, please keep it that way for future patches, it would be hugely appreciated, that being said, thank you for fixing this issue

Update: As of 1:49 PM, I was able to log into Aggramar.

Can’t log in. Reset, reinstall, updates. Reset router. It stops logging in at contact with game server. Then I get disconnect wow 328. I can play classic, and other games but not retail wow… haven’t been able to log in since patch. Over a day in ticket line… seriously? Wtf is going on… so much for the 6mon sub I just payed for

I am now able to log into Malfurion from Seattle area. Seems to be fixed for me on Astound/Wave.

I tried a VPN and it let me log in. Turned it off, and I was able to log in like normal. But I am now also seeing others from Seattle area say they are able to get into the servers. So hopefully the fix is rolling out.

As of 2:27PM I am able to login (North of Seattle) and access my characters
no VPN

I finally got a response from Wave that they were still working on the problem, but that some of their customers were reporting successful connections now. Checked mine, and I can now log in.

Good news indeed!

South Sound area here: Able to log into my east coast servers.

Thanks to whomever posted about proton vpn. It was free, super easy to set up, and let me level. My MS was a bit high at times, but not enough to make a dramatic difference while leveling.

Yep, NW Washington Wave here, 6:40pm PST, am now able to login without the VPN.
So Wave is working on it, if you haven’t tried in the last hour or so, try again without the VPN on and see if they fixed it for you.