[Teksavvy ISP] High latency every night at the same time

Support Technical Support
17

Having the exact same issues.

For about 2-3 weeks, at peak times 8-9, completely unplayable. Happens during the raids mostly, and in PvP but not at the same extent. No issues basically before that. Same provider and I think the same area.

TRACEROUTE:
traceroute to 185.242.5.150 (185.242.5.150), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.860 ms 1.864 ms 1.867 ms
2 24.105.18.130 (24.105.18.130) 3.263 ms 3.286 ms 3.291 ms
3 137.221.105.14 (137.221.105.14) 3.293 ms 3.296 ms 3.298 ms
4 137.221.66.18 (137.221.66.18) 3.795 ms 3.808 ms 3.810 ms
5 137.221.83.82 (137.221.83.82) 275.639 ms 275.644 ms 275.647 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.004 ms 6.134 ms 6.126 ms
8 4-1-3.ear3.LosAngeles1.Level3.ne (4.71.135.105) 5.488 ms 5.607 ms 5.601 ms
9 ae-28.r00.lsanca07.us.bb.gin.ntt.ne (129.250.9.93) 6.060 ms 5.975 ms 6.095 ms
10 ae-2.r23.lsanca07.us.bb.gin.ntt.ne (129.250.3.237) 5.693 ms 5.805 ms 5.818 ms
11 ae-5.r01.lsanca20.us.bb.gin.ntt.ne (129.250.6.49) 6.506 ms 6.632 ms 6.646 ms
12 ce-0-1-0-0.r01.lsanca20.us.ce.gin.ntt.ne (128.241.6.1) 6.085 ms 5.813 ms 5.668 ms

Deleted the T in .net

But essentially the same routing/issues as the others here.

Not trying to be a snooty, but it seems like an issue with the routing to a Blizzard server, talked to a networking friend and he suggested its not on my (our) ends.

18

^^^ Thats me, Zul’Jin is my server, forgot to mention that. The trace was the wrong one, forgot I was testing it with my VPN, although the same cluster of servers seem to be an issue. (.com removed) It gets much worse around 830-9.

1 Blizzard Blizzard 0.476 ms 0.441 ms 0.440 ms
2 24.105.18.2 (24.105.18.2) 0.585 ms 0.632 ms 0.681 ms
3 137.221.105.10 (137.221.105.10) 0.729 ms 0.740 ms 0.777 ms
4 137.221.66.16 (137.221.66.16) 0.495 ms 0.513 ms 0.527 ms
5 137.221.83.80 (137.221.83.80) 294.166 ms 294.183 ms 294.195 ms
6 * * *
7 137.221.69.32 (137.221.69.32) 38.170 ms 38.613 ms 38.663 ms
8 eqix-ch1-ix.teksavvy (208.115.136.65) 49.513 ms 49.867 ms 49.851 ms
9 ae8-0-bdr01-tor2.teksavvy (206.248.155.9) 60.859 ms 66.642 ms 66.640 ms
10 ae3-0-agg01-tor2.teksavvy (206.248.155.93) 58.998 ms 58.881 ms 58.885 ms
11 richmond_road-ottawa.rcable-tsi.tor2.teksavvy (104.195.129.2) 48.468 ms 48.417 ms 48.548 ms
12 * * *
13 * * *
14 * * *
15 * * *

19

Hey there,

The downstream looks fine from the LookingGlass test. Could you try this winMTR instead to check the upstream? It should look similar to the one posted by Alarael.

On that note, I do need to mention that the problem in Alarael’s winMTR appears here:

Basically some data is being lost in transit between the game client and game servers. This causes the game to have to wait and re-send/receive the same data which may result in an increased display for latency in-game. The in-game display measures how long the game waits on data, so if it has to redo stuff it will make the number higher regardless of what the actual latency is.

Thanks! We look forward to your reply!

20

I have the same problem. We’re in the same area in Ottawa. M+ is impossible for me to play as I lag out all the time. I called TekSavvy and they’re idiots and won’t acknowledge the problem or provide any solution. I don’t know what else to do stop playing WoW all together.

21

I’ve had the same experience, my sub has 13 days left so I guess just let it run out and hope SL is better.

22

This is happening again tonight (first time on since last Weds at peak), though it feels not as drastic yet. Started spiking at 9:20pm EDT. Currently 46/680.

23

Same here at 57/913.

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

