Rapid Disconnects

I don’t know if this will help anyone else, but I installed an older version of my Nvidia driver ( the one before yesterdays ) and it’s helped. I still disconnect but not nearly as much.

Yep, I updated mine but it solved nothing. I was hopeful. But I think this is a Blizz thing.

I don’t think this has anything to do with internet connectivity between nodes. But I’ll send the info later when I’m back at home.

I didn’t update till late last night, neither new or old seems to fix things.

thats part of my point. my connection to them is gonna be the same across all my toons on the same server, yet the trait of being in a guild seems to be what takes them out. i log in, guild takes abit to load in, i get booted. toons not in a guild get to play for awhile but eventually get booted too.

It seemed like it was fixed for me for an hour or so last night but the dc’s returned.

How is this a connection issue if my banks characters are playable without any dc for hours but any other 70’s or my main is unplayable cause i get constant dc’s after few seconds :roll_eyes:
I mean i can play the game in certain characters like right now i HAVE to play my lowbies because i just can’t play with my 70’s, that is not a connection issue at all

It probably isn’t. But there’s no harm in us all taking 5 minutes to do what they ask just to make sure.

2 Likes

I did not say it was a connection issue. I said they are troubleshooting which includes collecting that connection and path data. They don’t know what the issue is yet.

The information that it happens only to chars in Guilds sounds like really critical info they can use for troubleshooting as well.

They have not settled on a cause for this. They are investigating multiple things and only asked for help on one small part of it so far.

1 Like

I am AMD, still having the issue.

Happening to my main and only my main. I am playing my alt just fine. No issues.

Ojigi-Sargeras - Im able to log in, use abilities, but I am NOT able to chat. Then within seconds disconnected and sent to the login screen. It seems like everyone in the world (Valdrakken city) is standing suspiciously still - also very populated for a Wednesday AM EST morning.

A shutdown/restart will probably fix this?

1 Like

This started yesterday for me, i went to bed waiting for them to fix it. But seems like they are still working on the issue

It seems, every 20 minutes (even less probably) after some interaction, be it a quest turn-in, spell-cast, crafting order, etc., there’s a disconnect.

Addons maybe? Playing on Bloodsail Bucs Classic. Disabled all addons except ACP and Hardcore. Stopped disconnecting.

Addon Control Panel
Hardcore 0.11.22

Suspect:

Leatrix Maps
Leatrix Plus
Questie 7.5.2
RestedXP guides

Having the same disconnect problems on my main as well. Was unable to play on my main without near constant disconnects every 10 seconds even with disabling addons and changing locations in game, but alt characters on another server were perfectly fine.

Not sure if it’s associated or not, but unable to open the WoW Companion app anymore either as of yesterday. Just immediately “Unable to load data from the network” even with uninstalls/rebooting/wi-fi vs data (character selected on it as of last logout was my main).

Perhaps but then again I thought i was ok then got disconnected again. Ive now been connected for 18 min… x fingers

nm went back after posing this and was diconnected.

i havent seen a blizzard post where they acknowledged that there even is an issue

Been running pathping for a while to US West. Here is what I am getting:

 1  192.168.4.1 (192.168.4.1)  3.595 ms  2.795 ms  4.559 ms  2.658 ms  2.532 ms  2.741 ms *  8.656 ms  2.826 ms  2.764 ms  2.999 ms  2.802 ms *  4.863 ms  2.792 ms  2.829 ms  2.776 ms  2.746 ms *  4.641 ms (15% loss)
 2  192.168.1.1 (192.168.1.1)  8.670 ms  3.589 ms  3.462 ms  3.341 ms  4.039 ms  2.951 ms *  9.389 ms  4.122 ms  3.453 ms  3.410 ms  2.972 ms *  10.126 ms  4.317 ms  3.637 ms  3.979 ms  3.534 ms *  3.688 ms (15% loss)
 3  lo0-100.washdc-vfttp-329.verizon-gni.net (100.15.173.1)  6.763 ms  4.361 ms  7.587 ms  4.342 ms  5.476 ms  4.982 ms  4.890 ms  5.425 ms  3.881 ms  3.852 ms  5.196 ms  3.909 ms  4.420 ms  4.305 ms  4.065 ms  4.524 ms  5.439 ms  6.426 ms  6.472 ms  4.741 ms (0% loss)
 4  * * * * * * * * * * * * * * * * * * * * (100% loss)
 5  * * * * * * * * * * * * * * * * * * * * (100% loss)
 6  192.205.36.137 (192.205.36.137)  9.897 ms  10.693 ms  10.359 ms  11.255 ms  11.831 ms  10.168 ms  8.162 ms  8.776 ms  8.316 ms  7.536 ms  10.973 ms  7.955 ms  7.901 ms  8.631 ms  11.328 ms  10.599 ms  10.181 ms  10.985 ms  9.003 ms  7.982 ms (0% loss)
 7  cr82.wshdc.ip.att.net (12.122.135.182)  14.129 ms  9.095 ms  7.929 ms
    cr81.wshdc.ip.att.net (12.122.134.150)  11.368 ms  15.182 ms  16.935 ms  15.604 ms
    cr82.wshdc.ip.att.net (12.122.135.182)  12.368 ms
    cr81.wshdc.ip.att.net (12.122.134.150)  9.732 ms
    cr82.wshdc.ip.att.net (12.122.135.182)  12.469 ms  15.313 ms
    cr81.wshdc.ip.att.net (12.122.134.150)  10.353 ms  15.290 ms
    cr82.wshdc.ip.att.net (12.122.135.182)  15.006 ms  13.442 ms  8.495 ms  15.636 ms
    cr81.wshdc.ip.att.net (12.122.134.150)  10.790 ms  15.491 ms
    cr82.wshdc.ip.att.net (12.122.135.182)  12.828 ms (0% loss)
 8  wswdc22crs.ip.att.net (12.122.135.250)  13.803 ms
    cr82.wshdc.ip.att.net (12.122.135.174)  12.153 ms
    wswdc22crs.ip.att.net (12.122.135.250)  9.831 ms  14.240 ms  14.239 ms
    cr82.wshdc.ip.att.net (12.122.135.174)  10.000 ms  9.310 ms
    wswdc22crs.ip.att.net (12.122.135.250)  12.370 ms
    cr82.wshdc.ip.att.net (12.122.135.174)  10.690 ms  16.997 ms  12.773 ms
    wswdc22crs.ip.att.net (12.122.135.250)  12.776 ms  16.695 ms
    cr82.wshdc.ip.att.net (12.122.135.174)  15.960 ms
    wswdc22crs.ip.att.net (12.122.135.250)  13.598 ms  9.644 ms
    cr82.wshdc.ip.att.net (12.122.135.174)  15.454 ms
    wswdc22crs.ip.att.net (12.122.135.250)  17.169 ms  12.010 ms  9.672 ms (0% loss)
 9  wshdc84crs.ip.att.net (12.122.135.230)  9.569 ms
    cr1.cl2oh.ip.att.net (12.122.116.2)  13.142 ms
    wshdc84crs.ip.att.net (12.122.135.230)  9.680 ms  9.519 ms  12.833 ms  10.839 ms  17.131 ms
    cr1.cl2oh.ip.att.net (12.122.116.2)  14.036 ms  11.262 ms  19.463 ms  16.359 ms  14.902 ms  8.507 ms  17.349 ms  15.102 ms  11.743 ms
    wshdc84crs.ip.att.net (12.122.135.230)  12.253 ms  15.059 ms
    cr1.cl2oh.ip.att.net (12.122.116.2)  11.086 ms  8.790 ms (0% loss)
