Just wanting to add my experience with this. I normally sit at 21-22ms solid being in Northern Ohio. Last couple of days it has been 50 higher than that consistently. Not spikes, not crazy high lag without the ms, just…higher. I’ve done a few of the tracert, mtr things and they all come back that it is the last hop (I think that is the term) seemingly being the issue.
edit: I believe I am also on a Chicago based server as well
edit2causetired: Spectrum as well
I am using Spectrum and live in KY, my latency is 38, but then will spike to 500-600 and then return back to 38-40. I have seen 1200 latency once or twice since Friday night when this started. I am on Dalaran server, and during raid Friday night it started and hasn’t let up.
Another guild member who lives in Northern Ohio, same issue. 80ms, normally 30
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 142.254.148.69 | 0 | 961 | 961 | 5 | 8 | 34 | 9 |
| agg63.grspoh0401h.midwest.rr.com | 1 | 957 | 956 | 9 | 35 | 253 | 21 |
| agg77.clmkohpe02r.midwest.rr.com | 0 | 961 | 961 | 10 | 15 | 33 | 18 |
| be27.clmkohpe01r.midwest.rr.com | 0 | 961 | 961 | 10 | 15 | 30 | 21 |
| bu-ether15.chctilwc00w-bcr00.tbone.rr.com | 0 | 961 | 961 | 19 | 25 | 35 | 25 |
| bu-ether11.chcgildt87w-bcr00.tbone.rr.com | 0 | 961 | 961 | 20 | 25 | 39 | 29 |
| 66.109.5.225 | 0 | 961 | 961 | 15 | 26 | 102 | 24 |
| 66.109.9.149 | 0 | 961 | 961 | 15 | 22 | 64 | 23 |
| ae1-br01-eqch2.as57976.net | 0 | 961 | 961 | 15 | 26 | 244 | 20 |
| be1-pe01-eqch2.as57976.net | 0 | 961 | 961 | 65 | 70 | 88 | 69 |
| 24.105.62.129 | 0 | 961 | 961 | 65 | 70 | 87 | 70 |
Nat, do you happen to have a neighbor who a) plays WoW and b) uses a different ISP?
It would be useful to find out if this is a location issue or not.
If you’ve got a neighbor playing WoW on a different ISP and they’re experiencing elevated ping times as well, that would pretty much eliminate this as a “Spectrum” problem.
The fact that Spectrum/Charter/TWC is present in so many cities in the east may be skewing this a bit as far as “but it’s obvious that…” goes.
Spectrum is the only thing offered in my area lol at least worth getting in terms of price/speed
Im just seeing it more and more of the issue at hand considering multiple ppl in my guild on the chicago server who live in dif states showing higher consistent MS. in the 80’s
Father in-law 1/4 mile using spectrum on a different node, same server. His MS is exactly like mine. 85
Here is going to the US central for 15 mins just now.
WinMTR Statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.1.1 | 0 | 906 | 906 | 0 | 0 | 1 | 0 |
| 142.254.211.157 | 0 | 906 | 906 | 3 | 8 | 18 | 8 |
| agg63.cblsny1001h.northeast.rr.com | 1 | 902 | 901 | 12 | 39 | 306 | 25 |
| 24.58.51.248 | 0 | 906 | 906 | 6 | 10 | 24 | 9 |
| be26.albynyyf01r.northeast.rr.com | 1 | 902 | 901 | 8 | 13 | 25 | 14 |
| bu-ether16.nycmny837aw-bcr00.tbone.rr.com | 1 | 902 | 901 | 16 | 21 | 37 | 22 |
| 66.109.5.139 | 0 | 906 | 906 | 22 | 26 | 42 | 25 |
| 107.14.17.239 | 1 | 902 | 901 | 22 | 26 | 36 | 30 |
| 66.109.5.117 | 0 | 906 | 906 | 19 | 27 | 113 | 23 |
| 66.109.9.155 | 1 | 902 | 901 | 19 | 23 | 51 | 22 |
| ae1-br01-eqdc2.as57976.net | 1 | 902 | 901 | 83 | 87 | 239 | 85 |
| et-0-0-2-br01-eqch2.as57976.net | 0 | 902 | 902 | 34 | 45 | 4261 | 40 |
| be1-pe02-eqch2.as57976.net | 1 | 902 | 901 | 83 | 84 | 96 | 84 |
| 24.105.62.129 | 1 | 898 | 896 | 84 | 85 | 97 | 86 |
|66.109.9.155|1|902|901|19|23|51|22|
| --- | --- | --- | --- | --- | --- | --- | --- |
|ae1-br01-eqdc2.as57976.net|1|902|901|83|87|239|85|
|et-0-0-2-br01-eqch2.as57976.net|0|902|902|34|45|4261|40|
|be1-pe02-eqch2.as57976.net|1|902|901|83|84|96|84|
|24.105.62.129|1|898|896|84|85|97|86|
Okay, here’s the thing that I’m concerned about. 66.109.9.155 belongs to Charter Communications - part of Spectrum. But your three worst times come from two of the next three domains which are (inexplicably) GoDaddy domains and then that last one which is Blizzard, just a bit west of Wichita, Kansas.
The other one that’s got a high “worst” value looks like a leased backbone router belonging to Indiana Railroad - that’s just part of the infrastructure.
What I don’t get is that if you’re in the northeast and playing on east-coast servers, why would the Blizzard server be west of Wichita, Kansas and why is this all getting routed through three GoDaddy domains on the way unless those are also leased backbone routers.
This really looks like some sort of DNS corruption - something, somewhere has convinced DNS that the fastest route from A to B lies through C and D and E and F and G, waaaaaaay off the true fastest route.
Again, “Speed” is misleading in terms of what ISPs offer. If you know someone accessing WoW over DSL, that would be helpful.
Except for patch day, WoW uses very little bandwidth (what the ISPs mislabel speed and should be labeled capacity).
Ping is speed. Bandwidth is capacity.
DSL can get you decent ping but has limited capacity.
ANYONE you know locally connecting to WoW via anything OTHER than Spectrum would help narrow this down a bit.
Someone who lives in germantown 1.5 hrs from me using a dif cable company is gonna test when hes home…otherwise no other net here
And he just let me know hes at 40 which is his normal. Hudson cable vision.
Having the same issue here on the east coast with spectrum. Getting about 40ms higher ping than usual but it sometimes creeps up to over 100ms causing bad lag
Thanks for your reports and connection tests so far! We’re continuing to gather data, please continue to provide WinMTR tests while running the game for 5 minutes, and let’s start gathering Looking Glass Tests and what realm you’re currently playing on.
Please run the WinMTR test for both IPs and include the Looking Glass test.
Result from Kael’thas realm
traceroute to 72.231.162.124 (72.231.162.124), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.988 ms 0.979 ms 0.974 ms
2 24.105.18.131 (24.105.18.131) 2.678 ms 2.687 ms 2.697 ms
3 137.221.105.16 (137.221.105.16) 2.669 ms 2.678 ms 2.688 ms
4 137.221.66.22 (137.221.66.22) 2.675 ms 2.675 ms 2.677 ms
5 137.221.83.68 (137.221.83.68) 13.586 ms 13.589 ms 13.591 ms
6 137.221.65.68 (137.221.65.68) 22.044 ms 16.694 ms 16.667 ms
7 137.221.65.1 (137.221.65.1) 12.747 ms 13.043 ms 13.040 ms
8 137.221.65.7 (137.221.65.7) 13.105 ms 13.118 ms 13.117 ms
9 137.221.70.32 (137.221.70.32) 12.787 ms 12.773 ms 12.604 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. com (66.109.9.172) 16.369 ms 12.337 ms 12.327 ms
11 66.109.5.132 (66.109.5.132) 56.072 ms 56.975 ms 56.272 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. com (66.109.6.9) 50.178 ms 50.191 ms 50.171 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. com (66.109.6.15) 54.905 ms 54.474 ms 54.466 ms
14 66.109.6.73 (66.109.6.73) 70.215 ms 67.901 ms 68.182 ms
15 agg1.cblsny1002h.northeast.rr. com (24.58.51.233) 88.938 ms 88.521 ms 86.709 ms
TRACEROUTE:
traceroute to 72.231.162.124 (72.231.162.124), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.926 ms 3.941 ms 9.145 ms
2 24.105.18.131 (24.105.18.131) 9.791 ms 9.840 ms 9.864 ms
3 137.221.105.16 (137.221.105.16) 9.810 ms 9.823 ms 9.862 ms
4 137.221.66.22 (137.221.66.22) 11.979 ms 11.996 ms 12.006 ms
5 137.221.83.68 (137.221.83.68) 16.548 ms 16.560 ms 16.571 ms
6 137.221.65.68 (137.221.65.68) 16.490 ms 13.100 ms 13.103 ms
7 137.221.65.1 (137.221.65.1) 13.041 ms 12.889 ms 12.901 ms
8 137.221.65.7 (137.221.65.7) 13.018 ms 13.047 ms 14.229 ms
9 137.221.70.32 (137.221.70.32) 13.213 ms 15.525 ms 15.476 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. com (66.109.9.172) 13.518 ms 15.982 ms 15.475 ms
11 66.109.5.132 (66.109.5.132) 53.296 ms 52.729 ms 53.866 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. com (66.109.6.9) 55.669 ms 54.794 ms 54.777 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. com (66.109.6.15) 51.518 ms 57.647 ms 57.666 ms
14 66.109.6.73 (66.109.6.73) 65.882 ms 72.199 ms 72.177 ms
15 agg1.cblsny1002h.northeast.rr. com (24.58.51.233) 92.957 ms 89.423 ms 89.409 ms
TRACEROUTE:
traceroute to 72.231.162.124 (72.231.162.124), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.428 ms 0.452 ms 0.468 ms
2 24.105.18.131 (24.105.18.131) 1.707 ms 1.762 ms 1.784 ms
3 137.221.105.16 (137.221.105.16) 1.722 ms 1.731 ms 1.747 ms
4 137.221.66.22 (137.221.66.22) 1.539 ms 1.589 ms 1.604 ms
5 137.221.83.68 (137.221.83.68) 13.128 ms 13.168 ms 13.183 ms
6 137.221.65.68 (137.221.65.68) 12.897 ms 12.864 ms 12.863 ms
7 137.221.65.1 (137.221.65.1) 13.114 ms 13.161 ms 13.154 ms
8 137.221.65.7 (137.221.65.7) 12.731 ms 13.160 ms 13.166 ms
9 137.221.70.32 (137.221.70.32) 12.679 ms 12.708 ms 12.719 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. com (66.109.9.172) 12.778 ms 13.114 ms 12.498 ms
11 66.109.5.132 (66.109.5.132) 55.050 ms 54.383 ms 53.285 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. com (66.109.6.9) 54.964 ms 54.989 ms 54.080 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. com (66.109.6.15) 50.973 ms 50.686 ms 50.692 ms
14 66.109.6.73 (66.109.6.73) 66.619 ms 66.648 ms 66.665 ms
15 agg1.cblsny1002h.northeast.rr. com (24.58.51.233) 90.844 ms 90.242 ms 82.929 ms
PING:
PING 72.231.162.124 (72.231.162.124) 56(84) bytes of data.
— 72.231.162.124 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3002ms
PING:
PING 72.231.162.124 (72.231.162.124) 56(84) bytes of data.
— 72.231.162.124 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3004ms
TRACEROUTE:
traceroute to 72.231.162.124 (72.231.162.124), 15 hops max, 60 byte packets
1 Blizzard Blizzard 11.102 ms 11.105 ms 11.112 ms
2 24.105.18.131 (24.105.18.131) 11.295 ms 11.333 ms 11.356 ms
3 137.221.105.16 (137.221.105.16) 11.247 ms 11.288 ms 11.326 ms
4 137.221.66.22 (137.221.66.22) 11.164 ms 11.165 ms 11.171 ms
5 137.221.83.68 (137.221.83.68) 21.688 ms 21.693 ms 21.711 ms
6 137.221.65.68 (137.221.65.68) 21.626 ms 19.713 ms 19.682 ms
7 137.221.65.1 (137.221.65.1) 19.122 ms 19.143 ms 19.145 ms
8 137.221.65.7 (137.221.65.7) 19.589 ms 19.619 ms 13.790 ms
9 137.221.70.32 (137.221.70.32) 13.533 ms 13.702 ms 13.715 ms
10 ge-11-0-0.pr0.sjc20.tbone.rr. com (66.109.9.172) 21.106 ms 21.111 ms 20.405 ms
11 66.109.5.132 (66.109.5.132) 52.912 ms 52.330 ms 52.294 ms
12 bu-ether12.snvacaid17w-bcr00.tbone.rr. com (66.109.6.9) 54.118 ms 54.037 ms 54.119 ms
13 bu-ether14.chcgildt87w-bcr00.tbone.rr. com (66.109.6.15) 50.740 ms 56.973 ms 56.934 ms
14 66.109.6.73 (66.109.6.73) 66.357 ms 66.162 ms 66.146 ms
15 agg1.cblsny1002h.northeast.rr. com (24.58.51.233) 85.548 ms 86.824 ms 86.884 ms
PING:
PING 72.231.162.124 (72.231.162.124) 56(84) bytes of data.
— 72.231.162.124 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
PING:
PING 72.231.162.124 (72.231.162.124) 56(84) bytes of data.
— 72.231.162.124 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3006ms
MTR:
Start: Sun Feb 17 22:50:57 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 3.1 0.3 22.9 7.1
2.|-- 24.105.18.131 0.0% 10 0.6 3.4 0.5 24.1 7.4
3.|-- 137.221.105.16 0.0% 10 0.8 0.9 0.5 3.1 0.7
4.|-- 137.221.66.22 0.0% 10 12.1 2.0 0.6 12.1 3.6
5.|-- 137.221.83.68 0.0% 10 13.0 16.3 12.7 32.7 6.2
6.|-- 137.221.65.68 0.0% 10 12.8 15.3 12.8 30.3 5.6
7.|-- 137.221.65.1 0.0% 10 13.0 18.8 12.8 44.0 12.4
8.|-- 137.221.65.7 0.0% 10 12.8 13.0 12.8 13.2 0.0
9.|-- 137.221.70.32 0.0% 10 12.7 12.8 12.6 14.0 0.3
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. com 0.0% 10 12.8 14.6 12.3 33.0 6.4
11.|-- 66.109.5.132 0.0% 10 51.2 53.0 50.3 57.2 2.1
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. com 0.0% 10 57.0 53.6 49.7 57.0 2.6
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. com 0.0% 10 50.9 53.5 50.0 57.6 2.3
14.|-- 66.109.6.73 0.0% 10 63.2 66.8 63.2 70.6 2.4
15.|-- agg1.cblsny1002h.northeast.rr. com 0.0% 10 75.3 104.5 75.3 212.7 40.7
16.|-- agg2.cblsny1001m.nyroc.rr. com 0.0% 10 76.6 76.8 76.6 77.5 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
MTR:
Start: Sun Feb 17 22:50:57 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.7 0.0
2.|-- 24.105.18.131 0.0% 10 0.8 0.8 0.5 1.5 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.8 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.8 0.6 2.0 0.3
5.|-- 137.221.83.68 0.0% 10 13.1 13.1 12.9 13.4 0.0
6.|-- 137.221.65.68 0.0% 10 27.5 22.1 12.7 65.0 17.3
7.|-- 137.221.65.1 0.0% 10 13.4 25.3 12.6 82.9 23.4
8.|-- 137.221.65.7 0.0% 10 12.8 12.9 12.7 13.0 0.0
9.|-- 137.221.70.32 0.0% 10 14.2 13.6 12.6 18.1 1.6
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. com 0.0% 10 12.6 15.2 12.5 37.8 7.9
11.|-- 66.109.5.132 0.0% 10 53.0 54.3 50.2 57.6 2.3
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. com 0.0% 10 51.2 53.3 50.9 56.4 2.1
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. com 0.0% 10 52.4 54.5 52.0 57.6 2.2
14.|-- 66.109.6.73 0.0% 10 65.2 67.0 63.9 70.2 2.1
15.|-- agg1.cblsny1002h.northeast.rr. com 0.0% 10 73.6 100.2 73.6 215.2 40.9
16.|-- agg2.cblsny1001m.nyroc.rr. com 0.0% 10 76.6 77.0 76.6 78.8 0.6
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
MTR:
Start: Sun Feb 17 22:50:57 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 0.7 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.8 0.8 0.5 1.9 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.3 12.7 17.2 1.3
6.|-- 137.221.65.68 0.0% 10 34.9 26.2 12.8 78.6 23.5
7.|-- 137.221.65.1 0.0% 10 13.0 21.1 12.7 71.5 19.2
8.|-- 137.221.65.7 0.0% 10 12.8 12.9 12.8 13.4 0.0
9.|-- 137.221.70.32 0.0% 10 12.8 13.1 12.6 15.8 0.9
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. com 0.0% 10 14.7 14.8 12.5 17.6 1.8
11.|-- 66.109.5.132 0.0% 10 53.8 53.6 49.9 57.5 2.6
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. com 0.0% 10 52.3 54.2 51.1 57.0 1.9
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. com 0.0% 10 53.2 54.6 50.3 57.5 2.2
14.|-- 66.109.6.73 0.0% 10 65.8 67.9 64.9 71.0 1.9
15.|-- agg1.cblsny1002h.northeast.rr. com 0.0% 10 225.4 106.6 82.9 225.4 44.1
16.|-- agg2.cblsny1001m.nyroc.rr. com 0.0% 10 76.8 78.5 76.6 94.2 5.5
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
MTR:
Start: Sun Feb 17 22:51:02 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 1.5 0.3 12.3 3.7
2.|-- 24.105.18.131 0.0% 10 0.7 4.0 0.5 21.0 7.2
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.4 0.7 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.7 0.6 1.4 0.0
5.|-- 137.221.83.68 0.0% 10 12.9 14.6 12.7 29.2 5.1
6.|-- 137.221.65.68 0.0% 10 12.8 21.4 12.8 74.7 19.6
7.|-- 137.221.65.1 0.0% 10 13.1 16.5 12.8 34.1 6.9
8.|-- 137.221.65.7 0.0% 10 12.9 13.0 12.8 14.0 0.0
9.|-- 137.221.70.32 0.0% 10 12.7 12.8 12.6 13.3 0.0
10.|-- ge-11-0-0.pr0.sjc20.tbone.rr. com 0.0% 10 12.6 14.2 12.5 27.7 4.7
11.|-- 66.109.5.132 0.0% 10 56.4 53.5 50.6 57.2 2.4
12.|-- bu-ether12.snvacaid17w-bcr00.tbone.rr. com 0.0% 10 54.7 54.2 50.2 57.3 2.4
13.|-- bu-ether14.chcgildt87w-bcr00.tbone.rr. com 0.0% 10 55.7 53.6 50.1 57.8 2.6
14.|-- 66.109.6.73 0.0% 10 68.1 66.9 63.0 70.5 2.4
15.|-- agg1.cblsny1002h.northeast.rr. com 0.0% 10 84.1 87.2 73.8 94.8 5.7
16.|-- agg2.cblsny1001m.nyroc.rr. com 0.0% 10 76.8 76.9 76.6 78.1 0.3
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
Yeah, not just Spectrum. I am with Frontier on the east coast and before 8.1 dropped my average latency was 36ms/36ms for over 2 years. The very next day after 8.1 and everyday since both my home and world stay in the range of 90ms-362ms. And when one does go low it’s either something like 52ms/254ms or 325ms/42ms.
Also been having issues with latency as well, while having spectrum . Seems to only be affecting WoW/blizzard games only too. Usually my latency is in the 30s, but past few days it has been in the low 100s.
At first I thought maybe it was something on my end, but I checked everything out, even looking at my lines outside to see if a critter had done any damage to it, but nothing.
I also live on the East Coast, so hopefully we can figure this out.
So Im not sure what all of this means but here is my looking glass all I saw at the end was 100 percent packet loss so that made me feel all warm and fuzzy…
TRACEROUTE:
traceroute to 69.204.115.9 (69.204.115.9), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.279 ms 0.257 ms 0.252 ms
2 24.105.18.131 (24.105.18.131) 0.849 ms 0.971 ms 2.271 ms
3 137.221.105.16 (137.221.105.16) 0.824 ms 0.830 ms 0.947 ms
4 137.221.66.22 (137.221.66.22) 0.584 ms 0.589 ms 0.587 ms
5 137.221.83.68 (137.221.83.68) 12.814 ms 12.831 ms 12.831 ms
6 137.221.65.68 (137.221.65.68) 12.751 ms 13.924 ms 13.900 ms
7 137.221.65.1 (137.221.65.1) 12.848 ms 12.854 ms 12.850 ms
8 137.221.65.7 (137.221.65.7) 13.115 ms 13.114 ms 14.693 ms
9 137.221.70.32 (137.221.70.32) 12.682 ms 12.685 ms 12.676 ms
10 (66.109.9.172) 13.466 ms 12.623 ms 12.745 ms
11 66.109.5.132 (66.109.5.132) 50.561 ms 50.059 ms 60.017 ms
12 . (66.109.6.9) 59.124 ms 59.145 ms 58.896 ms
13 . (66.109.6.15) 50.139 ms 49.949 ms 50.000 ms
14 66.109.6.73 (66.109.6.73) 63.423 ms 70.925 ms 70.823 ms
15 (24.58.37.115) 70.811 ms 70.450 ms 70.233 ms
PING:
PING 69.204.115.9 (69.204.115.9) 56(84) bytes of data.
— 69.204.115.9 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
MTR:
Start: Mon Feb 18 06:06:03 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 0.6 0.5 1.1 0.0
3.|-- 137.221.105.16 0.0% 10 0.5 0.6 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.6 0.6 0.4 0.7 0.0
5.|-- 137.221.83.68 0.0% 10 49.4 16.5 12.6 49.4 11.6
6.|-- 137.221.65.68 0.0% 10 12.9 21.3 12.8 75.7 20.2
7.|-- 137.221.65.1 0.0% 10 12.6 22.9 12.6 88.9 24.5
8.|-- 137.221.65.7 0.0% 10 12.6 13.2 12.6 16.6 1.1
9.|-- 137.221.70.32 0.0% 10 12.5 12.6 12.5 12.8 0.0
10.|-- 0.0% 10 12.6 12.6 12.4 12.8 0.0
11.|-- 66.109.5.132 0.0% 10 50.1 53.3 50.1 57.2 2.5
12.|-- 0.0% 10 52.0 53.2 49.8 57.2 2.3
13.|-- 0.0% 10 52.5 53.1 50.1 56.4 2.1
14.|-- 66.109.6.73 0.0% 10 70.2 67.7 63.2 70.7 2.4
15.|-- 0.0% 10 80.4 156.5 77.5 660.6 184.9
16.|-- 0.0% 10 77.3 77.4 77.3 77.5 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
Same problem here NY Spectrum, this latency only started a few days ago for me also. normally 30 ms, now up in the 85-89 ms range.