went into a key and all of us had to re-login because we were lagging so badly.(before tuesday reset) and it’s still happening even in low level dungeons. big oof.
Hey there!
Thank you all for your reports. I noticed that everyone posting in this thread is connecting from Canada across a few different ISPs. We’ve received reports impacting Shaw Communications and Rogers Cable specifically, but given your reports the issue may be isolated to a peering partner of which all of your ISP’s share. To further investigate this, let’s go ahead and grab a winMTR. Here are the instructions:
- Download the tool from this page
- Enter the game IP into the “host” field. The IP address for our games are listed on the winMTR instructions page
- Start the test and play the affected game for at least 15 minutes. Ensure the problem happens (so in this case, high latency) while the winMTR tool is running.
- After recording the problem data, click “export text” and save the winMTR file in an easy to find location.
- Once you have that made, open the file. You’ll need to copy and paste the contents of the Text document into the post, and put four Tilde (~) marks above the winMTR. It’ll look like this:
WinMTR goes here
If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).
its also telus, cause i was getting similar, but sometimes even higher than 600MS, it be over 1000 sometimes, but its mainly only on east/cst servers, cause if check a west coast server and id be 30, while on cst/est server my latency be threw the roof
I’ve got bell. X.x
I usually get around 57 home, 57 world , since playing from west coast …now its sitting in the 70s , than would sky rocket to high 500-1000 etc , heres my pastebin of a winMTR
-pastebin.com/7SfekcK9
Hey there Gruumsh, thanks for linking that WinMTR test! Were you experiencing the latency issues in-game while this test was running? If not, please run a new WinMTR using these instructions.
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.0.1
2 9 ms 7 ms 7 ms 184.64.0.1
3 9 ms 10 ms 9 ms rc3so-be124-1.cg.shawcable .net [64.59.134.201]
4 30 ms 30 ms 30 ms rc1wt-be82.wa.shawcable .net [66.163.76.9]
5 28 ms 28 ms 27 ms rc6wt-tge0-10-0-10.wa.shawcable .net [66.163.68.66]
6 3442 ms 219 ms 159 ms ae1-br01-eqse2.as57976 .net [137.221.73.33]
7 71 ms 60 ms 59 ms xe-0-0-0-1-br01-eqsv5.as57976 .net [137.221.65.40]
8 60 ms 62 ms 102 ms et-0-0-29-br02-eqsv5.as57976 .net [137.221.65.117]
9 60 ms 60 ms 60 ms xe-0-0-1-1-br02-eqla1.as57976 .net [137.221.65.6]
10 60 ms 59 ms 60 ms et-0-0-29-br01-eqla1.as57976 .net [137.221.65.0]
11 57 ms 57 ms 57 ms et-0-0-2-br01-swlv10.as57976 .net [137.221.65.69]
12 69 ms 61 ms 60 ms et-0-0-0-pe01-swlv10.as57976 .net [137.221.83.81]
13 61 ms 60 ms 60 ms 137.221.105.2
Trace complete.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| homeportal - 0 | 1329 | 1329 | 0 | 0 | 10 | 1 |
| bas2-barrie18_lo0_symp.net.bell.ca - 0 | 1329 | 1329 | 11 | 15 | 385 | 12 |
| core2-barrie18_pos3-1.net.bell.ca - 0 | 1329 | 1329 | 9 | 13 | 129 | 10 |
|tcore3-barrie18_bundle-ether2.net.bell.ca - 0 | 1328 | 1328 | 23 | 28 | 137 | 26 |
| tcore4-toronto63_hu1-13-0-0.net.bell.ca - 0 | 1328 | 1328 | 23 | 28 | 138 | 28 |
|tcore4-chicagocp_hundredgige0-5-0-0.net.bell.ca - 0 | 1328 | 1328 | 23 | 30 | 135 | 28 |
| bx6-chicagodt_0-7-0-0.net.bell.ca - 0 | 1328 | 1328 | 23 | 27 | 134 | 25 |
| No response from host - 100 | 267 | 0 | 0 | 0 | 0 | 0 |
| ae1-br02-eqch2.as57976.net - 0 | 1329 | 1329 | 21 | 29 | 145 | 24 |
| be2-pe2-eqch2.as57976.net - 0 | 1328 | 1328 | 21 | 24 | 132 | 22 |
| chi-eqch2-ia-bons-04.as57976.net - 0 | 1328 | 1328 | 21 | 25 | 125 | 26 |
| 24.105.62.129 - 0 | 1328 | 1328 | 23 | 27 | 131 | 26 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
With me having 70ish latency YES , but this morning around 3amish+ it was spiking up and down from 70ish to over 1000+ , but ran the test when i was ingame and its atm sitting at 70ish, which it should be around 56-58 home/world …so its 20 or so more than normal, but it seems to hit me the highest from 1am+
Gruumsh,
There’s nothing in this test that indicates where the issue would be, oddly enough. That test indicates that your latency should be way lower than it is. Can we run a looking glass with all three options checked instead? If you post that we can check the path back.
From Canada, on Telus, disconnecting every 3-4 minutes. Started today, but I didn’t log in yesterday so might be earlier. Please fix this asap.
TRACEROUTE:
traceroute to 24.71.118.185 (24.71.118.185), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.705 ms 1.684 ms 1.686 ms
2 24.105.18.3 (24.105.18.3) 2.722 ms 2.745 ms 2.743 ms
3 137.221.105.12 (137.221.105.12) 2.164 ms 2.174 ms 2.177 ms
4 137.221.66.16 (137.221.66.16) 1.949 ms 1.986 ms 1.985 ms
5 137.221.83.80 (137.221.83.80) 14.227 ms 14.469 ms 14.477 ms
6 137.221.65.68 (137.221.65.68) 14.021 ms 12.962 ms 12.943 ms
7 137.221.65.1 (137.221.65.1) 13.099 ms 13.085 ms 13.082 ms
8 137.221.65.7 (137.221.65.7) 13.078 ms 13.075 ms 13.071 ms
9 137.221.70.34 (137.221.70.34) 13.067 ms 13.315 ms 13.298 ms
10 rt0sj-equinix.cl.shawcable .net (206.223.116.20) 12.891 ms 16.646 ms 15.991 ms
11 dx9ht-la1-s1.ok.int.shawcable .net (64.59.170.102) 47.433 ms 47.126 ms 47.272 ms
12 S0106105611bde05b.ok.shawcable .net (24.71.118.185) 61.449 ms 66.357 ms 66.347 ms
07/03/2020 17:22:17 UTC
PING:
PING 24.71.118.185 (24.71.118.185) 56(84) bytes of data.
— 24.71.118.185 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms
07/03/2020 17:22:17 UTC
MTR:
Start: Sat Mar 7 17:22:17 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.6 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.12 0.0% 10 0.9 1.9 0.6 7.9 2.4
4.|-- 137.221.66.16 0.0% 10 0.4 0.5 0.3 0.7 0.0
5.|-- 137.221.83.80 0.0% 10 13.0 14.0 12.7 24.7 3.7
6.|-- 137.221.65.68 0.0% 10 12.9 13.6 12.6 19.0 1.8
7.|-- 137.221.65.1 0.0% 10 13.0 19.0 12.7 44.7 12.9
8.|-- 137.221.65.7 0.0% 10 12.8 15.5 12.8 36.6 7.4
9.|-- 137.221.70.34 0.0% 10 13.0 15.3 13.0 35.6 7.1
10.|-- rt0sj-equinix.cl.shawcable .net 0.0% 10 13.0 14.5 12.8 16.7 1.2
11.|-- dx9ht-la1-s1.ok.int.shawcable .net 0.0% 10 47.4 47.3 47.2 47.5 0.0
12.|-- S0106105611bde05b.ok.shawcable .net 0.0% 10 62.1 65.1 62.1 70.3 2.8
07/03/2020 17:22:17 UTC
Same here, past 3 days now, I usually hover around 15-30, now it’s 600-700, absolutely horrible!!
Like most mine can easily handle settings maxed out, I am now at level 4 and still getting hard lag - I am with Teksavvy and have been since 2012. No issues with this kind of latency until 3 days ago.
Not exactly sure what happened, but yesterday, the 11th of March, latency was back to normal, and again, I changed nothing so it was clearly at Blizzard’s end. Just happy it’s back to normal.
It seems like reports may have slowed down a bit in the last few days on this. We’re keeping an eye on it. Anybody still having problems (for folks who started getting issues in March?)