|                                      WinMTR statistics                                   |

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

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

|                   ENTERPRISE.ENTERPRISE -    0 |  160 |  160 |    0 |    0 |   10 |    0 |

|                            69.63.242.42 -    0 |  160 |  160 |   12 |   39 |  177 |   21 |

|richmond_road-ottawa.rcable-tsi.tor.teksavvy.com -    6 |  132 |  125 |   14 |   35 |  174 |   24 |

|richmond_road-ottawa.tsi-rcable.tor2.teksavvy.com -    0 |  160 |  160 |   15 |   36 |  176 |   22 |

|          ae10-0-bdr01-tor2.teksavvy.com -    1 |  156 |  155 |   15 |   35 |  179 |   22 |

|           ae12-0-bdr01-tor.teksavvy.com -    4 |  140 |  135 |   16 |   36 |  122 |   31 |

|                eqix-ix-ch1.blizzard.com -    9 |  124 |  114 |   24 |   51 |  186 |   28 |

|         et-0-0-0-pe04-eqch2.as57976.net -   84 |   37 |    6 |    0 |   33 |   46 |   27 |

|         et-0-0-0-pe04-eqch2.as57976.net -    0 |  160 |  160 |   24 |   51 |  213 |   32 |

|        chi-eqch2-ia-bons-04.as57976.net -   11 |  112 |  100 |   26 |   49 |  173 |   28 |

|                           24.105.62.129 -    8 |  126 |  117 |   24 |   49 |  188 |   32 |

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

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

Hey all,

Thanks for the new reports and new WinMTRs. While the high latency is occurring, the more WinMTRs that we can get posted the better. This allows us to see what the connection path is doing and gauge how many are being affected.

Since the problem appears to only show up around peak times it’s very likely there’s a problem occurring between Teksavvy and the Blizzard network that’s causing this. We’re tracking this on our end, and we would encourage players to reach out to Teksavvy support as well just to report this so they can do the same.

Thanks!

25

This is from tonight. I ran it until my internet literally crashed (is running this too long something that might get flagged for DC? haha) either way, I tried to run as long as possible:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
INTEL_CE_LINUX - 1 2080 2074 1 6 141 5
135-23-121-225.cpe.pppoe. ca - 1 2057 2045 9 22 540 540
kitchener.rcable-tsi.tor.teksavvy. com - 31 945 654 0 24 148 16
kitchener.tsi-rcable.tor.teksavvy. com - 4 1817 1745 10 25 202 40
ae2-0-bdr01-tor2.teksavvy. com - 2 1997 1970 12 27 172 104
eqix-ix-ny8.blizzard. com - 4 1833 1765 24 40 214 33
ae1-br01-eqny8.as57976. net - 4 1866 1807 35 154 2664 176
No response from host - 100 422 0 0 0 0 0
et-0-0-1-pe02-eqch2.as57976. net - 3 1934 1891 31 48 536 536
chi-eqch2-ia-bons-02.as57976. net - 3 1929 1885 35 49 171 48
24.105.62.129 - 4 1858 1796 35 47 189 64
________________________________________________ ______ ______ ______ ______ ______ ______

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

26

Posting here as well to add to the dataset. Teksavvy ISP, exact same issue >.<

Host % Sent Recv Best Avrg Wrst Last
Mr-Shine-and-Mr 0 372 372 0 0 5 0
66.185.91.158 0 372 372 18 32 208 27
fallowfield-ottawa.rcable-tsi.tor.teksavvy .com 7 297 278 12 24 182 19
fallowfield-ottawa.tsi-rcable.tor2.teksavvy .com 0 372 372 14 26 142 23
ae1-0-bdr01-tor.teksavvy .com 3 336 327 17 28 138 22
ae8-0-bdr01-tor2.teksavvy .com 0 372 372 16 27 147 28
eqix-ix-ny8.blizzard .com 10 273 248 27 47 225 37
ae1-br01-eqny8.as57976 .net 2 348 342 76 168 1087 109
No response from host 100 75 0 0 0 0 0
No response from host 100 75 0 0 0 0 0
No response from host 100 75 0 0 0 0 0
et-0-0-0-pe01-swlv10.as57976 .net 2 349 343 73 89 223 189
137.221.105.2 14 241 208 73 89 250 159

Edit: and my ping, which usually hovers around 65ms, has reached as high as 3300ms during these windows.

27

