Random Latency Spikes in Game

Anjunabeats-11820 · September 28, 2018, 8:37am

spikes at 1100ms is crazy bad

VeiledFlame-1983 · September 28, 2018, 5:45pm

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).

Anjunabeats-11820 · September 29, 2018, 4:21am

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

Anjunabeats-11820 · September 29, 2018, 4:24am

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

Anjunabeats-11820 · September 29, 2018, 4:33am

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

Anjunabeats-11820 · November 21, 2018, 9:23am

Still no blue post on this? Sweet

funkylime-1237 · November 27, 2018, 2:02am

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]

Nicole-1893 · November 27, 2018, 2:16am

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.

funkylime-1237 · November 27, 2018, 3:18am

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.

Nicole-1893 · November 27, 2018, 3:41am

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.

Anjunabeats-11820 · November 30, 2018, 8:14am

So what is the issue in your professional opinion?

Nicole-1893 · November 30, 2018, 8:43am

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.

ŠËRÅPHĮNȁ-1139 · December 17, 2018, 3:26am

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 |

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

| 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 |

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

SnowManMan11-1206 · December 17, 2018, 9:02pm

Same exact case here, works fine on xbox version though

| WinMTR statistics |

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

| 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 |

Palladon-1277 · December 22, 2018, 5:39pm

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 )

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.

cwra007-1849 · December 29, 2018, 1:07am

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…

cwra007-1849 · December 29, 2018, 1:09am

Oh, and LAN connection with a fairly new ASUS AC3100 router.

Shockashn-1451 · February 1, 2020, 12:10am

Random high latency spikes, It will go from 43ms to 150 or higher. When this happens players move all over the screen and the game cant be played. Been happening for about a month now. I have 1gb download and 26mb upload speeds. My computers are running GTX1080 and RTX 2080TI.

Please help this is only an issue on Overwatch.

Here is my traceroute info:
TRACEROUTE:
traceroute to 73.152.6.153 (73.152.6.153), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.404 ms 0.375 ms 1.142 ms
2 24.105.18.131 (24.105.18.131) 0.736 ms 0.812 ms 0.816 ms
3 137.221.105.12 (137.221.105.12) 1.150 ms 1.149 ms 1.176 ms
4 137.221.66.16 (137.221.66.16) 1.123 ms 1.123 ms 1.123 ms
5 137.221.83.80 (137.221.83.80) 6.342 ms 6.351 ms 6.354 ms
6 137.221.65.68 (137.221.65.68) 5.956 ms 7.873 ms 7.847 ms
7 137.221.68.32 (137.221.68.32) 9.440 ms 9.488 ms 9.484 ms
8 te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcastnet (23.30.206.153) 7.149 ms 7.167 ms 7.169 ms
9 be-11545-cr02.losangeles.ca.ibone.comcastnet (68.86.84.233) 8.313 ms 6.378 ms 6.348 ms
10 be-11523-cr01.houston.tx.ibone.comcastnet (68.86.87.174) 32.781 ms 32.833 ms 34.194 ms
11 be-11423-cr02.56marietta.ga.ibone.comcastnet (68.86.85.21) 45.623 ms 46.736 ms 45.962 ms
12 ae-4-ar02.staplesmllrd.va.richmond.comcastnet (68.86.94.30) 57.402 ms 57.234 ms 57.209 ms
13 162.151.163.70 (162.151.163.70) 63.185 ms 63.329 ms 63.295 ms
14 te-7-1-acr01.tollesboro.va.richmond.comcastnet (96.108.131.130) 63.332 ms 63.363 ms 63.410 ms
15 c-73-152-6-153.hsd1.va.comcastnet (73.152.6.153) 75.237 ms 79.524 ms 79.556 ms

31/01/2020 23:46:00 UTC

TRACEROUTE:
traceroute to 73.152.6.153 (73.152.6.153), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.057 ms 1.082 ms 1.094 ms
2 24.105.18.131 (24.105.18.131) 1.758 ms 1.796 ms 1.810 ms
3 137.221.105.12 (137.221.105.12) 2.125 ms 2.136 ms 2.162 ms
4 137.221.66.16 (137.221.66.16) 2.005 ms 2.042 ms 2.036 ms
5 137.221.83.80 (137.221.83.80) 6.769 ms 6.798 ms 6.813 ms
6 137.221.65.68 (137.221.65.68) 6.576 ms 6.007 ms 6.030 ms
7 137.221.68.32 (137.221.68.32) 6.126 ms 6.067 ms 6.065 ms
8 te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcastnet (23.30.206.153) 5.768 ms 5.800 ms 5.896 ms
9 be-11545-cr02.losangeles.ca.ibone.comcastnet (68.86.84.233) 8.294 ms 7.729 ms 7.713 ms
10 be-11523-cr01.houston.tx.ibone.comcastnet (68.86.87.174) 32.457 ms 33.670 ms 33.015 ms
11 be-11423-cr02.56marietta.ga.ibone.comcastnet (68.86.85.21) 46.881 ms 46.339 ms 46.591 ms
12 ae-4-ar02.staplesmllrd.va.richmond.comcastnet (68.86.94.30) 57.476 ms 57.355 ms 57.354 ms
13 162.151.163.70 (162.151.163.70) 63.417 ms 63.530 ms 63.547 ms
14 te-7-1-acr01.tollesboro.va.richmond.comcastnet (96.108.131.130) 63.202 ms 63.112 ms 63.239 ms
15 * * *

