Better advice would probably be to uninstall KNM. My personal impression of it is that it’s A: garbage code and B: often in conflict with other network “QoS” hacks, and even with the network stack itself sometimes.
Responded to the wrong post. See above.
Hi! I’ve been experiencing the same issue the last week or so (that I’ve noticed). It seems to be an on/off thing, but I’ll log in and have a constant latency around 240-250 ms. I then go to Fortnite, and run 30-70 ms.
I ran the Looking Glass trace (all three options) and got the following. Is this any help?
TRACEROUTE:
traceroute to 64.184.151.9 (64.184.151.9), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.288 ms 0.263 ms 0.261 ms
2 37.244.22.131 (37.244.22.131) 0.595 ms 0.670 ms 0.751 ms
3 24.105.30.148 (24.105.30.148) 1.091 ms 1.111 ms 1.142 ms
4 137.221.66.0 (137.221.66.0) 1.655 ms 1.722 ms 1.849 ms
5 137.221.68.70 (137.221.68.70) 1.568 ms 1.571 ms 1.571 ms
6 137.221.65.7 (137.221.65.7) 8.478 ms 8.467 ms 8.462 ms
7 137.221.65.41 (137.221.65.41) 25.704 ms 25.698 ms 25.686 ms
8 137.221.73.32 (137.221.73.32) 25.457 ms 25.587 ms 25.562 ms
9 * * *
10 xe-0-0-1.brm.cor0.noanet.net (64.184.134.30) 33.060 ms 33.056 ms 33.061 ms
11 1-1-24.chj-mpls0.noanet.net (64.184.134.209) 32.776 ms 32.756 ms 32.880 ms
12 bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net (66.119.193.242) 33.251 ms 33.007 ms 33.004 ms
13 64.146.233.106 (64.146.233.106) 36.584 ms 36.058 ms 36.343 ms
14 64.146.233.226 (64.146.233.226) 35.997 ms 34.154 ms 34.103 ms
15 * * *
21/07/2018 05:38:05 UTC
--------------------
TRACEROUTE:
traceroute to 64.184.151.9 (64.184.151.9), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.038 ms 2.020 ms 2.018 ms
2 37.244.23.130 (37.244.23.130) 3.283 ms 3.301 ms 3.327 ms
3 24.105.62.146 (24.105.62.146) 3.336 ms 3.339 ms 3.341 ms
4 137.221.66.12 (137.221.66.12) 5.175 ms 5.177 ms 5.180 ms
5 137.221.69.72 (137.221.69.72) 5.122 ms 5.146 ms 5.150 ms
6 137.221.65.43 (137.221.65.43) 52.246 ms 50.557 ms 50.547 ms
7 137.221.73.32 (137.221.73.32) 50.467 ms 50.489 ms 50.476 ms
8 * * *
9 xe-0-0-1.brm.cor0.noanet.net (64.184.134.30) 58.010 ms 58.027 ms 58.097 ms
10 1-1-24.chj-mpls0.noanet.net (64.184.134.209) 57.600 ms 58.036 ms 58.013 ms
11 bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net (66.119.193.242) 57.830 ms 57.637 ms 57.665 ms
12 64.146.233.106 (64.146.233.106) 58.327 ms 58.475 ms 58.462 ms
13 64.146.233.226 (64.146.233.226) 59.487 ms 59.621 ms 59.790 ms
14 * * *
15 * * *
21/07/2018 05:38:05 UTC
--------------------
PING:
PING 64.184.151.9 (64.184.151.9) 56(84) bytes of data.
--- 64.184.151.9 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms
21/07/2018 05:38:05 UTC
--------------------
PING:
PING 64.184.151.9 (64.184.151.9) 56(84) bytes of data.
--- 64.184.151.9 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3007ms
21/07/2018 05:38:05 UTC
--------------------
MTR:
Start: Sat Jul 21 05:38:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.8 0.0
2.|-- 37.244.23.130 0.0% 10 0.5 0.6 0.4 1.3 0.0
3.|-- 24.105.62.146 0.0% 10 1.0 1.1 0.8 2.2 0.3
4.|-- 137.221.66.12 0.0% 10 2.4 2.5 2.3 3.3 0.0
5.|-- 137.221.69.72 0.0% 10 2.3 2.5 2.2 3.4 0.0
6.|-- 137.221.65.43 0.0% 10 50.5 53.5 50.5 78.7 8.8
7.|-- 137.221.73.32 0.0% 10 50.5 50.6 50.3 51.8 0.3
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- xe-0-0-1.brm.cor0.noanet.net 0.0% 10 57.8 57.8 57.8 57.9 0.0
10.|-- 1-1-24.chj-mpls0.noanet.net 0.0% 10 57.5 57.6 57.4 58.6 0.0
11.|-- bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net 0.0% 10 57.6 57.9 57.6 58.3 0.0
12.|-- 64.146.233.106 0.0% 10 58.5 58.6 58.3 59.0 0.0
13.|-- 64.146.233.226 0.0% 10 60.0 60.3 59.0 66.4 2.1
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21/07/2018 05:38:05 UTC
--------------------
MTR:
Start: Sat Jul 21 05:38:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 1.0 0.0
2.|-- 37.244.22.131 0.0% 10 0.5 0.6 0.4 1.0 0.0
3.|-- 24.105.30.148 0.0% 10 1.0 1.1 0.9 1.3 0.0
4.|-- 137.221.66.0 0.0% 10 1.6 1.6 1.3 2.6 0.3
5.|-- 137.221.68.70 0.0% 10 1.3 1.5 1.3 1.9 0.0
6.|-- 137.221.65.7 0.0% 10 8.3 8.5 8.3 9.3 0.0
7.|-- 137.221.65.41 0.0% 10 25.8 28.6 25.7 47.0 6.8
8.|-- 137.221.73.32 0.0% 10 25.6 25.6 25.5 25.8 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- xe-0-0-1.brm.cor0.noanet.net 0.0% 10 33.0 33.0 32.9 33.3 0.0
11.|-- 1-1-24.chj-mpls0.noanet.net 0.0% 10 33.3 32.9 32.8 33.3 0.0
12.|-- bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net 0.0% 10 33.1 33.2 33.0 33.4 0.0
13.|-- 64.146.233.106 0.0% 10 33.2 33.2 33.0 33.7 0.0
14.|-- 64.146.233.226 0.0% 10 34.4 34.3 34.0 34.6 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21/07/2018 05:38:05 UTC
--------------------That is not to an Overwatch server, is it? You need to select it in the dropdown to the left, instead of Battlenet servers or whatever the default is.
Yeah after updating it all didn’t help I ended up just uninstalling but it still didn’t seem to make any difference. Thanks for the suggestion though.
No, I selected Overwatch if I recall correctly. I just logged in this morning and my latency is in the 60s (normal); as I said it’s an on/off thing. I’ll throw in the Looking Glass trace for now, anyway:
TRACEROUTE:
traceroute to 64.184.151.9 (64.184.151.9), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.315 ms 0.296 ms 0.294 ms
2 37.244.22.3 (37.244.22.3) 0.581 ms 0.625 ms 0.762 ms
3 24.105.30.148 (24.105.30.148) 1.139 ms 1.149 ms 1.219 ms
4 137.221.66.4 (137.221.66.4) 1.525 ms 1.586 ms 1.632 ms
5 137.221.68.72 (137.221.68.72) 1.544 ms 1.545 ms 1.545 ms
6 137.221.65.7 (137.221.65.7) 8.453 ms 8.411 ms 8.395 ms
7 137.221.65.41 (137.221.65.41) 25.741 ms 25.824 ms 25.792 ms
8 137.221.73.32 (137.221.73.32) 25.640 ms 25.567 ms 25.545 ms
9 * * *
10 xe-0-0-1.brm.cor0.noanet.net (64.184.134.30) 33.366 ms 33.375 ms 33.487 ms
11 1-1-24.chj-mpls0.noanet.net (64.184.134.209) 32.705 ms 32.688 ms 33.168 ms
12 bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net (66.119.193.242) 33.027 ms 33.089 ms 32.761 ms
13 64.146.233.106 (64.146.233.106) 33.451 ms 32.929 ms 33.107 ms
14 64.146.233.226 (64.146.233.226) 34.242 ms 34.141 ms 34.411 ms
15 * * *
21/07/2018 15:01:10 UTC
--------------------
TRACEROUTE:
traceroute to 64.184.151.9 (64.184.151.9), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.676 ms 0.673 ms 0.675 ms
2 * * *
3 * * *
4 137.221.66.12 (137.221.66.12) 3.120 ms 3.141 ms 3.146 ms
5 * * *
6 137.221.65.43 (137.221.65.43) 51.266 ms 51.230 ms 51.221 ms
7 137.221.73.32 (137.221.73.32) 51.051 ms 51.063 ms 51.185 ms
8 * * *
9 xe-0-0-1.brm.cor0.noanet.net (64.184.134.30) 58.062 ms 58.031 ms 58.118 ms
10 1-1-24.chj-mpls0.noanet.net (64.184.134.209) 57.693 ms 71.057 ms 70.886 ms
11 bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net (66.119.193.242) 58.362 ms 58.261 ms 58.354 ms
12 64.146.233.106 (64.146.233.106) 58.537 ms 58.502 ms 58.529 ms
13 64.146.233.226 (64.146.233.226) 60.334 ms 60.838 ms 59.575 ms
14 * * *
15 * * *
21/07/2018 15:01:10 UTC
--------------------
PING:
PING 64.184.151.9 (64.184.151.9) 56(84) bytes of data.
--- 64.184.151.9 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3008ms
21/07/2018 15:01:10 UTC
--------------------
PING:
PING 64.184.151.9 (64.184.151.9) 56(84) bytes of data.
--- 64.184.151.9 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
21/07/2018 15:01:10 UTC
--------------------
MTR:
Start: Sat Jul 21 15:01:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.8 0.0
2.|-- 37.244.22.3 0.0% 10 0.5 0.8 0.5 1.5 0.0
3.|-- 24.105.30.148 0.0% 10 1.0 1.1 0.9 1.7 0.0
4.|-- 137.221.66.4 0.0% 10 1.4 3.2 1.4 18.3 5.3
5.|-- 137.221.68.72 0.0% 10 3.7 2.6 1.3 11.7 3.2
6.|-- 137.221.65.7 0.0% 10 8.4 9.4 8.4 17.6 2.9
7.|-- 137.221.65.41 0.0% 10 25.8 27.5 25.7 42.8 5.4
8.|-- 137.221.73.32 0.0% 10 25.5 25.7 25.4 26.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- xe-0-0-1.brm.cor0.noanet.net 0.0% 10 33.1 33.4 33.1 34.0 0.0
11.|-- 1-1-24.chj-mpls0.noanet.net 0.0% 10 61.6 35.7 32.7 61.6 9.1
12.|-- bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net 0.0% 10 33.0 33.0 32.9 33.2 0.0
13.|-- 64.146.233.106 0.0% 10 33.0 33.3 33.0 33.6 0.0
14.|-- 64.146.233.226 0.0% 10 34.2 34.2 34.1 34.3 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21/07/2018 15:01:10 UTC
--------------------
MTR:
Start: Sat Jul 21 15:01:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 1.3 0.0
2.|-- 37.244.23.2 0.0% 10 0.6 0.9 0.5 1.6 0.0
3.|-- 24.105.62.146 0.0% 10 2.1 3.0 1.2 17.0 4.9
4.|-- 137.221.66.12 0.0% 10 3.2 2.7 2.5 3.2 0.0
5.|-- 137.221.69.72 0.0% 10 2.4 2.5 2.3 3.0 0.0
6.|-- 137.221.65.43 0.0% 10 51.1 51.2 51.0 52.1 0.0
7.|-- 137.221.73.32 0.0% 10 50.8 51.0 50.7 51.9 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- xe-0-0-1.brm.cor0.noanet.net 0.0% 10 57.9 58.3 57.9 59.5 0.3
10.|-- 1-1-24.chj-mpls0.noanet.net 0.0% 10 57.6 58.4 57.5 65.6 2.5
11.|-- bentonpud-cust.ge-2-2-8.505.oly-cor1.noanet.net 0.0% 10 58.2 58.4 58.1 59.1 0.0
12.|-- 64.146.233.106 0.0% 10 59.2 58.8 58.3 59.6 0.0
13.|-- 64.146.233.226 0.0% 10 59.4 59.7 59.4 60.6 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21/07/2018 15:01:10 UTC
--------------------Central Florida Spectrum here. This started last night for me. Only game this happens to. I went from a 65ms ping constantly, to 180, and it is extremely noticeable (not just a reporting thing, you can feel it heavily in game).
The weird thing is that it is a steady 180ms and not accompanied by packet loss or drops. The MTRs look good all the way from me to Blizzard and back though, which makes me think blizz has some type of localized network issue.
TRACEROUTE:
traceroute to 142.197.125.187 (142.197.125.187), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.133 ms 2.105 ms 2.103 ms
2 37.244.22.3 (37.244.22.3) 2.102 ms 2.102 ms 2.103 ms
3 24.105.30.152 (24.105.30.152) 2.306 ms 2.311 ms 2.370 ms
4 137.221.66.2 (137.221.66.2) 2.679 ms 2.731 ms 2.794 ms
5 137.221.68.66 (137.221.68.66) 2.689 ms 2.692 ms 2.692 ms
6 137.221.68.32 (137.221.68.32) 2.447 ms 1.000 ms 1.276 ms
7 ae34.pr1.lax10.tbone.rr.com (66.109.9.160) 0.944 ms 0.920 ms 0.905 ms
8 bu-ether27.tustca4200w-bcr00.tbone.rr.com (107.14.19.57) 64.219 ms 63.640 ms 63.610 ms
9 bu-ether16.dllstx976iw-bcr00.tbone.rr.com (66.109.6.1) 64.008 ms 64.011 ms 63.509 ms
10 bu-ether34.atlngamq46w-bcr00.tbone.rr.com (107.14.19.48) 60.193 ms 60.220 ms 60.222 ms
11 bu-ether11.tamsflde20w-bcr00.tbone.rr.com (66.109.1.71) 61.866 ms 60.752 ms 60.723 ms
12 so-0-0-2.ar1.cdp01.tbone.rr.com (66.109.6.97) 66.535 ms 66.163 ms 66.145 ms
13 hun0-3-0-7.tamp20-car1.bhn.net (72.31.3.79) 65.345 ms 63.670 ms 63.634 ms
14 ten0-13-0-0.orld71-CAR1.bhn.net (71.44.1.209) 63.457 ms 61.870 ms 61.851 ms
15 hun-0-6-0-0-orld01-ser1.bhn.net (72.31.188.188) 61.218 ms 61.132 ms 61.117 ms
22/07/2018 13:22:34 UTC
--------------------
TRACEROUTE:
traceroute to 142.197.125.187 (142.197.125.187), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.284 ms 0.273 ms 0.272 ms
2 37.244.23.2 (37.244.23.2) 1.320 ms 1.346 ms 1.347 ms
3 24.105.62.150 (24.105.62.150) 1.408 ms 1.417 ms 1.464 ms
4 137.221.66.14 (137.221.66.14) 2.227 ms 2.228 ms 2.303 ms
5 137.221.69.68 (137.221.69.68) 2.180 ms 2.194 ms 2.196 ms
6 137.221.69.32 (137.221.69.32) 1.717 ms 1.713 ms 1.684 ms
7 66.109.9.148 (66.109.9.148) 0.984 ms 1.283 ms 1.264 ms
8 bu-ether19.chcgildt87w-bcr00.tbone.rr.com (107.14.17.193) 52.675 ms 52.186 ms 52.162 ms
9 66.109.5.137 (66.109.5.137) 51.515 ms 51.518 ms 51.514 ms
10 bu-ether13.dllstx976iw-bcr00.tbone.rr.com (66.109.6.22) 50.103 ms 50.101 ms 49.582 ms
11 bu-ether11.tamsflde20w-bcr00.tbone.rr.com (66.109.1.71) 47.774 ms 46.791 ms 46.764 ms
12 so-0-0-2.ar1.cdp01.tbone.rr.com (66.109.6.97) 48.502 ms 51.899 ms 51.880 ms
13 hun0-3-0-7.tamp20-car2.bhn.net (72.31.3.137) 51.869 ms 51.865 ms *
14 * * *
15 hun-0-6-0-0-orld01-ser2.bhn.net (72.31.188.216) 51.825 ms 51.822 ms 51.819 ms
22/07/2018 13:22:34 UTC
--------------------
MTR:
Start: Sun Jul 22 13:22:34 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 1.7 0.3
2.|-- 37.244.23.2 0.0% 10 1.3 0.8 0.5 1.6 0.0
3.|-- 24.105.62.150 0.0% 10 1.3 1.3 1.0 1.8 0.0
4.|-- 137.221.66.14 0.0% 10 1.9 2.1 1.9 2.4 0.0
5.|-- 137.221.69.68 0.0% 10 1.8 2.0 1.8 2.7 0.0
6.|-- 137.221.69.32 0.0% 10 1.7 2.6 1.7 9.1 2.3
7.|-- 66.109.9.148 0.0% 10 1.0 1.5 1.0 3.4 0.6
8.|-- bu-ether19.chcgildt87w-bcr00.tbone.rr.com 0.0% 10 51.4 50.3 46.7 54.2 2.4
9.|-- 66.109.5.137 0.0% 10 47.8 49.4 46.2 52.3 2.1
10.|-- bu-ether13.dllstx976iw-bcr00.tbone.rr.com 0.0% 10 52.0 49.3 45.4 52.5 2.4
11.|-- bu-ether11.tamsflde20w-bcr00.tbone.rr.com 0.0% 10 47.3 48.2 45.4 51.4 2.1
12.|-- so-0-0-2.ar1.cdp01.tbone.rr.com 0.0% 10 47.9 48.3 47.5 48.9 0.0
13.|-- hun0-3-0-7.tamp20-car2.bhn.net 0.0% 10 50.0 50.3 49.3 51.1 0.3
14.|-- ten0-4-0-6.ORLD71-CAR2.bhn.net 0.0% 10 52.9 52.1 51.1 53.0 0.3
15.|-- hun-0-6-0-0-orld01-ser2.bhn.net 0.0% 10 49.3 49.5 49.2 50.1 0.0
16.|-- 72-31-216-225.net.bhntampa.com 0.0% 10 48.6 48.8 48.6 49.0 0.0
17.|-- 142-197-125-187.res.bhn.net 0.0% 10 57.8 56.9 55.6 57.8 0.3
22/07/2018 13:22:34 UTC
--------------------
MTR:
Start: Sun Jul 22 13:22:34 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 37.244.22.3 0.0% 10 2.8 0.8 0.5 2.8 0.7
3.|-- 24.105.30.152 0.0% 10 1.1 1.0 0.9 1.1 0.0
4.|-- 137.221.66.2 0.0% 10 1.9 1.5 1.3 1.9 0.0
5.|-- 137.221.68.66 0.0% 10 1.4 1.5 1.3 2.1 0.0
6.|-- 137.221.68.32 0.0% 10 1.3 1.7 1.1 6.9 1.8
7.|-- ae34.pr1.lax10.tbone.rr.com 0.0% 10 0.9 2.4 0.9 14.6 4.2
8.|-- bu-ether27.tustca4200w-bcr00.tbone.rr.com 0.0% 10 59.2 60.4 57.7 64.4 2.4
9.|-- bu-ether16.dllstx976iw-bcr00.tbone.rr.com 0.0% 10 63.7 61.1 57.1 63.8 2.3
10.|-- bu-ether34.atlngamq46w-bcr00.tbone.rr.com 0.0% 10 57.4 60.6 57.3 64.8 2.4
11.|-- bu-ether11.tamsflde20w-bcr00.tbone.rr.com 0.0% 10 64.3 61.2 57.9 64.4 2.2
12.|-- so-0-0-2.ar1.cdp01.tbone.rr.com 0.0% 10 59.9 59.4 58.7 60.2 0.0
13.|-- hun0-3-0-7.tamp20-car1.bhn.net 0.0% 10 64.3 64.6 63.5 65.5 0.3
14.|-- ten0-13-0-0.orld71-CAR1.bhn.net 0.0% 10 63.5 62.5 61.7 63.5 0.0
15.|-- hun-0-6-0-0-orld01-ser1.bhn.net 0.0% 10 61.3 61.2 61.1 61.3 0.0
16.|-- 72-31-216-223.net.bhntampa.com 0.0% 10 62.8 62.7 62.6 63.1 0.0
17.|-- 142-197-125-187.res.bhn.net 0.0% 10 68.7 68.1 67.4 69.1 0.3
22/07/2018 13:22:34 UTC
--------------------Stinkywhispr,
There is really not a ton going on in your MSinfo. Does your router have any quality of service settings or anything like that? Have you updated your router firmware yet? For information on updating your router’s firmware, you can look the make/model up online or contact the manufacturer.
You can try logging into the router’s firewall and consulting it’s manual/online resources for looking for these services:
- Quality of Service (QoS) - Disable this
- Universal Plug and Play (UPnP) - Test with this Disabled
If neither works, I’d like to get information on your router make/model and modem make/model.
So first off let me say thanks for really sticking this one out lol I really do appreciate it. OK, so I have previously, on more than one occasion, connected directly to my modem and i get identical conditions. That said it is a Linksys EA6350 with the latest firmware and I did try disabling Upnp and it didn’t really seem to change anything. Modem is an Arris tm1602 provided by my isp which is charter/spectrum. Thanks again…
Same exact problem as stinkywhispr, haven’t played for 2 weeks because of it
Every other game I play is fine except OW
Stinkywhispr,
I did some more digging on this, and from what I’m seeing on my end, your ping is averaging in the 90s more often than the 130+ you’re talking about here. Have things been better lately? When you ran that WinMTR, were you actively having some of the high latency you were talking about? As far as we can tell none of the evidence we’ve got so far explains the behavior you’re reporting here, which is why I’m kind of stuck. Just to be clear here, it’s not that I don’t trust your reports, I just lack the evidence to help you make an informed decision about what to do about it.
I’ve been running a monologue in a thread on the EU forums, where I’ve been blackbox troubleshooting a latency issue a lot of people have been having. It appears the cause is a routing issue that leads to asymmetric routing in one of the AM data centers. If there’s something similar here, it will only show up in a traceroute from the client to the server, not the other way around.
Good thought, but for what I just did I used internal telemetry which tracks data the game client reports both to the player and us. Our looking glass test only tests from the authentication server rather than the play servers as many of those are cloud based. It’s not particularly useful for this problem unfortunately.
When you say cloud-based, you mean private cloud right? Or aren’t your game servers colocated at eq?
Oh, I’m kind of unsure if anyone has seen my monologue on the EU forums. Do you have any way to see if anyone is following up on it?
IIRC it’s mostly if not all AWS cloud. I don’t do direct interaction with the EU forums typically, but if you’re noticing a regional issue and the forums aren’t getting any traction, I recommend submitting a ticket to the EU support staff with whatever data you’ve gathered so we can give it a look and make appropriate escalations to our network team if necessary. Keep in mind we tend to need a decent amount of data to do this, so if you have other posters on your thread, make sure they’re gathering the information we need as well like winMTR tests during the problem, etc.
I can’t really address this fully in this thread as we’re focusing mostly on the OP here, but I wanted to clarify that particular point about our using the cloud for hosting games. That’s part of why it’s so important to follow our winMTR steps exactly for Overwatch - if it’s run on the wrong IP address, we get junk data from it.
Yeah sorry let me explain. Solo games and training range seem to be like 93-105 ping range when they used to be 50-70. Seemingly any time I try to play with any size group is when is worsens to 130-140. Not that I mind solo that much but I miss my friends and still the relationship changed from 50-70 to now mid to high nineties in the best case and 130 ish in group cases and even occasionally on my own. Im assuming when i solo i tend to get west servers and when i group with my filthy Canadian friends lol i get east servers. Sorry if i was unclear about any of that. 93-105 isnt unplayable its just i can feel the difference in response as i main mccree. Just feels less fun and certainly less competitive.
Gotcha,
In that case, it does sound like you’re getting prioritized over to the central or east servers while in a group. Can you do that WinMTR with the IP from a game with your friends and while the ping is high? The server you tested earlier was the West Coast server, which is consistent with your normal ping. That’s why this whole thing has been more confusing than it should have been. Sorry 'bout that, we should have caught this earlier!
Fair warning, there may not be anything we or you can do to optimize your connection while you’re playing with friends. Still, let’s give it a look and see if we can find anything one of us can act on. There’s a reason you’re defaulting to the west coast servers while solo - those are the best servers for you connection-wise.
Yeah I mean I get that lol and I’m glad I default to the west I just don’t know why it used to be so much better. I feel bad for as much time as I’ve taken I was mostly just reaching out to see if there was something obvious someone saw. Yeah whenever I hop in a group next ill WinMTR it. If nothing comes of that you’re probably better off helping other folks and ill cry to my isp one more time. Thanks and ill try to post that asap but havent actually played with anyone in like 2 weeks:(
Understood, just send it our way when you get the chance. Replying back so you can post in the thread without editing things. Good luck until then!
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| Brun - 0 | 244 | 244 | 0 | 0 | 3 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| host-69-144-131-249.bzm-mt.client.bresnannet - 1 | 240 | 239 | 0 | 13 | 30 | 15 |
| host-69-144-24-28.lar-wy.client.bresnannet - 0 | 244 | 244 | 7 | 10 | 30 | 8 |
| host-69-144-47-49.sal-co.client.bresnannet - 1 | 240 | 239 | 0 | 50 | 80 | 56 |
| 96-34-76-114.static.unas.sc.chartercom - 1 | 240 | 239 | 0 | 50 | 78 | 48 |
| 69.145.174.134 - 0 | 243 | 243 | 46 | 53 | 72 | 54 |
| bbr02snjsca-bue-2.snjs.ca.chartercom - 1 | 240 | 239 | 0 | 81 | 101 | 87 |
| prr01snjsca-bue-6.snjs.ca.chartercom - 0 | 243 | 243 | 73 | 77 | 94 | 74 |
| eqix-ix-sv1.blizzardcom - 1 | 240 | 239 | 0 | 77 | 96 | 82 |
| ae1-br01-eqsv5.blizzardonlinenet - 0 | 243 | 243 | 74 | 79 | 111 | 84 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
My ping in game was over 200 the entire time.