Random Latency Spikes in Game

Technical Support
1

My latency in game when performing well is ~50ms, but on seemingly any day my latency will start jumping up hundreds of ms, sometimes even thousands, then back down again at random intervals. Abilities undo themselves, myself and enemies teleport around the map, and it’s just generally unplayable. This problem has persisted randomly for quite some time now, showing up for several hours or even days then disappearing for no apparent reason. I have tried:
resetting network devices
Release/renew ip and flush dns
Update drivers
Optimized wifi connection (I cannot use ethernet)
closing all other aplications
Updated network card drivers and settings
Disabling proxies
Running antivirus
No VPN
No security programs

I do not have problems loading videos or using the internet for anything other than gaming.

Traceroute

Tracing route to 24.105.13.123 over a maximum of 30 hops

  1     2 ms     4 ms     7 ms  192.168.1.254 
  2     7 ms     4 ms     3 ms  d64-180-196-1.bchsia.telus.net [64.180.196.1] 
  3     8 ms     8 ms     9 ms  STTLWAWBCI01.bb.telus.com [75.154.217.106] 
  4     8 ms     8 ms     8 ms  six.blizzardonline.net [206.81.81.122] 
  5    35 ms    34 ms    34 ms  ae1-br01-eqse2.as57976.net [137.221.73.33] 
  6    53 ms    29 ms    39 ms  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40] 
  7  2701 ms  1102 ms  1539 ms  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Pathping

Tracing route to 24.105.13.123 over a maximum of 30 hops

  0  DESKTOP-0K76179.telus [192.168.1.73] 
  1  192.168.1.254 
  2  d64-180-196-1.bchsia.telus.net [64.180.196.1] 
  3  STTLWAWBCI01.bb.telus.com [75.154.217.106] 
  4  six.blizzardonline.net [206.81.81.122] 
  5  ae1-br01-eqse2.as57976.net [137.221.73.33] 
  6  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40] 
  7  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 
  8     *        *        *     
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP-0K76179.telus [192.168.1.73] 
                                0/ 100 =  0%   |
  1    4ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254 
                                0/ 100 =  0%   |
  2    7ms     0/ 100 =  0%     0/ 100 =  0%  d64-180-196-1.bchsia.telus.net [64.180.196.1] 
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  STTLWAWBCI01.bb.telus.com [75.154.217.106] 
                                0/ 100 =  0%   |
  4  ---     100/ 100 =100%   100/ 100 =100%  six.blizzardonline.net [206.81.81.122] 
                                0/ 100 =  0%   |
  5   10ms     0/ 100 =  0%     0/ 100 =  0%  ae1-br01-eqse2.as57976.net [137.221.73.33] 
                                0/ 100 =  0%   |
  6   32ms     0/ 100 =  0%     0/ 100 =  0%  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40] 
                                0/ 100 =  0%   |
  7   43ms     0/ 100 =  0%     0/ 100 =  0%  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 

Trace complete.
2 Likes
3

Anything? This problem has been getting worse lately, and now that the endorsement system is out I’m scared to even play QP since I’m punished for every game I can’t finish.

4

Have you run another WinMTR to see if the problem is fixed?

5

Having issue with eqla server

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 115 115 0 0 8 0
No response from host 100 23 0 0 0 0 0
dtr01hsprca-tge-0-0-0-19.hspr.ca.charter.com 0 115 115 7 9 21 8
96-34-98-243.static.unas.ca.charter.com 0 115 115 8 11 13 8
bbr01stcdmn-tge-0-1-0-3.stcd.mn.charter.com 0 115 115 9 14 21 17
bbr01ashbva-tge-0-1-0-1.ashb.va.charter.com 0 115 115 12 13 20 14
eqix-ix-la1.blizzard.com 0 115 115 12 13 31 13
ae1-br01-eqla1.as57976.net 0 115 115 10 76 1177 14
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
6

spikes at 1100ms is crazy bad

7

I’ve made blizzard aware of this issue months ago, they ignored it and closed the threads that had it. This is exactly what my WinMTR tests look like in both Overwatch and WoW, always an Equinex (eq) route causing the problem. Mine are usually around 200-500ms jumps on the route.

Edit: Out of curiosity to those seeing these issues where are you located? When dealing with blizzard support we had isolated this issue to Canadian ISPs (I’ve tried Shaw and Telus). But I was never sure if people elsewhere had these issues (I’m in Alberta).

8

I am on NA West servers (LAX1), Southern California area. So it is an issue here in the US as well and has been for some time now. Since the Brigitte roll out

9

And I find it alarming this has never been seriously addressed. It has made me stop playing for the most part. Really kills the game for me

10

I was also placed in this server earlier today as well. from what the google tells me it is routing through Hong Kong?

          WinMTR statistics                                   |
Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 138 138 0 0 0 0
No response from host - 100 28 0 0 0 0 0
dtr01hsprca-tge-0-0-0-19.hspr.ca.charter. com - 0 138 138 4 9 20 8
96-34-98-243.static.unas.ca.charter. com - 0 138 138 10 11 20 12
bbr01stcdmn-tge-0-1-0-3.stcd.mn.charter. com - 0 138 138 8 15 25 12
bbr01snloca-bue-1.snlo.ca.cha rter. com - 0 138 138 14 20 32 26
bbr02snloca-bue-4.snlo.ca.ch arter. com - 0 138 138 11 19 33 17
bbr01snjsca-bue-6.snjs.ca.cha rter. com - 0 138 138 29 34 43 34
prr01snjsca-bue-5.snjs.ca.ch arter. com - 0 138 138 24 25 35 26
96-34-154-3.static.unas.ca.c harter. com - 0 138 138 21 26 37 25
TenGE0-1-0-17.br02.h kg12.pccwb tn.ne t - 2 131 129 182 185 197 184
amazon.buneth1.br02.hkg12.pcc wbtn. ne t - 2 131 129 180 185 202 184
No response from host - 100 28 0 0 0 0 0
No response from host - 100 28 0 0 0 0 0
No response from host - 100 28 0 0 0 0 0
No response from host - 100 28 0 0 0 0 0
52.93.8.12 - 3 127 124 220 222 235 221
52.93.11.33 - 3 127 124 208 210 242 210
52.93.11.32 - 3 127 124 197 199 211 199
52.93.8.29 - 3 127 124 201 202 242 201
203.83.223.31 - 2 131 129 216 219 233 218
11

