Happening for me right now too it’s very frustrating.
I’m from Area-52 currently in a group from Zul’jin and everybody is stuck with OCE ping.
Nya Heroic
TCP 192.168.0.3:29875 24.105.32.112:3724 ESTABLISHED
TCP 192.168.0.3:32224 103.4.115.150:3724 ESTABLISHED
TCP 192.168.1.10:51357 103.4.115.252:3724 ESTABLISHED
TCP 192.168.1.10:63969 24.105.34.190:3724 ESTABLISHED
Turalyon - ruining our mythic carapace prog.
TCP 192.168.1.71:62311 24.105.34.10:3724 ESTABLISHED
TCP 192.168.1.71:63294 103.4.115.252:3724 ESTABLISHED
Jukie - Turalyon
Ny’alotha Mythic
9:00pm - 9:20pm, same problem occurred last week but we stuck through it 9-12pm CT
Abradekay-Turalyon
Nya’lotha Mythic
10pm EST
TCP 103.4.115.252:3724 ESTABLISHED
TCP 24.105.34.10:3724 ESTABLISHED
Every time I’m trying to do a M+ with my guildies we’re always lagging with 200+ ms. Please just fix this lag, it’s making me not want to do dungeons/raids at all.
Connected again to 103.4.115.145, 300 ms.
TCP 192.168.42.142:57754 24.105.32.148:3724 ESTABLISHED
TCP 192.168.42.142:58085 103.4.115.145:3724 ESTABLISHED
10 pm EST
Server Ragnaros
Instance: Mogushan Palace
Calieda-Arthas
Hellfire Citadel
TCP 192.168.0.197:50917 24.105.33.109:3724 ESTABLISHED
TCP 192.168.0.197:51495 103.4.115.191:3724 ESTABLISHED
4/5/20 - 00:43
Heroic Hellfire later on: 4/5/20 - 01:12
TCP 192.168.0.197:52640 24.105.34.99:3724 ESTABLISHED
TCP 192.168.0.197:52860 24.105.32.97:3724 ESTABLISHED
Same here, this sucks a lot!
OMG, in my netstat test, using an ipv6 tracker, it connects me to france and it never goes through Irvine, California, United States of America (24.105.34.99), it happens to me in any instance Boralus dungeons raid BG etc etc
And the ip that many show 103.4.115.245 and 103.4.115.194:3724 is from singapore
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| router.charter.n3t - 0 | 499 | 499 | 0 | 0 | 5 | 0 |
| 072-031-136-077.res.spectrum.c0m - 0 | 499 | 499 | 6 | 10 | 24 | 11 |
| 071-046-009-133.res.spectrum.c0m - 0 | 499 | 499 | 7 | 11 | 22 | 9 |
| bundle-ether34.orld71-car1.bhn.n3t - 0 | 499 | 499 | 8 | 12 | 22 | 10 |
| 072-031-188-170.res.spectrum.c0m - 0 | 499 | 499 | 9 | 13 | 24 | 13 |
| bu-ether44.tustca4200w-bcr00.tbone.rr.c0m - 0 | 499 | 499 | 7 | 16 | 27 | 16 |
| 66.109.5.131 - 0 | 499 | 499 | 12 | 24 | 86 | 24 |
| ae-15-312.pr0.dca10.tbone.rr.c0m - 0 | 499 | 499 | 15 | 23 | 99 | 78 |
| ae1-br01-eqmi2.as57976.n3t - 1 | 495 | 494 | 0 | 58 | 136 | 57 |
| xe-0-0-0-1-br01-eqat2.as57976.n3t - 0 | 499 | 499 | 50 | 56 | 128 | 55 |
| et-0-0-4-br02-eqch2.as57976.n3t - 0 | 499 | 499 | 50 | 58 | 202 | 59 |
| et-0-0-1-pe01-eqch2.as57976.n3t - 0 | 499 | 499 | 53 | 60 | 179 | 55 |
| 24.105.62.129 - 0 | 499 | 499 | 50 | 54 | 67 | 55 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
Edited net to n3t and com to c0m. This was just inside an M+ ToS 16.
TCP 24.105.33.242:3724 ESTABLISHED
TCP 103.4.115.236:3724 ESTABLISHED
Cyntech - Bleeding Hollow
Nyalotha Mythic
Evening (7:30 EST). I am in the mountain time zone, but my entire raid is lagging. We’re all over NA.
TCP 192.168.1.49:62831 24.105.35.230:3724 ESTABLISHED
TCP 192.168.1.49:63627 103.4.115.191:3724 ESTABLISHED
Maiv - Ragnaros
BoD Mythic
22:40 GMT -3
TCP 192.168.0.14:51418 24.105.32.148:3724 ESTABLISHED
TCP 192.168.0.14:52268 24.105.39.117:3724 TIME_WAIT
TCP 192.168.0.14:52340 103.4.115.191:3724 ESTABLISHED
Mokenuf - Ragnaros
BoD Mythic
22:45 GMT-3
TCP 192.168.0.14:51418 24.105.32.148:3724 ESTABLISHED
TCP 192.168.0.14:55972 24.105.35.75:3724 TIME_WAIT
TCP 192.168.0.14:55994 103.4.115.193:3724 ESTABLISHED
Mokenuf - Ragnaros
Ny’Alotha Mythic
00:21 GMT-3
Used wireshark to identify why my ms when through the roof during horrific visions:
I am connecting to 103.4.115.193
Looks like the server is in Singapore?
I’m physically in the midwest US region and play on Bleeding Hollow. Only happens when I enter an instance of any kind.
Characters: Badhaigene, Genekeen, Savagene, Geneforprez
Has been observed in Horrific Visions, M+ and Nyalotha
Has occurred at all hours, but I mostly play in the evening after 7:30 pm.
This has been the case since around that time.
5 21 ms 12 ms 11 ms be-62-ar02.taylor.mi.michigan.comcast.n3t [68.86.167.9]
6 23 ms 22 ms 23 ms be-33668-cr02.ashburn.va.ibone.comcast.n3t [68.86.90.13]
7 38 ms 36 ms 42 ms be-10114-cr02.56marietta.ga.ibone.comcast.n3t [68.86.85.10]
8 48 ms 51 ms 51 ms be-11423-cr01.houston.tx.ibone.comcast.n3t [68.86.85.22]
9 85 ms 84 ms 75 ms be-11523-cr02.losangeles.ca.ibone.comcast.n3t [68.86.87.173]
10 74 ms 73 ms 73 ms be-11599-pe01.losangeles.ca.ibone.comcast.n3t [68.86.84.194]
11 74 ms 130 ms 78 ms 66.208.233.214
12 75 ms 76 ms 75 ms i-93.1wlt-core02.telstraglobal.n3t [202.84.253.85]
13 218 ms 211 ms 209 ms i-10406.sydo-core04.telstraglobal.n3t [202.84.141.226]
14 211 ms 212 ms 211 ms i-91.sydo10.telstraglobal.n3t [202.84.222.198]
15 214 ms 213 ms 240 ms unknown.telstraglobal.n3t [210.176.152.33]
16 207 ms 211 ms 237 ms 137.221.85.35
17 208 ms 206 ms 214 ms et-0-0-0-pe02-eqsy4.as57976.n3t [137.221.85.71]
18 207 ms 206 ms 206 ms 137.221.66.147
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
TCP 10.72.240.118:53833 103.4.115.193:3724 ESTABLISHED
TCP 10.72.240.118:63405 24.105.35.230:3724 ESTABLISHED
Hésher - Ragnaros
Ny’alotha Mythic
10:25 PM GMT-5
Third time posting about this in the last few weeks, have had to drop out of numerous dungeons and raids. Only happens in instance zones. This was taken inside a heroic Atal’Dazar.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------|------|------|------|------|------|------|
| testwifi.here - 0 | 271 | 271 | 0 | 0 | 3 | 0 |
| ip98-161-30-1.om.om.cox.net - 0 | 271 | 271 | 1 | 6 | 854 | 2 |
| 68.13.10.174 - 0 | 271 | 271 | 1 | 1 | 5 | 1 |
| 68.13.9.241 - 0 | 271 | 271 | 1 | 1 | 11 | 1 |
| chgobprj01-ae0.0.rd.ch.cox.net - 0 | 271 | 271 | 10 | 12 | 37 | 11 |
| 68.105.30.218 - 0 | 271 | 271 | 11 | 17 | 466 | 13 |
| ae1-br01-eqch2.as57976.net - 0 | 271 | 271 | 11 | 47 | 1206 | 12 |
|et-0-0-0-pe03-eqch2.as57976.net - 0 | 271 | 271 | 11 | 15 | 102 | 11 |
| 24.105.62.129 - 0 | 271 | 271 | 12 | 12 | 17 | 12 |
|____________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Could we please get some clarification on this? Why am i being pushed from Midwest US and Chicago data centers to the UK to do instance zones?
Same here, east coast server and getting AU ping. Was only in raids for me but now it’s also in instances. Missed a key timer because of it.
So I did a few things on Duskwood on Sunday night (April 5) and hopped between characters and zoned into the garrison at 11:25PM, 11:45PM, and 11:53PM (EST server time) and got dumped on to Oceanic servers every time. 103.4.115.188, 103.4.115.179, and 103.4.115.143 respectively.
Did a Trial of the Champion on heroic at midnight and ended up on a US server (24.105.33.140) like it’s supposed to be and then zoned into the garrison again at 12:26AM and was correctly placed on a US server (24.105.35.231).
For those wondering, US peak period is mid-morning to early afternoon Sydney time. I find it difficult to believe that thousands of US players were loading Australian servers during the mornings for several weeks and managed to escape notice and not trigger an internal investigation on its own.
Have to wonder how poor their data tracking and analytics are if players need to keep reporting this for an extended period of time. They track so many customer metrics how could this slip past?
Drakuloth - is there anything we can do in the interim as a work around here? Anything you’re seeing from your end? It’s going to suck if we lose another raid week on this, progress on N’zoth mythic is a nightmare with this much latency.
Had this happen Thursday night during raid. Made doing Mythic Xanesh essentially impossible. Also just had it happen in a vision.
Outside the instance, totally fine, 30-50 ms. Inside the instance ~250+ ms.