10  12.122.135.237 (12.122.135.237)  8.456 ms  8.534 ms  11.842 ms
    12.122.135.241 (12.122.135.241)  9.064 ms  9.842 ms
    12.122.135.237 (12.122.135.237)  9.239 ms  8.882 ms
    12.122.135.241 (12.122.135.241)  7.990 ms  9.321 ms  8.538 ms
    12.122.135.237 (12.122.135.237)  9.544 ms  8.917 ms  10.339 ms
    12.122.135.241 (12.122.135.241)  10.529 ms  8.950 ms  7.915 ms  9.612 ms
    12.122.135.237 (12.122.135.237)  9.219 ms  8.161 ms  9.119 ms (0% loss)
11  * * * * * * * * * * * * * * * * * * * * (100% loss)
12  * * * * * * * * * * * * * * * * * * * * (100% loss)
13  * * * * * * * * * * * * * * * * * * * * (100% loss)
14  * * * * * * * * * * * * * * * * * * * * (100% loss)
15  * * * * * * * * * * * * * * * * * * * * (100% loss)
16  * * * * * * * * * * * * * * * * * * * * (100% loss)
17  * * * * * * * * * * * * * * * * * * * * (100% loss)
18  * * * * * * * * * * * * * * * * * * * * (100% loss)
19  * * * * * * * * * * * * * * * * * * * * (100% loss)
20  * * * * * * * * * * * * * * * * * * * * (100% loss)
21  * * * * * * * * * * * * * * * * * * * * (100% loss)
22  * * * * * * * * * * * * * * * * * * * * (100% loss)
23  * * * * * * * * * * * * * * * * * * * * (100% loss)
24  * * * * * * * * * * * * * * * * * * * * (100% loss)
25  * * * * * * * * * * * * * * * * * * * * (100% loss)
26  * * * * * * * * * * * * * * * * * * * * (100% loss)
27  * * * * * * * * * * * * * * * * * * * * (100% loss)
28  * * * * * * * * * * * * * * * * * * * * (100% loss)
29  * * * * * * * * * * * * * * * * * * * * (100% loss)
30  * * * * * * * * * * * * * * * * * * * * (100% loss)
31  * * * * * * * * * * * * * * * * * * * * (100% loss)
32  * * * * * * * * * * * * * * * * * * * * (100% loss)
33  * * * * * * * * * * * * * * * * * * * * (100% loss)
34  * * * * * * * * * * * * * * * * * * * * (100% loss)
35  * * * * * * * * * * * * * * * * * * * * (100% loss)
36  * * * * * * * * * * * * * * * * * * * * (100% loss)
37  * * * * * * * * * * * * * * * * * * * * (100% loss)
38  * * * * * * * * * * * * * * * * * * * * (100% loss)
39  * * * * * * * * * * * * * * * * * * * * (100% loss)
40  * * * * * * * * * * * * * * * * * * * * (100% loss)
41  * * * * * * * * * * * * * * * * * * * * (100% loss)
42  * * * * * * * * * * * * * * * 

I keep getting disconnected every 3 seconds… It’s getting super annoying… Moon Guard, ET

I’m on a Mac too. Started getting DC’d last night, haven’t bothered to log back on since. I’m on East Coast, US-Azgalor. Really hope this gets fixed soon. :bat::crystal_ball:

1 Like

It is so annoying cant accept quest, no access to guild, unable to que for dung and raids. if it lasts to and more 24 hours blizz should give all a free day of play and extend timewalking a day.