08/28/2018 12:53 AMPosted by
Silenz
Any possible update on when they're gonna fix this? Is it only Oceanic realms? I can't imagine what servers like Kel'thuzad or Darkspear are like if little old Khaz'goroth is struggling this much. None of us are going to be able to raid if it's not fixed before next Tuesday. Imagine how badly the Uldir servers are going to be lagging on the first day..
It's Oceanic only, I doubt you will see a fix soon since it's most likely hardware related and I don't think you will see additional server resources allocated anytime soon as it's an expensive investment too make to fix a short term issue. This will probably get fixed with the Oceanic population goes down over the course of a few months like it always does. That would be a cheaper fix for them :)
08/28/2018 01:02 AMPosted by
Aussiè
It's Oceanic only, I doubt you will see a fix soon since it's most likely hardware related and I don't think you will see additional server resources allocated anytime soon as it's an expensive investment too make to fix a short term issue. This will probably get fixed with the Oceanic population goes down over the course of a few months like it always does. That would be a cheaper fix for them :)
Really doesn't seem like a short-term issue at this point. Expansion lag is of course expected but it's usually dropped off by the end of the 2nd week. Actual content is releasing soon and if Oceanic guilds aren't able to raid or people can't play Warfronts because the servers are garbage it seems logical to me that it's worth the investment.
Instances are fine, this is all world lag, and the latency shown is fine...
Tonight on Frostmourne in Stormsong Valley, the server side lag was really quite bad. Latency to the servers from Perth was only 48ms and that never spiked. My local link is definitely not congesting and my backhaul isn't either (I work for the ISP that provides my connection).
Win MTR - shows no network issues at all.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 784 | 784 | 0 | 0 | 5 | 0 |
| lo1.bras21.per4.on.ii.net - 0 | 784 | 784 | 1 | 1 | 17 | 1 |
| ae25.cr1.per4.on.ii.net - 0 | 784 | 784 | 1 | 2 | 48 | 21 |
| be170.cr2.adl6.on.ii.net - 0 | 784 | 784 | 48 | 48 | 68 | 48 |
| be40.cr2.syd7.on.ii.net - 1 | 780 | 779 | 48 | 48 | 65 | 48 |
| ae6.cr2.syd4.on.ii.net - 0 | 784 | 784 | 48 | 50 | 132 | 48 |
| 55497.syd.equinix.com - 0 | 784 | 784 | 48 | 48 | 65 | 48 |
| 103.4.115.248 - 0 | 784 | 784 | 48 | 48 | 67 | 48 |
|________________________________________________|______|______|______|______|______|______|
Traceroute is also fine, mirrors the latency shown in game.
Tracing route to 103.4.115.248 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 2 ms 2 ms lo1.bras21.per4.on.ii.net [150.101.42.165]
3 2 ms 2 ms 1 ms ae25.cr1.per4.on.ii.net [150.101.34.99]
4 49 ms 49 ms 48 ms be170.cr2.adl6.on.ii.net [150.101.33.20]
5 49 ms 48 ms 48 ms be40.cr2.syd7.on.ii.net [150.101.33.34]
6 49 ms 48 ms 48 ms ae6.cr2.syd4.on.ii.net [150.101.41.124]
7 48 ms 48 ms 48 ms 55497.syd.equinix.com [45.127.172.99]
8 57 ms 48 ms 48 ms 103.4.115.248
Trace complete.
And finally, pathping, showing nothing wrong at all.
Tracing route to 103.4.115.248 over a maximum of 30 hops
0 [192.168.1.47]
1 192.168.1.1
2 lo1.bras21.per4.on.ii.net [150.101.42.165]
3 ae25.cr1.per4.on.ii.net [150.101.34.99]
4 be170.cr2.adl6.on.ii.net [150.101.33.20]
5 be40.cr2.syd7.on.ii.net [150.101.33.34]
6 ae6.cr2.syd4.on.ii.net [150.101.41.124]
7 55497.syd.equinix.com [45.127.172.99]
8 103.4.115.248
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.1.47]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% lo1.bras21.per4.on.ii.net [150.101.42.165]
0/ 100 = 0% |
3 2ms 0/ 100 = 0% 0/ 100 = 0% ae25.cr1.per4.on.ii.net [150.101.34.99]
0/ 100 = 0% |
4 33ms 0/ 100 = 0% 0/ 100 = 0% be170.cr2.adl6.on.ii.net [150.101.33.20]
0/ 100 = 0% |
5 50ms 0/ 100 = 0% 0/ 100 = 0% be40.cr2.syd7.on.ii.net [150.101.33.34]
0/ 100 = 0% |
6 49ms 0/ 100 = 0% 0/ 100 = 0% ae6.cr2.syd4.on.ii.net [150.101.41.124]
0/ 100 = 0% |
7 48ms 0/ 100 = 0% 0/ 100 = 0% 55497.syd.equinix.com [45.127.172.99]
0/ 100 = 0% |
8 49ms 0/ 100 = 0% 0/ 100 = 0% 103.4.115.248
Trace complete.
These morons at Blizzard love to force CRZ / Sharding in current content, no wonder why the servers are having issues, cost cutting to the extreme. Screw this game and screw Blizzard I'm over it all.
Zuldazar 8:25pm Brisbane Australia
40ms World latency
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 1 | 555 | 554 | 0 | 9 | 186 | 1 |
| No response from host - 1 | 555 | 554 | 7 | 19 | 171 | 7 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| 198.142.250.177 - 1 | 551 | 549 | 25 | 39 | 240 | 28 |
| 198.142.139.112 - 1 | 547 | 544 | 24 | 40 | 238 | 28 |
| 203.208.192.133 - 1 | 551 | 549 | 179 | 199 | 388 | 189 |
| 203.208.173.138 - 1 | 551 | 549 | 180 | 196 | 374 | 183 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| ae-1-6.bar2.SanFrancisco1.Level3.net - 1 | 555 | 554 | 185 | 201 | 380 | 186 |
|BLIZZARD-EN.bar2.SanFrancisco1.Level3.net - 1 | 551 | 549 | 186 | 203 | 380 | 189 |
| ae1-br01-eqsv5.as57976.net - 1 | 551 | 549 | 184 | 201 | 365 | 189 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 2 | 515 | 506 | 188 | 231 | 3375 | 192 |
| et-0-0-29-br01-eqla1.as57976.net - 1 | 543 | 539 | 188 | 217 | 787 | 189 |
| et-0-0-2-br01-swlv10.as57976.net - 1 | 551 | 549 | 188 | 207 | 376 | 196 |
| et-0-0-31-pe02-swlv10.as57976.net - 1 | 547 | 544 | 188 | 204 | 392 | 189 |
| las-swlv10-ia-bons-04.as57976.net - 1 | 555 | 554 | 188 | 203 | 390 | 191 |
| 137.221.105.2 - 1 | 551 | 549 | 188 | 203 | 324 | 188 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
These morons at Blizzard love to force CRZ / Sharding in current content, no wonder why the servers are having issues, cost cutting to the extreme. Screw this game and screw Blizzard I'm over it all.
\
seriously you think this adds anything to the current situation...
feel free to unsub with that winning attitude
Lag was so bad tonight I just stopped playing. I mean, I wasn't really playing anyhow.
But it's been two weeks now, Bliz. Really. This is pretty unacceptable.
Lag heavy again tonight. Vol'dun foothold for alliance, Caelestrasz in last 10 mins ie 1925-1935 AWST. [Ed. Latency 179ms Home, 191ms World. (usually around 67ms)
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| BoB2.iiNet - 0 | 577 | 577 | 0 | 0 | 5 | 1 |
| lo0.bras1.per1.on.ii.net - 0 | 577 | 577 | 18 | 20 | 72 | 18 |
| ae21.cr1.per4.on.ii.net - 0 | 577 | 577 | 18 | 22 | 428 | 19 |
| be170.cr2.adl6.on.ii.net - 6 | 474 | 448 | 110 | 128 | 415 | 135 |
| be40.cr2.syd7.on.ii.net - 8 | 450 | 417 | 0 | 129 | 412 | 135 |
| ae6.cr2.syd4.on.ii.net - 6 | 470 | 443 | 107 | 131 | 408 | 129 |
| 55497.syd.equinix.com - 5 | 486 | 463 | 108 | 128 | 420 | 135 |
| 103.4.115.248 - 7 | 466 | 438 | 108 | 128 | 413 | 135 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I've pretty well stopped reporting on it, it doesnt seem to make any difference, it continues on as it has for two weeks. If they can't figure out/fix what is wrong in 2 weeks I really don't know what to say.
They definitely know the cause by now.
They are just not acting on it, they will just wait and let oceanic numbers go down naturally. Rather than investing in hardware from this decade.
Oceanic servers are tiny in comparison to the big NA ones. Even frostmourne which is our biggest is 12th overall in terms of population in NA.
We are using older poorer hardware that cant even cope with a launch population a fraction of what NA gets.
More server lag tonight and Im not posting any more winmters. Thats eleven days of reports and we are nowhere.
I appreciate what the Blues have done but Im sorry, enough. Ive heard complaints ingame for days on end, the same questions being asked.
Whats the matter and when does it get fixed?
Tonight I was crafting some inks, easy, right? Craft bar...pause...craft bar..pause...I did about 130 inks and it took me close to 20 minutes to do.
Cast lag, server lag, vendor lag....we didnt have this issue in Legion and I dont know why we are having it now. This plus the depressing fact all we ever see is NIGHT TIME in game, which still hasnt been answered in close to two years..and what Oceanic players are being given is an utterly substandard gaming experience.
It is not my ping. It is not my internet. It is not my isp. It is BFA outer areas and this started in BFA.
Let's see if this week's restarts make any difference. Tonight was a bit hit and miss for me, in some zones it was terrible and then in others there was very little noticeable delay. Overall the experience is still absolute garbage - last night I came very close to putting a fist through my monitor. Coming home from a long, crappy day at work, wanting to just relax a bit on WoW only to be instantly confronted by this aggravating lag.
It's usually better after restart, because a lot of people log off for the night.
We all then think it's fixed until the same problems arise again the next day.
Smells very much like the hardware isn't sufficient to maintain the populace right now.
Nope no change...starting to get a little bit frustrated ..there was a patch...but it hasnt seemed to have helped anything
30ms world latency
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 75 | 75 | 0 | 1 | 8 | 1 |
| No response from host - 0 | 75 | 75 | 8 | 11 | 27 | 10 |
| No response from host - 100 | 15 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 15 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 15 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 15 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 15 | 0 | 0 | 0 | 0 | 0 |
| 198.142.250.177 - 0 | 75 | 75 | 25 | 30 | 50 | 29 |
| 198.142.139.112 - 0 | 75 | 75 | 25 | 31 | 48 | 28 |
| 203.208.192.133 - 0 | 75 | 75 | 180 | 188 | 226 | 187 |
| 203.208.173.138 - 0 | 75 | 75 | 181 | 187 | 228 | 184 |
| No response from host - 100 | 15 | 0 | 0 | 0 | 0 | 0 |
| ae-1-6.bar2.SanFrancisco1.Level3.net - 2 | 71 | 70 | 184 | 189 | 210 | 188 |
|BLIZZARD-EN.bar2.SanFrancisco1.Level3.net - 2 | 71 | 70 | 186 | 191 | 215 | 187 |
| ae1-br01-eqsv5.as57976.net - 0 | 75 | 75 | 185 | 191 | 238 | 189 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 0 | 75 | 75 | 188 | 196 | 300 | 192 |
| et-0-0-29-br01-eqla1.as57976.net - 0 | 75 | 75 | 189 | 196 | 232 | 192 |
| et-0-0-2-br01-swlv10.as57976.net - 0 | 75 | 75 | 189 | 195 | 227 | 190 |
| et-0-0-31-pe02-swlv10.as57976.net - 0 | 75 | 75 | 188 | 194 | 227 | 190 |
| las-swlv10-ia-bons-04.as57976.net - 0 | 75 | 75 | 188 | 193 | 236 | 193 |
| 137.221.105.2 - 0 | 75 | 75 | 188 | 193 | 228 | 191 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Reset is over and still a complete mess.
30 ms lag in boralus main city
10:40pm
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 473 | 473 | 0 | 2 | 131 | 1 |
| No response from host - 0 | 473 | 473 | 7 | 12 | 134 | 7 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
| 198.142.250.177 - 0 | 473 | 473 | 24 | 31 | 211 | 44 |
| 198.142.139.112 - 0 | 473 | 473 | 25 | 31 | 226 | 29 |
| 203.208.192.133 - 0 | 473 | 473 | 180 | 190 | 389 | 183 |
| 203.208.173.138 - 0 | 473 | 473 | 180 | 187 | 399 | 180 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
| ae-1-6.bar2.SanFrancisco1.Level3.net - 1 | 469 | 468 | 184 | 190 | 287 | 191 |
|BLIZZARD-EN.bar2.SanFrancisco1.Level3.net - 1 | 469 | 468 | 185 | 192 | 425 | 188 |
| ae1-br01-eqsv5.as57976.net - 0 | 473 | 473 | 184 | 192 | 390 | 208 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 2 | 432 | 425 | 188 | 243 | 4972 | 192 |
| et-0-0-29-br01-eqla1.as57976.net - 0 | 473 | 473 | 188 | 209 | 646 | 333 |
| et-0-0-2-br01-swlv10.as57976.net - 0 | 473 | 473 | 188 | 196 | 384 | 193 |
| et-0-0-31-pe02-swlv10.as57976.net - 0 | 473 | 473 | 188 | 194 | 381 | 191 |
| las-swlv10-ia-bons-04.as57976.net - 0 | 473 | 473 | 188 | 195 | 402 | 191 |
| 137.221.105.2 - 0 | 473 | 473 | 188 | 195 | 394 | 190 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
TRACERT
Tracing route to 103.4.115.248 over a maximum of 30 hops
1 9 ms 1 ms <1 ms 192.168.0.1
2 11 ms 16 ms 10 ms MSI [0.0.0.0]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 27 ms 27 ms 27 ms 124.19.61.3
8 25 ms 25 ms 26 ms 220.101.73.6
9 29 ms 30 ms 31 ms xe-1-0-1.gw102.sy3.ap.equinix.com [27.111.240.147]
10 27 ms 27 ms 37 ms 27.111.251.114
11 28 ms 25 ms 25 ms 103.4.115.248
Trace complete.
PATH PING
Tracing route to 103.4.115.248 over a maximum of 30 hops
0 MSI [192.168.0.22]
1 192.168.0.1
2 MSI [0.0.0.0]
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 MSI [192.168.0.22]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
100/ 100 =100% |
2 --- 100/ 100 =100% 0/ 100 = 0% MSI [0.0.0.0]
Trace complete.
Somewhat unsurprisingly, the restarts have done nothing to fix this issue. The game is completely, and utterly unplayable. I am trying to level my Mage alt at the moment and the Fire rotation is impossible to play in these conditions. By the time my "Heating Up" proc applies from my most recent Critical effect, I have already finished casting my next Fireball, which then inevitably does not crit, so all I see is the buff and UI effect lighting up for a split second before being cancelled.
This is getting beyond pathetic, how many more Pathpings, Traceroutes and WinMTRs do we need to send you before we even get an update on the situation? And don't start again with "the amount of data sent only reflects 0.01% of the player base, bla bla bla..." That's not good enough! What do you expect? Thousands of replies?
Blizzard have said themselves multiple times that active forum users only make up a small fraction of the playerbase. You will NEVER get as many reports as you seem to expect for this issue because there simply are not enough players that use these forums.
The data that has been supplied is all from players who are collecting this data while the issue is actively affecting them. Anyone who knows how to read this data should know immediately whether the problem lies on the player's end, the ISPs end or with Blizzard. Why have we not been informed of which of these it is?
All of my traceroutes and WinMTRs have shown an average latency of 10-30ms. To me that says that there is no problem between me and the server.
08/28/2018 05:01 AMPosted by
Rixven
They definitely know the cause by now.
They are just not acting on it, they will just wait and let oceanic numbers go down naturally. Rather than investing in hardware from this decade.
Oceanic servers are tiny in comparison to the big NA ones. Even frostmourne which is our biggest is 12th overall in terms of population in NA.
We are using older poorer hardware that cant even cope with a launch population a fraction of what NA gets.
Older hardware isn't a thing really any more. Blizzard more than likely runs the servers as VMs, on leased hardware that is almost certainly not outdated. These would grow and shrink as necessary to meet pop demands, so I doubt very much that this is to do with server population.
Likely it is some new process running since BfA launched, that is causing the server load.
Servers are enormously complex and I promise you that they have a lot of system engineers trying to figure out exactly what the issue is. I do not envy the poor sods who have to go through the logs looking for the issue.
Shutdown did nothing, was back to laggy piece of crap the second the servers came back up... here's hoping for next shutdown something changes.