In the greater Seattle area and having the same Wave issue. Any updates Blizzard?
I’m in the same area, same issue. Only when I’m in AV for classic wow.
Using a VPN solves the issue as I cannot even move when I log in without one. This is not a Blizzard or Wave issue it is the backbones in between which without enough evidence will not take action to correct the issue.
Please post your WinMTR so Blizzard can collect the evidence needed to get the ball rolling.
In Oregon on with a ISP named Helio Broadband. Seems to occur non-stop and I noticed the start of the issue on Monday (1/13). Please note for whatever reason I had to add spaces to the domain names below as the forums wouldn’t let me post otherwise.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| testwifi.here - 0 | 367 | 367 | 0 | 0 | 0 | 0 |
| gw-24.heliobroadband. com - 0 | 367 | 367 | 0 | 0 | 1 | 0 |
| 76.191.95.101 - 0 | 367 | 367 | 0 | 1 | 24 | 1 |
| be2.cr2-sea-a.bb.as11404. net - 0 | 367 | 367 | 5 | 5 | 5 | 5 |
| be1.cr2-sea-b.bb.as11404. net - 0 | 367 | 367 | 5 | 5 | 6 | 5 |
| six.blizzardonline .net - 0 | 366 | 366 | 5 | 9 | 79 | 5 |
| ae1-br02-eqse2.as57976. net - 11 | 255 | 227 | 50 | 51 | 107 | 50 |
| xe-0-0-1-1-br02-eqch2.as57976. net - 11 | 257 | 229 | 50 | 53 | 108 | 50 |
| be2-pe1-eqch2.as57976. net - 10 | 267 | 242 | 50 | 50 | 52 | 50 |
| chi-eqch2-ia-bons-02.as57976. net - 7 | 287 | 267 | 51 | 52 | 53 | 52 |
| 24.105.62.129 - 7 | 295 | 277 | 51 | 51 | 52 | 51 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Just put a - sign behind the links like soo www.link.com-
1 Like
I bought a one month sub & downloaded ExpressVPN (I saw some other folks had done the same thing). After I installed it and turned it on it began working fine. Consistent 70 ping or so.
Exact same issue. Wave Broadband from Seattle. Had to jump into a VPN as well to raid last night. Still having the same problem today.
Yeah I started having this issue the night before patch 8.3 hit but since it came out, constant lag, freezing, disconnecting, making the game completely unplayable. I even tried to switch the DirectX thing to the 12, 11 and 11 Legacy and didn’t change anything on my end to make the game playable so I’m pretty much stuck in freezing lag limbo.
Went into a corruption event after the cloak and just froze and died instantly pretty much without getting anything done but then was stuck in the corruption for a couple hours.
It started acting up the night of the 13th before patch day and been practically unplayable/unenjoyable the 14th and today (15th) Trying a lot of things to fix the issue but apparently none of it is working.
To everyone having this problem im having great success with [Private Internet Access] vpn im able to play again with 50-60ms.
Hi there friends,
Thanks for continuing to report on this. We know that high latency in game is quite impacting. Please keep the WinMTR reports up. These hlp us gather reports, data, and help show impact.
We hope to have good news soon!
/Nathardrick
1 Like
I’m on wave also in Wa. Here are my WinMTR results:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - loss % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.40.254 - 0 | 225 | 225 | 0 | 0 | 1 | 1 |
| knotso-fw.knotso net - 0 | 225 | 225 | 0 | 0 | 0 | 0 |
| 24-113-42-1.wavecable com - 0 | 225 | 225 | 11 | 23 | 96 | 19 |
| agg1-pohe-a-be150.bb.as11404 net - 0 | 225 | 225 | 11 | 19 | 64 | 13 |
| be2.cr2-tuk2.bb.as11404 net - 0 | 225 | 225 | 13 | 22 | 71 | 21 |
| be3.cr2-sea-b.bb.as11404 net - 0 | 225 | 225 | 15 | 24 | 66 | 22 |
| six.blizzardonline net - 0 | 225 | 225 | 14 | 28 | 127 | 35 |
| ae1-br02-eqse2.as57976 net - 10 | 161 | 145 | 59 | 69 | 148 | 71 |
| xe-0-0-1-1-br02-eqch2.as57976 net - 15 | 145 | 124 | 59 | 79 | 380 | 68 |
| be2-pe1-eqch2.as57976 net - 12 | 153 | 135 | 60 | 67 | 98 | 66 |
| 24.105.62.129 - 11 | 157 | 140 | 54 | 66 | 141 | 62 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
If six dot blizzardonline dot net is owned by blizzard then it’s not an ISP issue. It’s a bliz issue. All the lost packets are after that ip.
1 Like
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|----------------------------------------------|------|------|------|------|------|------|
| Linksys08251 - 0 | 336 | 336 | 0 | 0 | 2 | 0 |
| 216-235-96-HCC-48.hcc. net - 0 | 336 | 336 | 1 | 1 | 5 | 1 |
| 216-235-124-HCC-214.hcc. net - 0 | 336 | 336 | 1 | 1 | 3 | 1 |
| 216-235-124-hcc-242.hcc. net - 0 | 336 | 336 | 1 | 1 | 4 | 2 |
| 152.44.129.69 - 0 | 336 | 336 | 4 | 4 | 6 | 4 |
| be3.cr2-sea-b.bb.as11404. net - 0 | 336 | 336 | 4 | 4 | 6 | 4 |
| six.blizzardonline. net - 0 | 336 | 336 | 4 | 12 | 79 | 10 |
| ae1-br02-eqse2.as57976. net - 8 | 261 | 242 | 49 | 50 | 116 | 50 |
| xe-0-0-1-1-br02-eqch2.as57976. net - 10 | 246 | 223 | 49 | 53 | 116 | 49 |
| be2-pe1-eqch2.as57976. net - 4 | 293 | 282 | 49 | 49 | 54 | 50 |
| 24.105.62.129 - 4 | 293 | 282 | 50 | 50 | 57 | 51 |
I’m also located in Washington with the same issues. Happens on Classic and Retail alike. Western Servers or Oceanic are completely fine until matched w/ other people for a dungeon or bg, than the ms spikes.
1 Like
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.1.1 - 1 | 1145 | 1138 | 0 | 0 | 5 | 0 |
| 24-113-192-1.wavecable-com - 0 | 1171 | 1171 | 5 | 18 | 97 | 17 |
| agg1-pohe-a-be154.bb.as11404-net - 0 | 1171 | 1171 | 6 | 16 | 46 | 19 |
| be2.cr2-tuk2.bb.as11404-net - 0 | 1171 | 1171 | 8 | 19 | 42 | 17 |
| be3.cr2-sea-b.bb.as11404-net - 0 | 1171 | 1171 | 8 | 18 | 51 | 17 |
| six.blizzardonline-net - 0 | 1171 | 1171 | 8 | 23 | 91 | 21 |
| ae1-br02-eqse2.as57976-net - 10 | 869 | 790 | 0 | 65 | 158 | 71 |
| xe-0-0-1-1-br02-eqch2.as57976-net - 11 | 837 | 751 | 55 | 69 | 422 | 63 |
| be2-pe2-eqch2.as57976-net - 8 | 921 | 856 | 58 | 64 | 99 | 63 |
| 24.105.62.129 - 7 | 932 | 870 | 57 | 65 | 100 | 65 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
My WinMTR stats. My confusion is why all traffic is being routed through Blizzard ip addresses for the Netherlands and then back to New York. To be specific, ae1-br02, xe-0-0, and be2-pe2 all resolve to Blizzard Netherlands site IPs and they are the ones causing latency and loss.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| router.asus-com - 0 | 788 | 788 | 0 | 0 | 2 | 0 |
| 10.249.94.1 - 0 | 788 | 788 | 2 | 18 | 129 | 13 |
| 63.249.69.97 - 0 | 788 | 788 | 1 | 14 | 97 | 3 |
| No response from host - 100 | 158 | 0 | 0 | 0 | 0 | 0 |
| 63.249.69.73 - 0 | 788 | 788 | 1 | 12 | 95 | 1 |
| l3cruzio.10g.cruzio-com - 1 | 784 | 783 | 1 | 12 | 92 | 2 |
| te0-3-0-23.cr2-scl.bb.as11404-net - 0 | 788 | 788 | 2 | 13 | 92 | 6 |
| be2.cr1-scl.bb.as11404-net - 0 | 788 | 788 | 2 | 12 | 92 | 2 |
| be11.cr5-scl.bb.as11404-net - 0 | 788 | 788 | 2 | 15 | 131 | 6 |
| be13.cr3-55smarket.bb.as11404-net - 1 | 784 | 783 | 2 | 12 | 93 | 5 |
| be12.cr4-11greatoaks.bb.as11404-net - 0 | 788 | 788 | 2 | 15 | 134 | 8 |
| cr1-9greatoaks-be4.bb.as11404-net - 0 | 788 | 788 | 2 | 15 | 130 | 11 |
| eqix-ix-sv1.blizzard-com - 0 | 788 | 788 | 3 | 19 | 205 | 9 |
| ae1-br01-eqsv5.as57976-net - 13 | 533 | 469 | 56 | 69 | 179 | 56 |
| et-0-0-3-br01-eqch2.as57976-net - 9 | 585 | 535 | 56 | 97 | 3541 | 58 |
| be1-pe1-eqch2.as57976-net - 7 | 629 | 589 | 56 | 65 | 144 | 62 |
| 24.105.62.129 - 7 | 633 | 594 | 57 | 67 | 122 | 63 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
My world ms went as high as 60,000 playing on Sargeras from CA. My ISP is Cruzio. Playing on a mobile hotspot corrects the problem. Hoping to find something quicker though because tonight is our last chance at CE.
Edit: VPN also completely fixes the problem.
That would be correct as six.blizzardonline-net sends following three hops out of the country, to Holland.
Having the same issue started on Monday night, had to raid last night and was the worst experience I’ve had on wow yet.
Not sure what’s going on, going to call Wave today to see if they have an explanation.
I am in Washington with Wave as well having the same issue trying my vpn now.
I doubt Wave would know why blizzard is routing out of six.blizzardonline-net in Seattle, to the Netherlands and then back to New York.
Has anyone ran WinMTR after attaching to a vpn or mobile hotspot to see the change in routing?
Its not going to the Netherlands they just didn’t update the name and you would see a higher ping then 55 on the test. Trust me been through this before in November of last year.
Everyone please keep posting those WinMTR’s it helps to get this resolved quicker.