It doesn’t happen every time but it does happen more often than not during peak US hours.
Be sure to post your WinMTR and to delete your WTF/Interface/cache folders.
miss u hosie <3
1 Like
Rofl some things never change love you hosie <3
1 Like
This has happened once or twice in the past. It’s pretty rare, but not unheard of and we can test for it pretty easily even if we can’t reproduce it always on our end.
edited: Removing a test requested earlier. We no longer need server IPs. Thanks for the reports!
Let us know the following for the character having the problem
- Character Name/Realm
- What Instance You Were In
- Time of Day/Timezone it Happened in
That’ll give us more info on when/where we need to test to reproduce things. If y’all can reply back we can give it a peek and try to find out if you’re ending up on the wrong server group for some reason.
3 Likes
No need scare people away by asking them to dive into the command line. Use Microsoft’s TCPView utility which will show everything that is needed.
By default everything will be sorted by program alphabetically. The relevant remote addresses will be the ones on remote port 3724.
On my end connections should be to 24.105.3x.x IP’s in the central US datacenter but they’ve sometimes been connected to 103.4.115.x systems upon zoning into instances.
It’s been happening frequently for several weeks and almost always during normal US peak hours. Example from last night I was placed into an Oceanic instance upon zoning into Throne of Thunder and Dragon Soul.
Edit: I’m rolling through repeated Shadow Labyrinth runs on Duskwood at the moment and everything was fine until just now where I got an instance on 103.4.115.155 and latency went into the dumpster.
In the next two instance resets I was placed on to 24.105.32.254 then 103.4.115.155.
TCP 10.0.0.9:51376 103.4.115.229:3724 ESTABLISHED
TCP 10.0.0.9:63755 24.105.34.221:3724 ESTABLISHED
Ragefish(Mal’ganis)
Nyalotha
7-9pm central time
My latency was 18 before entering the raid and like everyone else here and in my raid it spiked to 250ish. It returned to 18 after leaving the raid.
Hello Kaldraydis,
i am having this issue as well with extreme world latency both inside and outside of instances. I am connected through a hard line through google fiber. I have a strong connection to not only state further facts.
pastebin(dot)com/1mUHs81J
pastebin(dot)com/bVfffccJ
C:\Users\bniem>netstat -an | find “3724”
TCP 192.168.86.25:58585 24.105.34.225:3724 ESTABLISHED
TCP 192.168.86.25:59015 24.105.34.77:3724 TIME_WAIT
TCP 192.168.86.25:59056 103.4.115.216:3724 ESTABLISHED
- Character Name/Realm: Bowwjack Area 52
- What Instance You Were In: Ny’alotha
- Time of Day/Timezone it Happened in: 9:40 PM CST
Publik - US-Arthas
Mythic Ny’alotha
10:00 PM CST / 11:00 PM EST
netstat -an | find "3724"
TCP 192.168.86.21:61611 24.105.33.109:3724 ESTABLISHED
TCP 192.168.86.21:61908 103.4.115.158:3724 ESTABLISHED
I walked in exactly at 10 CST and immediately my world ms doubled my home ms. After staying in the raid for 5m my world ms jumped all the way to 250+ where home is still sub 20ms.
My whole server and a bucn of friends from USA have also been experiencing this issue for the past 2 weeks. There is a 1 second delay maybe caused be packet loss and high MS.
Raluka - Ragnaros
Zul’Farrak
10:00 GMT -5
TCP 192.168.42.142:52114 103.4.115.176:3724 ESTABLISHED — ASIA IP
TCP 192.168.42.142:58103 24.105.35.230:3724 ESTABLISHED — NA IP
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|---|
| -192.168.42.129 | 0 | 770 | 770 | 0 | 0 | 4 | 1 |
| No response from host | 100 | 155 | 0 | 0 | 0 | 0 | 0 |
| -10.96.99.53 | 0 | 770 | 770 | 15 | 56 | 166 | 48 |
| -10.95.156.46 | 0 | 770 | 770 | 13 | 61 | 178 | 53 |
| -ae61.edge2.LosAngeles9.Level3.net | 0 | 770 | 770 | 127 | 164 | 316 | 150 |
| -4.69.209.249 | 0 | 770 | 770 | 127 | 164 | 302 | 136 |
| -i-0-4-0-18-peer.tlot02.pr.telstraglobal.net | 0 | 770 | 770 | 124 | 173 | 325 | 155 |
| -i-93.1wlt-core02.telstraglobal.net | 0 | 770 | 770 | 128 | 167 | 313 | 146 |
| -i-10406.sydo-core04.telstraglobal.net | 0 | 770 | 770 | 261 | 309 | 420 | 283 |
| -i-91.sydo10.telstraglobal.net | 0 | 770 | 770 | 260 | 301 | 407 | 273 |
| -unknown.telstraglobal.net | 0 | 770 | 770 | 266 | 322 | 475 | 296 |
| -et-0-0-48-br01-eqsy4.as57976.net | 0 | 770 | 770 | 267 | 317 | 429 | 306 |
| -et-0-0-0-pe01-eqsy4.as57976.net | 0 | 770 | 770 | 262 | 314 | 436 | 296 |
| -137.221.66.145 | 1 | 762 | 760 | 263 | 323 | 475 | 280 |
This happened for our entire raid tonight also. The only person with playable world latency was a raider who was playing from Australia. His ping was 55, everyone else’s was 200+.
We called the raid due to the latency limitations otherwise I’d post the requested stats.
TCP 192.168.1.49:54860 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.49:58176 103.4.115.250:3724 ESTABLISHED
Maiv / Ragnaros
Instance: Throne of Thunder
01:40 AM GMT- 3 (23:42 Realm Time)
From 160ms (my normal ping) to 474ms (unplayable)
Here when im with my normal ping in open world
TCP 192.168.1.49:54860 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.49:58554 24.105.34.185:3724 ESTABLISHED
blizzard’s official stance on this isnt you guys going to pretend like this isnt a real thing that is happening and that its “rare” right? sounds like that from the blue post.
TCP [2800:810:42b:ae13:44d9:d325:a284:d274]:53947 [2a04:e800:5020:1873:f816:4bff:fefe:6e48]:3724 ESTABLISHED
TCP [2800:810:42b:ae13:44d9:d325:a284:d274]:53995 [2a04:e800:5020:1873:f816:4bff:feb5:dc19]:3724 TIME_WAIT
TCP [2800:810:42b:ae13:44d9:d325:a284:d274]:53997 [2a04:e800:5020:1873:f816:4bff:fe25:8bc2]:3724 ESTABLISHED
Fostt/Sargeras
instance chambert of heart
18:40 GMT-3/4:40 realm time
WinMtr
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 2502 | 2502 | 0 | 1 | 7 | 1 |
| 10.17.48.1 - 1 | 2490 | 2487 | 2 | 12 | 193 | 14 |
| 100.72.6.221 - 1 | 2494 | 2492 | 3 | 12 | 232 | 12 |
| 100.72.3.126 - 1 | 2490 | 2487 | 4 | 13 | 233 | 8 |
| 100.72.3.125 - 2 | 2396 | 2369 | 4 | 13 | 253 | 9 |
| 10.242.3.230 - 2 | 2380 | 2349 | 4 | 14 | 376 | 11 |
| 10.242.3.230 - 2 | 2372 | 2339 | 4 | 14 | 253 | 13 |
| 10.242.3.170 - 1 | 2494 | 2492 | 4 | 13 | 187 | 8 |
| 200-32-127-98.static.impsat.net.ar - 1 | 2490 | 2487 | 3 | 14 | 228 | 12 |
| 200-32-127-97.static.impsat.net.ar - 1 | 2494 | 2492 | 4 | 18 | 215 | 12 |
| No response from host - 100 | 502 | 0 | 0 | 0 | 0 | 0 |
| 4.7.26.166 - 1 | 2483 | 2478 | 178 | 200 | 375 | 184 |
| ae1-br01-csla1.as57976. net - 4 | 2169 | 2085 | 195 | 206 | 415 | 198 |
| xe-0-0-1-3-br01-eqla1.as57976. net - 4 | 2193 | 2115 | 198 | 213 | 933 | 200 |
| et-0-0-2-br01-swlv10.as57976. net - 4 | 2177 | 2095 | 198 | 212 | 638 | 205 |
| 137.221.65.133 - 7 | 1973 | 1840 | 197 | 216 | 873 | 206 |
| et-0-0-0-pe02-eqch2.as57976. net - 4 | 2202 | 2126 | 194 | 205 | 395 | 200 |
| chi-eqch2-ia-bons-02.as57976. net - 4 | 2205 | 2130 | 193 | 203 | 398 | 199 |
| 24.105.62.129 - 5 | 2102 | 2001 | 194 | 203 | 439 | 201 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
C:\Users\bniem>netstat -an | find “3724”
TCP 192.168.86.25:61003 103.4.115.245:3724 ESTABLISHED
TCP 192.168.86.25:65528 24.105.32.112:3724 ESTABLISHED
- Character Name/Realm: Boajack Area 52
- What Instance You Were In: Ny’alotha
- Time of Day/Timezone it Happened in 8:14 PM CST.
Hey all, thanks for all the data so far. There’s definitely something odd going on here. Please keep the reports coming - it’ll give us more data to point to. For those who haven’t run the test yet, check this post out:
1 Like
Volmotharax/Area 52
Ny’alotha
1837 PST
TCP 192.168.1.151:52623 24.105.32.112:3724 ESTABLISHED
TCP 192.168.1.151:53836 103.4.115.218:3724 ESTABLISHED
Slapys - Ragnaros
Nighthold Normal
TCP 192.168.1.37:51994 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.37:52460 103.4.115.194:3724 ESTABLISHED
Nighthold Heroic
TCP 192.168.1.37:51994 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.37:52460 103.4.115.194:3724 ESTABLISHED
Nighthold Mythic
TCP 192.168.1.37:51994 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.37:52880 24.105.34.146:3724 ESTABLISHED
Siege of Boralus Mythic
TCP 192.168.1.37:51994 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.37:53043 103.4.115.154:3724 ESTABLISHED
Siege of Boralus Heroic
TCP 192.168.1.37:51994 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.37:53053 24.105.34.58:3724 ESTABLISHED
Battle of Dazar´alor (Mythic)
TCP 192.168.1.37:51994 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.37:53053 24.105.34.58:3724 TIME_WAIT
TCP 192.168.1.37:53106 137.221.103.29:3724 ESTABLISHED
17:30 to 18:00 CDT approx.
We did a temporary solution by having an alt on an LA server invite everyone into the raid and then leave.
On Friday April 3, after drawing 24.105.32.254 and 103.4.115.155 as instance servers, I did several more dungeons on various Duskwood characters which connected to the following:
24.105.35.131
24.105.32.81
24.105.34.19
24.105.33.10
24.105.33.52
24.105.35.131
24.105.33.10
24.105.33.47 (Siege of Orgrimmar)
All with expected low latency but lo and behold tonight, I get into another Siege of Orgrimmar at 9:49pm server
(Maplesyrup@Duskwood) and got assigned to 103.4.115.223 with the expected high lag.
I’m surprised there doesn’t appear to be anything automated in the processes that detect anomalous behavior and alert the operator. Servers punting players on US servers to machines on the other side of the world shouldn’t be expected behavior.