this is still happening.
1 Like
TCP 192.168.0.23:50227 103.4.115.172:3724 ESTABLISHED
TCP 192.168.0.23:65039 24.105.32.25:3724 ESTABLISHED
Nyalotha, Mythic at Nzoth. ~8:00pm est
Character: Tzodk-Stormrage
This was happening in an Atal mythic+ just before entering the raid (approx 7:15-7:45pm eastern on Tzodk-Stormrage).
1 Like
TCP 192.168.0.56:63089 24.105.32.112:3724 ESTABLISHED
TCP 192.168.0.56:63149 103.4.115.151:3724 ESTABLISHED
Nyalotha mythic around 8 EST
Character: Chiroe-Area 52
Hey all,
Thanks for the info everyone has posted so far. I just wanted to let everyone know that our WoW team is actively looking into this issue. We will be sharing updates as we get them!
2 Likes
If there is any other info I can provide other than what has been provided, I would happily sit in game all night and provide it / test anything that needs to be tested. Really don’t want to have to call another raid tomorrow.
2 Likes
It seems to only be effecting dungeons on the Kul Tiras side. Just ran a ML and world ping was normal. Tried to do a Tol Dagor and the world ping shot up to 200+.
TCP 192.168.1.123:54863 24.105.32.114:3724 ESTABLISHED
TCP 192.168.1.123:57033 24.105.38.22:3724 TIME_WAIT
TCP 192.168.1.123:57293 24.105.36.157:3724 TIME_WAIT
TCP 192.168.1.123:57309 103.4.115.179:3724 ESTABLISHED
Merekats Mal’ganis Operation:Mechagon JY entrance 7:40pm pacific
been having this the last few days at night. caused me to lag out for 10mins in a horrific vision had to alt f4 out
Schiavtto-Azralon - from 23:10 to 00:10 BRT (UTC-3)
Instance was a mythic lockout of Ny’alotha
TCP 192.168.2.46:55941 24.105.37.156:3724 ESTABLISHED
TCP 192.168.2.46:60183 103.4.115.226:3724 ESTABLISHED
While instanced outside, in uldum, results were:
TCP 192.168.2.46:55941 24.105.37.156:3724 ESTABLISHED
TCP 192.168.2.46:59550 24.105.39.206:3724 ESTABLISHED
Which resulted in good latency. Lost a full raid day due to this, please give it it’s deserved attention.
If it helps in any way, changing to a different difficulty connects me into a close instance (no lag), also logged into my alt which is locked into the same boss but different ID, worked fine with no lag.
Different guild in my realm reported same issue yesterday, staying out of the instance for half an hour did the trick but we couldn’t reproduce it.
We were having issues in Temple, Underrot, Waycrest (such fun healing witches) - world ms is fine, within the first two pulls of the dungeon it’s like pushing heals through hardening cement.
I came to see if this issue was happening and found this thread. *450ms latency in kings rest. Party lead was on storm rage. 9:15pm cst.
will grab more detail if i run across the issue again (hopefully not)
1 Like
Was on Duskwood-US about 45 minutes ago and did a bunch of resets at the Throne of Thunder and got the following servers in this exact order:
103.4.115.225 (25N)
103.4.115.166 (10N)
103.4.115.247 (25N)
24.105.34.114 (25H)
24.105.35.1 (10N)
24.105.35.95 (25N)
24.105.35.45 (10N)
So I noticed that there are a lot of folks from Mal’ganis in this thread which is where two of our group is from. We had someone else make the group tonight and our latency stayed at 31 all night even though it was 250 all day and yesterday in Mechagon (we had a bunch of mecha keys this week).
Thanks, i hope this is finally fixed for this week.
a workaround that has been working so far for our mythic+ group is entering the dungeon to check if its an oceanic server via world ping results and if it is, having everyone leave the instance and reset it.
going back in the 2nd time seemed to make it the proper datacenter. very strange.
That’s a solution for dungeons or heroic/normal raids, the problem comes when you do mythic raiding and you get a oceanic instance, you cant do nothing but wait till that instance expires which we dont really know what the exact time for that is
I am now having this issue as well. Constant 250-300 MS both in world and instances. Internet is fine and other games have no latency issues. Several guildies in raid are also having this issue. Couldn’t finish reclear tonight because of it.
My latency issue seemed to have been fixed but in the recent nzoth vision, around 9.15pm realm time 8/4/2020 the lag started to rise and disconnected 3 times within the vision, and gave me the error WOW51900319
Right now in the chamber of heart with lockik-sargeras, local time 11:40 GMT -3 / real time 9:40
TCP 192.168.0.73:58235 24.105.39.94:3724 ESTABLISHED
TCP 192.168.0.73:58277 24.105.35.131:3724 ESTABLISHED
at 9:44 real time just before I disconnected from a vision and lost my vision
TCP 192.168.0.73:58235 24.105.39.94:3724 ESTABLISHED
TCP 192.168.0.73:58277 24.105.35.131:3724 TIME_WAIT
TCP 192.168.0.73:58529 24.105.39.9:3724 ESTABLISHED
- Eltony - Thrall US
- Boralus
- 10:50 PM EST
TCP 192.168.1.66:57699 24.105.36.174:3724 ESTABLISHED
TCP 192.168.1.66:57812 24.105.32.120:3724 ESTABLISHED
Having World MS issues 150 - 270 constantly anywhere I go. It was really bad on M+ too.
Here with zone being Siege of Boralus at 10:58 pm EST
TCP 192.168.1.66:57699 24.105.36.174:3724 ESTABLISHED
TCP 192.168.1.66:57943 24.105.37.91:3724 ESTABLISHED
Was having high world latency in both Nya’lotha tonight as well as BoD. Completely making game unplayable, cant even see my own casts. Latency 180-340MS world.
Not sure what test are needed 