31/01/2020 23:46:00 UTC

PING:
PING 73.152.6.153 (73.152.6.153) 56(84) bytes of data.

— 73.152.6.153 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

31/01/2020 23:46:00 UTC

PING:
PING 73.152.6.153 (73.152.6.153) 56(84) bytes of data.

— 73.152.6.153 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

31/01/2020 23:46:00 UTC

MTR:
Start: Fri Jan 31 23:46:00 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 41.6 5.9 0.5 41.6 13.0
3.|-- 137.221.105.12 0.0% 10 1.0 1.1 0.8 2.4 0.0
4.|-- 137.221.66.16 0.0% 10 0.5 9.0 0.5 84.8 26.6
5.|-- 137.221.83.80 0.0% 10 5.9 12.0 5.7 25.1 8.3
6.|-- 137.221.65.68 0.0% 10 5.7 9.4 5.7 41.8 11.4
7.|-- 137.221.68.32 0.0% 10 5.9 10.2 5.8 48.2 13.4
8.|-- te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcastnet 0.0% 10 5.7 5.7 5.6 5.9 0.0
9.|-- be-11545-cr02.losangeles.ca.ibone.comcastnet 0.0% 10 6.6 6.9 6.2 8.2 0.3
10.|-- be-11523-cr01.houston.tx.ibone.comcastnet 0.0% 10 32.4 33.3 32.4 34.5 0.5
11.|-- be-11423-cr02.56marietta.ga.ibone.comcastnet 0.0% 10 45.2 45.6 44.8 46.7 0.5
12.|-- ae-4-ar02.staplesmllrd.va.richmond.comcastnet 0.0% 10 65.4 58.2 57.2 65.4 2.5
13.|-- 162.151.163.70 0.0% 10 63.1 63.3 63.1 63.9 0.0
14.|-- te-7-1-acr01.tollesboro.va.richmond.comcastnet 0.0% 10 63.1 63.3 63.1 64.0 0.0
15.|-- c-73-152-6-153.hsd1.va.comcastnet 90.0% 10 72.8 72.8 72.8 72.8 0.0

31/01/2020 23:46:00 UTC

MTR:
Start: Fri Jan 31 23:46:00 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 2.0 0.6 9.1 2.7
3.|-- 137.221.105.12 0.0% 10 1.0 1.0 0.8 1.1 0.0
4.|-- 137.221.66.16 0.0% 10 0.4 6.6 0.3 61.4 19.2
5.|-- 137.221.83.80 0.0% 10 5.9 11.4 5.7 61.4 17.5
6.|-- 137.221.65.68 0.0% 10 5.9 13.1 5.8 70.2 20.2
7.|-- 137.221.68.32 0.0% 10 5.8 6.0 5.8 6.4 0.0
8.|-- te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcastnet 0.0% 10 5.7 5.7 5.6 6.0 0.0
9.|-- be-11545-cr02.losangeles.ca.ibone.comcastnet 0.0% 10 6.8 7.2 6.5 8.2 0.3
10.|-- be-11523-cr01.houston.tx.ibone.comcastnet 0.0% 10 33.9 34.2 32.5 40.7 2.3
11.|-- be-11423-cr02.56marietta.ga.ibone.comcastnet 0.0% 10 45.9 45.7 45.0 46.5 0.0
12.|-- ae-4-ar02.staplesmllrd.va.richmond.comcastnet 0.0% 10 57.3 58.1 57.2 65.6 2.5
13.|-- 162.151.163.70 0.0% 10 63.2 63.3 63.1 63.6 0.0
14.|-- te-7-1-acr01.tollesboro.va.richmond.comcastnet 0.0% 10 63.7 63.3 63.1 63.7 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

31/01/2020 23:46:00 UTC.

Nicole-1893 · February 1, 2020, 2:56am

Please stop adding your test to multiple threads, especially ones that are a year old. You should only be posting this in your own, new thread. No troubleshooting will happen on threads that aren’t yours because they alert the original poster as well.