My raid team had this happen yesterday, as well as tonight.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
| 192.168.0.1 - 0 |
201 |
201 |
1 |
5 |
84 |
3 |
| 072-031-128-241.res.spectrum .com - 0 |
201 |
201 |
9 |
16 |
108 |
14 |
| 072-031-007-191.res.spectrum .com - 0 |
201 |
201 |
10 |
19 |
90 |
16 |
| bundle-ether29.tamp27-car2.bhn .net - 0 |
201 |
201 |
14 |
24 |
175 |
20 |
| 072-031-006-178.res.spectrum com - 0 |
201 |
201 |
14 |
23 |
180 |
21 |
| hun0-1-0-5-tamp20-cbr1.bhn net - 0 |
201 |
201 |
14 |
23 |
186 |
17 |
| 10.bu-ether15.tamsflde20w-bcr00.tbone.rr com - 0 |
201 |
201 |
15 |
27 |
170 |
18 |
| 66.109.5.127 - 0 |
201 |
201 |
19 |
29 |
180 |
24 |
| ae-15-312.pr0.dca10.tbone.rr com - 0 |
201 |
201 |
21 |
34 |
182 |
29 |
| 137.221.76.35 - 0 |
201 |
201 |
74 |
85 |
177 |
78 |
| xe-0-0-1-1-br01-eqda6.as57976 net - 0 |
201 |
201 |
75 |
87 |
192 |
77 |
| et-0-0-2-br02-swlv10.as57976 net - 0 |
201 |
201 |
74 |
86 |
188 |
79 |
| 137.221.65.122 - 0 |
201 |
201 |
77 |
109 |
356 |
99 |
| et-0-0-2-br01-eqla1.as57976 net - 0 |
201 |
201 |
74 |
102 |
847 |
82 |
| 137.221.68.81 - 0 |
201 |
201 |
75 |
87 |
219 |
80 |
| lax-eqla1-ia-bons-03.as57976 net - 0 |
201 |
201 |
74 |
86 |
201 |
79 |
| 24.105.30.129 - 0 |
201 |
201 |
75 |
87 |
200 |
81 |
| ________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Same issue with us on Mal’Ganis. Latency is great until we enter Ny’alotha. Ping for almost everyone is 200ms world or higher. Issue only exists inside raid. Going on week 3-4 now.
1 Like
I’ve been leveling characters with friends for the last 2 weeks and we’ve been having this issue as well. Some times when we enter a random dungeon, we all climb up to 221ms world latency and then SLOWLY fall back down after we leave. It’s happened quite a bit that it brought me here to do some research if anyone else felt it as well haha. For us, we play on EDT realms and it’s the same for all of em so far (Dalaran, Stormrage, Area 52, also on Illidan). I’ll post a WinMTR the next time we get in one and it happens.
This is clearly on Blizzard’s end. Can you guys fix this? It has been going on for about a week now. I cant believe this is a capacity issues because the game has some pretty low sub numbers ATM. I’m starting to question why I’m still playing this silly game with how many bugs there has been in this patch.
1 Like
who, me? I am already hardwired. Are you asking me, or the original poster.
PS- my problem with latency is lately in the thousands. 2.5K MS to 17k MS. I think its funny people are talking about 200ms delay like it’s bad. For me, that is a really, really good playing day! . Like, when I have 200ms, is the best of years of gaming, that means wonderful game playing. I can’t even detect lag!
I think my problem is in a whole other world being overseas
1 Like
Is Blizzard going to fix this? We all had 250+ ms yesterday in mythic Ny.
Yeah, it seems to definitely only be an instance server issue.
My raid group (US) ended up on what appeared to be an OCE instance of the raid this week as well.
Yup, same problem here, normally playing around 170ms (south america) and this past week I’m at 500+
1 Like
To add to the comments on this thread, for the last two weeks I’m having HUGE latency issues, mostly on dungeons and instances.
It is ALWAYS world latency (home latency is fine as usual), and I’m getting really frustrated. I play other online games and I’m not having any latency issues. There must be something wrong on the server side.
Also seeing this same problem. I typically get between 15-20ms out in the world on both home and world. But as soon as myself and others step into our Mythic Ny’alotha raid my world ms climbs to 250+ms while the home stays at 20ms.
Here is the first test to US West:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| testwifi.here - 0 | 137 | 137 | 0 | 0 | 1 | 0 |
| 96.120.48.233 - 0 | 137 | 137 | 6 | 9 | 16 | 16 |
| 68.85.201.45 - 0 | 137 | 137 | 6 | 9 | 17 | 11 |
|be-11-ar01.roseville.mn.minn.comcast.net - 0 | 137 | 137 | 7 | 10 | 17 | 9 |
|be-13367-cr02.350ecermak.il.ibone.comcast.net - 0 | 137 | 137 | 17 | 20 | 27 | 17 |
|be-1302-cs03.350ecermak.il.ibone.comcast.net - 0 | 137 | 137 | 17 | 20 | 28 | 17 |
|be-2304-pe04.350ecermak.il.ibone.comcast.net - 0 | 137 | 137 | 16 | 19 | 25 | 20 |
| 173.167.58.14 - 0 | 137 | 137 | 16 | 22 | 88 | 19 |
| ae1-br01-eqch2.as57976.net - 0 | 136 | 136 | 57 | 111 | 1097 | 58 |
| 137.221.65.132 - 0 | 136 | 136 | 57 | 69 | 398 | 63 |
| et-0-0-0-pe02-swlv10.as57976.net - 0 | 137 | 137 | 57 | 62 | 170 | 60 |
| las-swlv10-ia-bons-02.as57976.net - 0 | 137 | 137 | 57 | 60 | 73 | 58 |
| 137.221.105.2 - 0 | 136 | 136 | 57 | 60 | 67 | 58 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
And the second test to US Central:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| testwifi.here - 0 | 105 | 105 | 0 | 0 | 2 | 0 |
| 96.120.48.233 - 0 | 105 | 105 | 7 | 10 | 16 | 8 |
| 68.85.201.13 - 0 | 105 | 105 | 6 | 10 | 14 | 10 |
| po-2-rur02.nmpls.mn.minn.comcast.net - 0 | 105 | 105 | 7 | 10 | 15 | 8 |
|be-11-ar01.roseville.mn.minn.comcast.net - 0 | 105 | 105 | 7 | 10 | 17 | 11 |
|be-13367-cr02.350ecermak.il.ibone.comcast.net - 0 | 105 | 105 | 17 | 21 | 26 | 22 |
|be-1202-cs02.350ecermak.il.ibone.comcast.net - 0 | 105 | 105 | 17 | 20 | 25 | 24 |
|be-2201-pe01.350ecermak.il.ibone.comcast.net - 0 | 105 | 105 | 16 | 19 | 25 | 22 |
| 50.242.151.154 - 0 | 105 | 105 | 16 | 24 | 104 | 19 |
| ae1-br01-eqch2.as57976.net - 0 | 103 | 103 | 16 | 121 | 2144 | 18 |
| et-0-0-0-pe03-eqch2.as57976.net - 0 | 105 | 105 | 16 | 22 | 122 | 20 |
| 24.105.62.129 - 0 | 105 | 105 | 18 | 21 | 31 | 19 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
This seems directly caused by the ae1-br01-eqch2.as57976.net host. This is also directly wired into a switch which is wired into my router which is wired into my modem. This is the second day in a row we are facing this problem.
2nd Edit: looks like the above host is a known high-cause when testing as mentioned in previous forum posts. However there is an IP address: 137.221.65.132 listed that is also considerably high located in the Netherlands. I have no idea why my PC is routing through the Netherlands inside of the raid instance, but that makes no sense living in the midwest of the United States.
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.2.1
2 9 ms 12 ms 9 ms 142.254.155.165
3 172 ms 32 ms 22 ms ae63.brfdwifb01h.midwest.rr. com [24.164.239.189]
4 14 ms 23 ms 15 ms be42.milzwift01r.midwest.rr. com [65.31.113.80]
5 14 ms 16 ms 16 ms bu-ether18.chctilwc00w-bcr00.tbone.rr. com [66.109.6.206]
6 16 ms 23 ms 15 ms 66.109.5.136
7 14 ms 23 ms 13 ms 66.109.5.225
8 15 ms 14 ms 13 ms 66.109.9.149
9 1031 ms 440 ms 219 ms ae1-br01-eqch2.as57976. net [137.221.69.33]
10 77 ms 81 ms 75 ms 137.221.65.132
11 55 ms 55 ms 58 ms et-0-0-0-pe02-swlv10.as57976. net [137.221.83.83]
12 62 ms 66 ms 56 ms las-swlv10-ia-bons-02.as57976. net [137.221.66.19]
13 56 ms 65 ms 57 ms 137.221.105.2
Trace complete.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
| router.charter.n3t- 0 |
246 |
246 |
0 |
0 |
5 |
0 |
| 072-031-136-077.res.spectrum.c0m - 0 |
246 |
246 |
7 |
12 |
24 |
13 |
| 071-046-009-133.res.spectrum.c0m - 0 |
246 |
246 |
7 |
12 |
23 |
12 |
| bundle-ether34.orld71-car1.bhn.n3t - 0 |
246 |
246 |
9 |
14 |
29 |
15 |
| 072-031-188-170.res.spectrum.c0m - 0 |
246 |
246 |
9 |
14 |
30 |
11 |
| bu-ether44.tustca4200w-bcr00.tbone.rr.c0m - 0 |
246 |
246 |
9 |
18 |
36 |
11 |
| 66.109.5.131 - 0 |
246 |
246 |
16 |
24 |
54 |
22 |
| ae-15-312.pr0.dca10.tbone.rr.c0m - 0 |
246 |
246 |
15 |
24 |
146 |
21 |
| ae1-br01-eqmi2.as57976.n3t - 0 |
246 |
246 |
53 |
60 |
118 |
58 |
| xe-0-0-0-1-br01-eqat2.as57976.n3t - 0 |
246 |
246 |
51 |
57 |
99 |
57 |
| et-0-0-4-br02-eqch2.as57976.n3t - 0 |
246 |
246 |
51 |
59 |
119 |
57 |
| et-0-0-1-pe01-eqch2.as57976.n3t - 0 |
246 |
246 |
53 |
62 |
156 |
59 |
| 24.105.62.129 - 0 |
246 |
246 |
50 |
55 |
73 |
53 |
| ________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Edited net to n3t and com to c0m so it would post. This was during a raid, where EVERYONE was over 200ms when normally are 30-60ms.
Please fix it, we can’t raid!! In open world we have our normal ping but when we join to the raid it spike to 300-500ms and we CAN’T raid. Our vpns said that we are on Syndey Server (OCE) when we are in a instance. Please fix your route/servers.
As soon as we zone into raid we’re seeing connection switch from US IP to Singapore IP 103.4.115.233 and our latency shoots up.
1 Like
Please Fix This is Insane for a large Gaming Corp. Would expect this from a small indy company. Been an issue for multiple days.
I’m also connecting to Singapore when entering Ny’alotha.
So… can we at least get a “we’re looking into it” post or anything?
We zoned out for 30 mins, let the instance soft reset, zoned back in, and we are now on US Central data center connection as expected. No idea if that actually had any impact, or if whatever job runs to create these instances in the proper data center was fixed, or if we just got lucky, but posting on the odd chance it helps anyone else out.
1 Like
Seems almost like its allocating people to oceanic server instead of US one. Has happened to our raid 2 times now.
1 Like