Still no blue post on this? Sweet

12

I, too, am having issues starting at the as57976.net server. Specifically, packet loss of about 23%. My ISP is Monkeybrains.

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
 [...]
  9   11ms     0/ 100 =  0%     0/ 100 =  0%  ae1-br01-eqsv5.as57976.net [137.221.70.33] 
                               23/ 100 = 23%   |
 10  296ms    23/ 100 = 23%     0/ 100 =  0%  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
1 Like
13

Your WinMTR is showing an issue on a routing partner that your ISP uses to connect you to Blizzard (2% packet loss and high/poor response time), so they wouldn’t be able to comment on another company’s network reliability.

All ping response times and packet loss will be inflated on those eq addresses, as those servers don’t immediately respond to pings because they have DDoS protection enabled. You can basically ignore them when looking at a WinMTR.

14

Hard to ignore that address given that all 3 people in this thread have the same host at the end of their WinMTR. It’s also the only host that has significant packet loss on my end.

15

I have the same results showing, with no lag issues, and have had these results for the past 2 years. It’s not an issue on that hop.

16

So what is the issue in your professional opinion?

17

I don’t know if I’d call it a professional opinion, but I did point out the issue in one of my previous replies. The routing partner your ISP works with/leases lines from is having 2% packet loss.

19

I am also having a similar issue with my game, mine is routing to Hong Kong at some point, and from what I can guess, it is losing 50% of the packets?

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 0 | 8 | 8 | 0 | 0 | 1 | 0 |

| 184-6-128-254.dthn.centurylink.net - 0 | 8 | 8 | 48 | 57 | 62 | 58 |

| dthn-agw1.inet.qwest.net - 0 | 8 | 8 | 59 | 69 | 76 | 70 |

| atx3-brdr-01.inet.qwest.net - 0 | 8 | 8 | 63 | 74 | 81 | 75 |

| 4.68.74.157 - 50 | 4 | 2 | 0 | 71 | 72 | 71 |

| ae-1-3514.edge2.Atlanta4.Level3.net - 0 | 8 | 8 | 65 | 76 | 86 | 76 |

| BLIZZARD-EN.edge2.Atlanta4.Level3.net - 0 | 8 | 8 | 65 | 77 | 86 | 79 |

| ae1-br01-eqat2.as57976.net - 0 | 8 | 8 | 74 | 87 | 131 | 75 |

| et-0-0-4-br02-eqch2.as57976.net - 0 | 8 | 8 | 88 | 146 | 300 | 259 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

20

Same exact case here, works fine on xbox version though

| WinMTR statistics |

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

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

| dslrouter.netgear com - 10 | 199 | 181 | 1 | 232 | 4489 | 186 |

| adr01.hrbg.pa.frontiernet net - 10 | 190 | 171 | 16 | 312 | 3777 | 1022 |

| ae2—0.car01.dlls.pa.frontiernet net - 12 | 184 | 163 | 19 | 324 | 3481 | 108 |

| ae3—0.cor01.asbn.va.frontiernet net - 11 | 190 | 170 | 27 | 322 | 3812 | 29 |

| ae0—0.cbr01.asbn.va.frontiernet net - 11 | 186 | 166 | 28 | 323 | 4060 | 1069 |

| eqix-dc2.blizzard com - 7 | 212 | 199 | 27 | 313 | 4150 | 1023 |

| ae1-br01-eqdc2.as57976 net - 8 | 207 | 191 | 29 | 284 | 3481 | 133 |

| et-0-0-2-br01-eqch2.as57976 net - 8 | 206 | 191 | 48 | 345 | 4570 | 53 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

21

So I work with an ISP in the Bay Area and we have had more than one customer complaint that I’ve traced down to this same machine/site (found this thread via Google since its the same problem).

Basically we peer with AS57976 at SFMIX which is an open exchange located in the San Francisco area (SF Metro Intenet eXchange in case you didn’t get it :slight_smile: )

From this exchange, it then goes over a Blizzard backbone link to LA down to the Equinix Facility down next to the One Wilshire Internet Exchange. Prior dealings with Blizzard indicate that this machine is one of their filter/regulation machines that helps deal with “bad players” and such.

xe-0-0-1-1-br02-eqla1 – This translates (typically) to a Cisco ASR or ISR (in this case probably an ISR) that is either a border router or branch router (0-0-1-1 indicates the slot/board/controller/interface) and is located in Equinix LA #1.

What does this mean? That a lot of the US West Coast IXs will route through this machine on their way to USWest based servers in the Blizzard Network.

Anyway, there are enough different ISPs that are having this same problem that there likely is either an issue with the router (generally unlikely) or with the configuration/programming of it (more likely) and how it is doing either traffic shaping or traffic rejection.

For the person on MonkeyBrains, looks like your traffic also goes through SFMIX as I believe your company is SF based as well.

24

Exact same issue for me too. Issue started around 2 months ago and had never experienced anything like it before. MonkeyBrains as my ISP. I do play over ps4 though (a fair bit). I’m not really into griefing and have never thrown a game in competitive, so not sure why I would be on a watch list…