[SaskTel] Latency spiking constantly during gameplay

I have had, since yesterday, an issue causing constant latency spikes followed by game catchup making the game completely unplayable. I don’t seem to have internet issues outside of blizzard games.

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 358 | 358 | 0 | 0 | 2 | 0 |

| 10.233.8.4 - 0 | 358 | 358 | 13 | 36 | 110 | 22 |

| 10.233.9.2 - 0 | 358 | 358 | 13 | 36 | 116 | 35 |

| 10.233.9.30 - 0 | 358 | 358 | 13 | 38 | 126 | 33 |

| 142.165.12.233 - 0 | 358 | 358 | 16 | 41 | 139 | 42 |

| 142.165.120.21 - 0 | 358 | 358 | 37 | 63 | 148 | 64 |

| 142.165.60.186 - 0 | 358 | 358 | 47 | 69 | 139 | 63 |

| 142.165.0.122 - 0 | 358 | 358 | 34 | 57 | 127 | 52 |

| six .blizzardonline.net - 0 | 358 | 358 | 39 | 70 | 185 | 51 |

| ae1 -br02-eqse2.as57976.net - 0 | 358 | 358 | 37 | 68 | 164 | 62 |

| xe -0-0-1-1-br02-eqch2.as57976.net - 13 | 239 | 209 | 105 | 131 | 278 | 114 |

| be2 -pe01-eqch2.as57976.net - 13 | 239 | 209 | 106 | 130 | 276 | 117 |

| 24.105.62.129 - 14 | 231 | 199 | 103 | 127 | 193 | 114 |

|________________________________________________|______|______|______|______|______|______|

yup same probs here just with my server though other servers ptr and games are fine

I’ve been experiencing this on Wyrmrest for the past few weeks. Granted it is just an alt server for me I’d still like to play uninterrupted when I’m playing an alt. :confused:

I am on the SaskTel ISP in Canada, not sure if it’s a shared issue across other users of that ISP, i know there was a short-duration issue a year or so back with the iSP and blizzard servers.

Yeah i’m on SaskTel ISP as well

Hey y’all,

We have received similar reports from other players on SaskTel and related ISPs like Telus, Access Communications, Bell Aliant, Eastlink, Xplornet and Northwestel. We are currently investigating to find the root cause but using a VPN or alternate network like a hotspot seems to work.

In the mean time, please continue to provide WinMTR tests so we can get our NOC team data to send to the ISPs.

Thank you for your response, hopefully the issue is resolved by SaskTel before 8.2 release :slight_smile:

I did a WinMTR test for both USWest and USCentral servers.

CENTRAL:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 375 | 375 | 0 | 0 | 2 | 0 |

| 10.233.8.4 - 0 | 375 | 375 | 14 | 39 | 129 | 14 |

| 10.233.9.2 - 0 | 375 | 375 | 12 | 42 | 137 | 32 |

| 10.233.9.30 - 0 | 375 | 375 | 12 | 44 | 145 | 33 |

| 142.165.12.233 - 0 | 375 | 375 | 12 | 46 | 153 | 44 |

| 142.165.120.42 - 0 | 375 | 375 | 42 | 69 | 143 | 60 |

| 142.165.120.25 - 0 | 375 | 375 | 42 | 71 | 135 | 55 |

| 142.165.0.122 - 0 | 375 | 375 | 35 | 63 | 137 | 51 |

| six.blizzardonline,net - 0 | 375 | 375 | 44 | 69 | 166 | 52 |

| ae1-br02-eqse2.as57976,net - 0 | 375 | 375 | 44 | 70 | 155 | 55 |

| xe-0-0-1-1-br02-eqch2.as57976,net - 13 | 254 | 223 | 103 | 138 | 464 | 131 |

| be2-pe01-eqch2.as57976,net - 20 | 211 | 169 | 107 | 131 | 345 | 119 |

| 24.105.62.129 - 18 | 222 | 183 | 106 | 131 | 346 | 130 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

