[East Coast] Disconnecting Tonight?

Technical Support
In south carolina as well been disconnecting over and over.

edit: I'm not just disconnecting from WoW I'm disconnecting from battle.net too.
As an update i played on Argent Dawn my original server as I am east coast and yes it DC'ed yet again. I've read the other comments and it may be a mostly east coast problem but it seems to have jumped to other areas of the country-continents also.

If this is a blizzard / Bnet problem (I think it is on their end) i wonder if we'll get a blue post to help clarify the issue as either being a taxing on their servers, an outside attack, or what ever is actually causing this.
11/03/2018 06:30 PMPosted by Belgorim
In SC as well. Seeing packet loss within the blizzard network. Posting some pings in here. https://us.battle.net/forums/en/wow/topic/20769749005

Please share those in a new post! Make them see!!!
How about in other Blizzard games and the APP? This morning while I was streaming (never lost connection) I got d/c'd from Overwatch and Wow, both had to wait 30 seconds to a minute before it would reconnect, kept telling to try again later.
SC here same as everyone else. I got fiber 60/60. Everything else is gtg just get WoW51900319 error at random intervals.

And Battlenet keeps disconnecting. I tried the trick to try and force the update notification. But I think my app/game is up to date.

I ran trace I have good connection with Central IP test but there West IP gets bullocks.
Also in SC and have been disconnecting all damn day!
i have 23ms home and fluctuating between 400-3000ms server side
i have played on multiple servers with the same issue

i have zero problems with any other internet-related activity on my computer
I am also getting disconnects about once every 5-10 mins.
Someone on twitter got back to me. There IS something going on for those of us on the east coast. Some backbone server or something is the problem. They said they are looking into it. I’m guessing they are alerting the ones who can fix this problem. They also told me how to get addons and such back, if you reset your folder stuff trying to fix this DC problem.
Has to be happening to more than just the east coast, I'm in Alberta, Canada and I'm getting the same thing happening to me. Disconnecting over and over and over again. Getting disconnected while logging back in as well.

Would y'all be able to run a traceroute and post the results? Please also include what ISP you're with.
11/04/2018 08:46 AMPosted by Zhyxen

Would y'all be able to run a [url="https://us.battle.net/support/en/article/7870"] traceroute[/url] and post the results? Please also include what ISP you're with.

I'm in SC as well, and started experiencing the 319's this morning. I'm willing to provide pathpings; traceroutes etc - just ask. What IP address am I tracing to?

Also - my ISP is Charter Communications (Charter Spectrum)
Go ahead and run the traceroute to the central IP address:

Tracing route to over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 * * * Request timed out.
3 13 ms 8 ms 8 ms 159-111-160-004.res.spectrum.com []

4 10 ms 10 ms 10 ms crr01spbgsc-bue-200.spbg.sc.charter.com [96.34.9
5 12 ms 15 ms 15 ms bbr01spbgsc-bue-3.spbg.sc.charter.com [
6 11 ms 15 ms 15 ms bbr01gnvlsc-bue-800.gnvl.sc.charter.com [96.34.0
7 27 ms 31 ms 31 ms bbr01aldlmi-tge-0-0-0-13.aldl.mi.charter.com [96
8 25 ms 23 ms 29 ms prr01ashbva-bue-3.ashb.va.charter.com [
9 25 ms 24 ms 24 ms eqix-dc2.blizzard.com []
10 47 ms 46 ms 46 ms ae1-br01-eqdc2.as57976.net []
11 48 ms 49 ms 47 ms et-0-0-2-br01-eqch2.as57976.net []

12 47 ms 47 ms 46 ms be1-pe02-eqch2.as57976.net []
13 47 ms 48 ms 47 ms chi-eqch2-ia-bons-04.as57976.net []

14 44 ms 43 ms 44 ms

Trace complete.

For clarification - I am behind a router, and again - using Charter Communications as my ISP. The issue seems to have cleared up, but I will continue to monitor and will provide additional feedback if it continues. I'm very tech savvy - and happy to oblige. :)
Thanks for grabbing that. Overall the results look fine which would be expected if the issue had cleared up. If it does come up again please post a new traceroute so we can try to catch the issue ^_^

Join the Conversation

Return to Forum