It keeps happening. Everything I’ve done on my end has not worked. Raided from 730 to 10; 730-850 was normal and then 600-1100+ Ping. Stop raiding, played counter strike, 0 issues, logged back in and the lag was still there at about 11.

100% conviced is the server hand off between techsavy and blizzard’s New York servers. Wow sub is expiring, only raid log, no reason to play the game anymore.

Hope it magically gets fixed soon or in shadowlands.

28

Any Blizz updates on this issue?

29

Going to chime in on this with my WinMTR text come next Tuesday during raid as this is happening to me as well.

30

It’s not Blizzard. See my own data with TekSavvy with connectivity data collected since last week: rogers.sinap.se/ping-plots/

24.105.62.129 in the plots is a Blizzard server.

I am experiencing the same problems with a number of different services and games during peak hours tied to packet loss and latency issues. It appears that the additional COVID load has revealed what we all suspected with TPIAs - infrastructure investment by Rogers et. al. was just enough to satisfy CRTC concerns prior to the pandemic sending everyone inside. Coupling that with changing trends regarding streaming, here we are.

I’d recommend switching to DSL or Fibre technology, even if only temporarily, as it is not subject to the same neighbourhood congestion issues. At least one person I know is switching to a cable offering from Start.ca to see if switching TPIAs is enough but I am unconvinced their hardware is any different at the node. My vDSL order is on the way. Some Rogers first party customers have been complaining of the same thing.

1 Like
31

I would agree that things have been overloaded since COVID, except that this is not something that has happened throughout COVID. Something has changed and needs to be addressed somewhere along the line.

It’s crappy that you have had this experience with other services alongside with Blizzard connectivity; however, many of us, like myself, are literally only experiencing this with Blizzard (mainly WoW) connectivity. I did multiple SpeedTests, among other things, while this latency was happening. Crystal clear in Discord as well, with no drops.

I have been raiding 2-3 days per week since before, and through COVID on the same network, the same hardware, and the same level of internet access (currently on 60 down 15 up) and haven’t had issues like this until the past few weeks, as the first poster expressed.

Something has changed here, and COVID-pressure alone is not to blame.

1 Like
32

Do you play any other latency sensitive games such as Path of Exile during the 9pm-12am congestion periods? Discord uses a different underlying protocol and will not exhibit the same behavior as WoW.

1 Like
33

Yes I do. I only play WoW on raid nights these days, but play a variety of latency sensitive games at peak times throughout the week and weekends too.

34

Its only blizzard games, havent had issues with any other games ive played during the same time frame.

35

It looks like there may be some packet loss on the hand-off between Equinix and Teksavvy. I’ll get this information added to our tracking. If anyone who uses Teksavvy is in contact with them please be sure to ask the agent you are speaking with to escalate a ticket internally as well.

Any ISP should have staff available to escalate reports that require interaction with “Peer Networks” such as Equinix to resolve problems with routing and signal stability. Reporting problems to the service provider so that they may contact peer networks should help expedite a resolution.

Thanks for the reports! If you are using this service provider and have the high latency problems, please continue to post winMTR reports.

1 Like
36

Same again tonight and you can see packet drops at all hops to blizzard.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   ENTERPRISE.ENTERPRISE -    0 |  962 |  962 |    0 |    0 |    4 |    0 |
|                            69.63.242.42 -    5 |  815 |  778 |   14 |   29 |  158 |   28 |
|richmond_road-ottawa.rcable-tsi.tor.teksavvy.com -   24 |  498 |  382 |    0 |   26 |  156 |  119 |
|richmond_road-ottawa.tsi-rcable.tor2.teksavvy.com -   16 |  591 |  498 |   14 |   26 |  161 |   29 |
|          ae10-0-bdr01-tor2.teksavvy.com -    5 |  811 |  773 |   12 |   27 |  164 |   20 |
|           ae12-0-bdr01-tor.teksavvy.com -    2 |  915 |  904 |   13 |   26 |  163 |   24 |
|                eqix-ix-ch1.blizzard.com -    6 |  791 |  748 |   22 |   39 |  196 |   27 |
|         et-0-0-0-pe04-eqch2.as57976.net -   95 |  202 |   12 |    0 |   42 |  162 |   30 |
|         et-0-0-0-pe04-eqch2.as57976.net -   12 |  667 |  593 |   24 |   39 |  174 |   35 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  192 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider