[Spectrum] Higher than normal Latency

Support Technical Support
82

In southeast Wisconsin with spectrum playing on Stormrage still having issues updated tests

WinMTR: 15 min run while doing world quests

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 901 901 0 0 8 0
142.254.153.117 0 901 901 2 10 24 8
ae63.nprrwi0101h.midwest.rr.com 0 901 901 14 49 375 26
be52.milzwift01r.midwest.rr.com 0 901 901 7 16 36 18
bu-ether18.chctilwc00w-bcr00.tbone.rr.com 0 901 901 10 17 35 20
bu-ether11.chcgildt87w-bcr00.tbone.rr.com 0 901 901 11 18 35 16
66.109.5.225 0 901 901 8 17 84 11
66.109.9.149 0 901 901 10 15 59 14
ae1-br01-eqch2.as57976.net 0 901 901 6 19 645 15
be1-pe01-eqch2.as57976.net 0 901 901 58 63 79 62
chi-eqch2-ia-bons-02.as57976.net 0 901 901 58 64 83 64
24.105.62.129 0 901 901 57 64 82 62

Looking Glass:
TRACEROUTE:
traceroute to 184.59.37.92 (184.59.37.92), 15 hops max, 60 byte packets
1 Blizzard Blizzard 7.416 ms 7.459 ms 7.460 ms Blizzard(24.105.18.3) 7.487 ms 7.508 ms 7.532 ms
3 137.221.105.16 (137.221.105.16) 7.447 ms 7.482 ms 7.522 ms
4 137.221.66.22 (137.221.66.22) 7.462 ms 7.483 ms 7.487 ms
5 137.221.83.68 (137.221.83.68) 30.204 ms 30.224 ms 30.231 ms
6 137.221.65.68 (137.221.65.68) 19.213 ms 12.898 ms 12.905 ms
7 137.221.65.1 (137.221.65.1) 12.906 ms 13.067 ms 12.791 ms
8 137.221.65.7 (137.221.65.7) 12.933 ms 12.944 ms 13.010 ms
9 137.221.70.32 (137.221.70.32) 12.885 ms 12.900 ms 12.614 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. (66.109.9.172) 12.450 ms 27.092 ms 24.196 ms
11 66.109.5.132 (66.109.5.132) 57.621 ms 57.630 ms 57.570 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. (66.109.6.9) 55.367 ms 55.216 ms 55.209 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. (66.109.6.15) 55.713 ms 56.153 ms 56.190 ms
14 66.109.6.205 (66.109.6.205) 52.621 ms 59.788 ms 52.305 ms
15 ae1.nprrwi0102h.midwest.rr. (65.31.113.123) 71.193 ms 68.389 ms 66.531 ms

21/02/2019 00:26:21 UTC

TRACEROUTE:
traceroute to 184.59.37.92 (184.59.37.92), 15 hops max, 60 byte packets
1 Blizzard Blizzard 6.018 ms 5.947 ms 5.946 ms Blizzard(24.105.18.3) 7.233 ms 7.858 ms 7.869 ms
3 137.221.105.16 (137.221.105.16) 6.956 ms 7.064 ms 7.071 ms
4 137.221.66.22 (137.221.66.22) 6.968 ms 7.003 ms 7.053 ms
5 137.221.83.68 (137.221.83.68) 18.669 ms 18.709 ms 18.732 ms
6 137.221.65.68 (137.221.65.68) 18.410 ms 13.494 ms 13.471 ms
7 137.221.65.1 (137.221.65.1) 13.819 ms 13.809 ms 13.811 ms
8 137.221.65.7 (137.221.65.7) 13.823 ms 13.823 ms 13.825 ms
9 137.221.70.32 (137.221.70.32) 13.132 ms 13.513 ms 13.487 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. (66.109.9.172) 12.703 ms 12.419 ms 12.550 ms
11 66.109.5.132 (66.109.5.132) 56.843 ms 56.335 ms 53.861 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. (66.109.6.9) 51.256 ms 51.166 ms 50.168 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. (66.109.6.15) 50.615 ms 50.619 ms 50.269 ms
14 66.109.6.205 (66.109.6.205) 54.502 ms 54.043 ms 54.034 ms
15 ae1.nprrwi0102h.midwest.rr. (65.31.113.123) 75.563 ms 75.220 ms 69.814 ms

21/02/2019 00:26:21 UTC

TRACEROUTE:
traceroute to 184.59.37.92 (184.59.37.92), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.399 ms 0.418 ms 0.431 ms Blizzard(24.105.18.3) 1.436 ms 1.507 ms 1.554 ms
3 137.221.105.16 (137.221.105.16) 1.463 ms 1.511 ms 1.552 ms
4 137.221.66.22 (137.221.66.22) 1.467 ms 1.513 ms 1.534 ms
5 137.221.83.68 (137.221.83.68) 13.206 ms 13.234 ms 13.244 ms
6 137.221.65.68 (137.221.65.68) 12.938 ms 13.108 ms 13.050 ms
7 137.221.65.1 (137.221.65.1) 12.987 ms 13.014 ms 13.021 ms
8 137.221.65.7 (137.221.65.7) 13.030 ms 13.035 ms 13.066 ms
9 137.221.70.32 (137.221.70.32) 12.794 ms 13.613 ms 13.127 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. (66.109.9.172) 21.453 ms 12.827 ms 12.792 ms
11 66.109.5.132 (66.109.5.132) 53.434 ms 52.888 ms 51.413 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. (66.109.6.9) 57.101 ms 56.381 ms 56.367 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. (66.109.6.15) 56.810 ms 56.834 ms 56.242 ms
14 66.109.6.205 (66.109.6.205) 52.718 ms 52.264 ms 52.535 ms
15 ae1.nprrwi0102h.midwest.rr. (65.31.113.123) 71.540 ms 73.694 ms 73.704 ms

21/02/2019 00:26:21 UTC

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

— 184.59.37.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3007ms

21/02/2019 00:26:21 UTC

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

— 184.59.37.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

21/02/2019 00:26:21 UTC

TRACEROUTE:
traceroute to 184.59.37.92 (184.59.37.92), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.279 ms 0.304 ms 0.327 ms Blizzard(24.105.18.3) 1.104 ms 1.162 ms 1.214 ms
3 137.221.105.16 (137.221.105.16) 1.105 ms 1.160 ms 1.211 ms
4 137.221.66.22 (137.221.66.22) 1.140 ms 1.162 ms 1.186 ms
5 137.221.83.68 (137.221.83.68) 12.869 ms 12.883 ms 12.896 ms
6 137.221.65.68 (137.221.65.68) 12.786 ms 12.934 ms 12.929 ms
7 137.221.65.1 (137.221.65.1) 12.721 ms 12.961 ms 12.949 ms
8 137.221.65.7 (137.221.65.7) 12.860 ms 12.884 ms 12.892 ms
9 137.221.70.32 (137.221.70.32) 12.651 ms 12.637 ms 12.637 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. (66.109.9.172) 33.730 ms 24.764 ms 24.263 ms
11 66.109.5.132 (66.109.5.132) 51.438 ms 51.031 ms 49.626 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. (66.109.6.9) 55.397 ms 54.495 ms 54.515 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. (66.109.6.15) 54.896 ms 54.927 ms 54.932 ms
14 66.109.6.205 (66.109.6.205) 59.530 ms 58.509 ms 58.475 ms
15 ae1.nprrwi0102h.midwest.rr. (65.31.113.123) 68.626 ms 69.703 ms 69.715 ms

21/02/2019 00:26:26 UTC

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

— 184.59.37.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3003ms

21/02/2019 00:26:22 UTC

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

— 184.59.37.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

21/02/2019 00:26:26 UTC

MTR:
Start: Thu Feb 21 00:26:21 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.5 0.0 Blizzard 0.0% 10 19.2 3.7 0.5 19.2 6.3
3.|-- 137.221.105.16 0.0% 10 0.7 0.7 0.6 0.9 0.0
4.|-- 137.221.66.22 0.0% 10 0.9 0.8 0.5 1.8 0.0
5.|-- 137.221.83.68 0.0% 10 13.4 13.6 12.6 19.6 2.0
6.|-- 137.221.65.68 0.0% 10 13.3 13.1 12.8 13.9 0.0
7.|-- 137.221.65.1 0.0% 10 14.2 19.2 12.7 73.8 19.2
8.|-- 137.221.65.7 0.0% 10 12.9 13.0 12.7 13.3 0.0
9.|-- 137.221.70.32 0.0% 10 12.8 12.8 12.6 12.9 0.0
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. 0.0% 10 12.6 12.7 12.5 13.0 0.0
11.|-- 66.109.5.132 0.0% 10 57.4 54.4 51.5 57.4 2.0
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. 0.0% 10 49.9 54.0 49.9 57.2 2.7
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. 0.0% 10 54.7 54.0 50.7 57.4 2.1
14.|-- 66.109.6.205 0.0% 10 55.7 55.8 52.0 59.7 2.2
15.|-- ae1.nprrwi0102h.midwest.rr. 0.0% 10 289.2 90.3 58.7 289.2 70.0
16.|-- ae2.nprrwi0105m.wi.rr. 0.0% 10 53.8 53.6 53.4 53.8 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/02/2019 00:26:21 UTC

MTR:
Start: Thu Feb 21 00:26:21 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0 Blizzard 0.0% 10 0.6 0.7 0.5 0.8 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.7 0.6 0.9 0.0
5.|-- 137.221.83.68 0.0% 10 13.1 13.3 12.8 15.6 0.6
6.|-- 137.221.65.68 0.0% 10 13.5 14.1 12.8 19.9 2.1
7.|-- 137.221.65.1 0.0% 10 13.1 13.3 12.8 16.9 1.1
8.|-- 137.221.65.7 0.0% 10 13.0 16.3 12.9 43.0 9.4
9.|-- 137.221.70.32 0.0% 10 12.6 12.8 12.6 12.9 0.0
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. 0.0% 10 12.8 15.0 12.5 23.5 4.1
11.|-- 66.109.5.132 0.0% 10 52.9 52.5 49.7 55.7 2.2
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. 0.0% 10 53.4 54.4 52.2 57.5 2.0
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. 0.0% 10 50.3 54.4 50.3 57.5 2.7
14.|-- 66.109.6.205 0.0% 10 59.3 56.1 52.4 59.3 2.4
15.|-- ae1.nprrwi0102h.midwest.rr. 0.0% 10 332.8 94.4 62.2 332.8 83.8
16.|-- ae2.nprrwi0105m.wi.rr. 0.0% 10 53.4 53.6 53.4 54.8 0.3
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/02/2019 00:26:21 UTC

MTR:
Start: Thu Feb 21 00:26:21 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.2 2.6 0.5 Blizzard 0.0% 10 0.6 0.6 0.5 0.8 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.6 0.7 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.7 0.6 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 12.8 13.2 12.8 15.6 0.8
6.|-- 137.221.65.68 0.0% 10 12.9 15.4 12.7 36.9 7.5
7.|-- 137.221.65.1 0.0% 10 24.6 14.2 12.8 24.6 3.7
8.|-- 137.221.65.7 0.0% 10 12.8 12.9 12.8 13.0 0.0
9.|-- 137.221.70.32 0.0% 10 12.8 12.7 12.6 12.8 0.0
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. 0.0% 10 25.7 15.2 12.4 25.7 4.6
11.|-- 66.109.5.132 0.0% 10 55.9 53.3 50.0 57.5 2.6
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. 0.0% 10 56.5 53.6 50.2 57.3 2.3
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. 0.0% 10 53.4 55.2 52.4 57.7 1.9
14.|-- 66.109.6.205 0.0% 10 54.5 56.1 53.3 58.6 1.8
15.|-- ae1.nprrwi0102h.midwest.rr. 0.0% 10 65.8 85.0 65.2 231.9 51.8
16.|-- ae2.nprrwi0105m.wi.rr. 0.0% 10 53.3 53.5 53.3 54.4 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/02/2019 00:26:21 UTC

MTR:
Start: Thu Feb 21 00:26:26 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.5 0.0 Blizzard 0.0% 10 0.5 2.5 0.5 18.7 5.7
3.|-- 137.221.105.16 0.0% 10 0.7 0.7 0.5 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 0.5 1.0 0.5 3.9 1.0
5.|-- 137.221.83.68 0.0% 10 12.8 13.8 12.8 19.4 1.9
6.|-- 137.221.65.68 0.0% 10 12.9 12.9 12.8 13.3 0.0
7.|-- 137.221.65.1 0.0% 10 12.9 25.0 12.8 73.8 25.2
8.|-- 137.221.65.7 0.0% 10 13.0 14.5 12.7 28.3 4.8
9.|-- 137.221.70.32 0.0% 10 12.6 12.7 12.5 13.4 0.0
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. 0.0% 10 12.7 12.7 12.5 12.8 0.0
11.|-- 66.109.5.132 0.0% 10 55.0 54.3 50.9 57.4 2.4
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. 0.0% 10 55.5 52.9 49.8 55.5 1.9
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. 0.0% 10 52.3 54.5 51.2 57.4 2.5
14.|-- 66.109.6.205 0.0% 10 53.4 55.5 52.2 58.9 2.4
15.|-- ae1.nprrwi0102h.midwest.rr. 0.0% 10 64.4 91.3 64.4 289.2 69.6
16.|-- ae2.nprrwi0105m.wi.rr. 0.0% 10 53.4 53.4 53.3 53.8 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/02/2019 00:26:26 UTC

REMOVED COM AT THE END OF URLS BECAUSE I CANT POST LINKS

83

Having same issues in northern KY with spectrum normal latency has always been 30-35 now 80-85 ever since last Thursday

84

NO change, actually have higher ms tonight…up another 5-8 consistent.

1 Like
85

I won’t post another log as I’ve posted a few already. Getting a little impatient here… Hard to go from my normal 25ms to 75ms to 85ms and not notice a difference. Seems to be getting higher…

1 Like
86

I still have high ping and this is my WinMTR from a few minutes ago:

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 39 39 0 0 5 0
142.254.155.37 0 39 39 4 7 12 4
24.164.105.241 0 39 39 19 74 566 23
be20.sgvlohaj01r.midwest.rr.com 0 39 39 7 9 13 9
be11.clevohek02r.midwest.rr.com 0 39 39 9 13 19 10
be25.clevohek01r.midwest.rr.com 0 39 39 9 13 22 9
so-7-1-0.ar0.dca10.tbone.rr.com 0 39 39 16 20 25 21
66.109.3.24 0 39 39 18 22 28 23
66.109.5.117 0 39 39 16 17 21 17
66.109.9.155 0 39 39 17 18 24 17
ae1-br01-eqdc2.as57976.net 0 39 39 77 80 102 80
et-0-0-2-br01-eqch2.as57976.net 0 39 39 29 34 88 31
be1-pe01-eqch2.as57976.net 0 39 39 79 81 83 82
24.105.62.129 0 39 39 80 81 84 81
87

Same here. Yesterday afternoon I was lucky to get under 90/80. Getting rather impatient here myself.

88

Apparently blizzard really isn’t worried as long as it doesn’t affect payment servers

89

3 days ago @blizzarscs reported they were PRETTY sure they find the problems and were reaching out to parties involved…well it’s been 7 days now total and nothing…

2 Likes
90

Yeah, getting hard to remain patient.

91

Well is this Blizzard’s fault? Or do we need to contact our ISP’s and tell them about it? It sounds like Blizzard is trying to do that for us but maybe I’m misunderstanding.

92

Sorry for the confusion Zuvykree. I am able to log in. I meant that I hadn’t had a chance to log in since the weekend so that’s why I was asking if the issue was still ongoing. Because I’m dealing with the unusually high latency as a northern KY spectrum user as well.

93

I have also been experiencing a stable 50ms increase with extreme spikes to over 3 seconds with more frequent spikes to 700-900ms. I am on Spectrum, Former Time Warner, in New York connecting to Mal’Ganis.

I posted an issue to the Blizzard Technical support forums with my ping plots.

It seems to be in the same place every time for me where a Charter backbone leads into Blizzards own IP address space.

It doesn’t seem to be an issue with my house’s network infrastructure, my local last mile infrastructure or Spectrum (Former Time Warner’s) immediate infrastructure.

94

I called Spectrum about it. They said there is no issue on my end, and since I am not having any trouble with any other games or connections, they said it was probably Blizzard :frowning:

1 Like
95

And here I thought I was going crazy…

I’m a victim as well.

2 Likes
96

Here is what I got from spectrum when I gave them this form to reference

Should you like us to address your issues, we’d be happy to. However, we cannot read through threads without IP addresses or account numbers to assist. Again, we are always here to help. ^JLM

97

BTW @blizzardcs it took me 10 min to get ahold of someone at Spectrum to send this info to and you are working on day 7 with no answers

98

The level of customer service you’re getting isn’t going to help most likely. This is apparently a routing issue with a peering partner outside of their network, it’ll have to be escalated to someone higher up than that guy that sends a guy to your house to climb the pole in your backyard. So people will probably have to start bugging Spectrum publicly on Twitter to get them to escalate to the proper people.

Usually when you get a bunch of people bugging a company publicly about a problem it lights a fire under their butt. Bad PR etc., so get your pitchforks and thread links ready!!!

It is pretty sad that it’s a week or more now and we’ve got like one update if you don’t count the update that was the same as the first one…

99

I know I am repeating myself from an earlier post but it is NOT just Spectrum customers that are having the issue. I am with AT&T and if you check back on the posts you will see there are others with different providers having the issue.

100

Can we please get an update about this issue? @Zhyxrn

101

I don’t think this is just spectrum users though, and if it isn’t, then this isn’t a spectrum issue, it is a blizzard issue, and it is just getting worse. I just spent most of my game time trying to kill stuff with 125/85, it is nonsense, they need to fix it.

2 Likes