WEST:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 359 | 359 | 0 | 0 | 1 | 0 |

| 10.233.8.4 - 0 | 359 | 359 | 15 | 33 | 94 | 36 |

| 10.233.9.2 - 0 | 359 | 359 | 12 | 39 | 108 | 32 |

| 10.233.9.22 - 0 | 359 | 359 | 12 | 41 | 109 | 42 |

| 142.165.12.233 - 0 | 359 | 359 | 15 | 42 | 115 | 42 |

| 142.165.120.42 - 0 | 359 | 359 | 40 | 62 | 125 | 63 |

| 142.165.120.25 - 0 | 359 | 359 | 42 | 68 | 137 | 58 |

| 142.165.0.122 - 0 | 359 | 359 | 43 | 64 | 125 | 51 |

| six.blizzardonline,net - 0 | 359 | 359 | 45 | 72 | 172 | 57 |

| ae1-br01-eqse2.as57976,net - 0 | 359 | 359 | 74 | 101 | 185 | 94 |

| xe-0-0-0-1-br01-eqsv5.as57976,net - 0 | 359 | 359 | 75 | 104 | 197 | 131 |

| et-0-0-29-br02-eqsv5.as57976,net - 0 | 359 | 359 | 75 | 103 | 172 | 104 |

| xe-0-0-1-1-br02-eqla1.as57976,net - 0 | 359 | 359 | 74 | 96 | 185 | 114 |

| et-0-0-29-br01-eqla1.as57976,net - 0 | 359 | 359 | 76 | 100 | 198 | 88 |

| et-0-0-2-br01-swlv10.as57976,net - 0 | 359 | 359 | 75 | 103 | 281 | 101 |

| et-0-0-31-pe02-swlv10.as57976,net - 0 | 359 | 359 | 74 | 97 | 161 | 85 |

| 137.221.105.2 - 0 | 359 | 359 | 72 | 90 | 149 | 84 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

So as of yesterday the latency as been spiking from 200-5000, and its been perfectly fine pretty much the last couple years up until this point so now the game is pretty unplayable on it, and I went and made a different char on a diff server cluster and it everything was working normal on it.

Same problem here, Kel’Thuzad server. Only started these last few days.

same problem. Here’s the test I ran today
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 172.16.1.254 - 0 | 247 | 247 | 0 | 0 | 3 | 0 |

| No response from host - 100 | 50 | 0 | 0 | 0 | 0 | 0 |

|207-47-195-169.ngai.static.sasknet.sk. ca - 0 | 247 | 247 | 1 | 5 | 15 | 2 |

| 142.165.0.118 - 0 | 247 | 247 | 20 | 22 | 30 | 21 |

| six.blizzardonline. net - 0 | 247 | 247 | 24 | 29 | 99 | 50 |

| ae1-br02-eqse2.as57976. net - 0 | 247 | 247 | 24 | 30 | 105 | 29 |

| xe-0-0-1-1-br02-eqch2.as57976. net - 12 | 172 | 153 | 0 | 99 | 183 | 94 |

| be2-pe01-eqch2.as57976. net - 17 | 148 | 123 | 92 | 93 | 96 | 95 |

| 24.105.62.129 - 14 | 160 | 138 | 0 | 93 | 98 | 94 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

No word on update yet.

Headline: Fibre Fault - Between Chicago, IL and Valparaiso, IN Services Affected: Fibre Region: Between Chicago, IL and Valparaiso, IN

Start: 2019¬/06¬/22 19:32:00

Incident #: INS000000XXXX

Update #11 @ 2019/06/23 16:19:25 Excavation continues to locate the damaged cable. No new updates are available at this time. The Rogers EBNOC remains in constant contact with the local US telco to ensure expedited resolution.

Technician ETA: On site

Estimated Time To Restore: Not available

Next update: 6:00 PM EDT or sooner should a major change in status occur.