they are updating their twitter, which i guess is a more “public” forum
There was an update from the CS twitter team. They said they’re looking into it and have no ETA for a fix… This was 4 hours ago.
Seems world content is ok, I was do WQ and storyline without issue.
Instances appear lagged out hard. Starts ok, then a minute or two in the 1k+ latency spike begins, ramps up from there until the game is unplayable.
BTW on Cox San Diego. Tracert is normal, it’s just them.
They copy and pasted the same line lmao. I guess if you wanna call that an update. sure
coulda changed the wording up and id of been more happy lol
No, you wouldn’t… You would say, “Same drek, different packaging.”
1 Like
you dont know me b!tch boy
TRACEROUTE:
traceroute to 146.88.193.75 (146.88.193.75), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.311 ms 0.302 ms 0.300 ms Blizzard(24.105.18.3) 0.940 ms 0.941 ms 0.947 ms
3 137.221.105.16 (137.221.105.16) 0.935 ms 0.940 ms 0.950 ms
4 137.221.66.18 (137.221.66.18) 0.888 ms 0.929 ms 0.913 ms
5 137.221.83.66 (137.221.83.66) 14.674 ms 14.670 ms 14.671 ms
6 137.221.65.68 (137.221.65.68) 5.717 ms 11.143 ms 11.078 ms
7 137.221.68.32 (137.221.68.32) 11.004 ms 11.017 ms 8.986 ms
8 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 8.947 ms 8.939 ms 14.164 ms
9 154.54.3.69 (154.54.3.69) 14.118 ms 14.114 ms 14.188 ms
10 be2932.ccr32.phx01.atlas.cogentco.com (154.54.45.161) 17.672 ms 17.838 ms 17.865 ms
11 be2930.ccr21.elp01.atlas.cogentco.com (154.54.42.78) 26.238 ms 26.370 ms 26.486 ms
12 154.54.1.126 (154.54.1.126) 43.225 ms 43.251 ms 43.253 ms
13 154.54.30.242 (154.54.30.242) 43.783 ms 43.830 ms 43.219 ms
14 38.140.184.114 (38.140.184.114) 43.124 ms 45.065 ms 45.069 ms
15 146.88.193.75 (146.88.193.75) 41.296 ms 41.347 ms 41.341 ms
13/04/2019 18:33:53 UTC
--------------------
PING:
PING 146.88.193.75 (146.88.193.75) 56(84) bytes of data.
64 bytes from 146.88.193.75: icmp_seq=1 ttl=54 time=41.3 ms
64 bytes from 146.88.193.75: icmp_seq=2 ttl=54 time=41.8 ms
64 bytes from 146.88.193.75: icmp_seq=3 ttl=54 time=41.2 ms
64 bytes from 146.88.193.75: icmp_seq=4 ttl=54 time=41.2 ms
--- 146.88.193.75 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 41.245/41.435/41.849/0.242 ms
13/04/2019 18:33:53 UTC
--------------------
MTR:
Start: Sat Apr 13 18:33:53 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.2 0.2 0.3 0.0 Blizzard 0.0% 10 4.7 1.0 0.5 4.7 1.3
3.|-- 137.221.105.16 0.0% 10 0.4 1.5 0.4 9.9 2.9
4.|-- 137.221.66.18 0.0% 10 0.5 0.6 0.4 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 5.8 5.7 5.7 5.9 0.0
6.|-- 137.221.65.68 0.0% 10 5.9 8.7 5.7 33.8 8.8
7.|-- 137.221.68.32 0.0% 10 5.6 5.6 5.4 5.8 0.0
8.|-- te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 5.7 5.9 5.7 6.1 0.0
9.|-- 154.54.3.69 0.0% 10 6.0 5.9 5.6 6.1 0.0
10.|-- be2932.ccr32.phx01.atlas.cogentco.com 0.0% 10 17.8 17.6 17.4 17.8 0.0
11.|-- be2930.ccr21.elp01.atlas.cogentco.com 0.0% 10 25.7 25.8 25.6 26.0 0.0
12.|-- 154.54.1.126 0.0% 10 43.2 43.0 42.9 43.2 0.0
13.|-- 154.54.30.242 0.0% 10 43.3 43.4 43.1 44.9 0.3
14.|-- 38.140.184.114 0.0% 10 43.1 43.2 43.1 43.4 0.0
15.|-- 146.88.193.75 0.0% 10 41.8 41.4 41.2 42.0 0.0Really hoping this gets resolved soon. Had to sit myself out of M Stormwall prog on Thursday as the raid lead and tank (luckily they got it without me), and now I can’t even run keys with my guildies without getting frustrated.
Cox in AZ.
I see the logic in that train of thought and almost agree entirely other than one major point… It is still related to Cox’s relationship with the servers. If it was on the Blizzard side for one of their pairing networks, it would affect more than just Cox ISP users. My roommate and I, and another guildmate are the only Cox ISP users in the guild and the only ones with this issue.
I haven’t tested it in raid but i’ve been queuing BGs all morning but it SHOULD be the same.
TRACEROUTE:
traceroute to 70.177.168.232 (70.177.168.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.248 ms 0.229 ms 0.224 ms Blizzard(24.105.18.3) 2.514 ms 2.525 ms 2.610 ms
3 137.221.105.12 (137.221.105.12) 0.515 ms 0.653 ms 0.694 ms
4 137.221.66.16 (137.221.66.16) 0.536 ms 0.646 ms 0.645 ms
5 137.221.83.66 (137.221.83.66) 5.817 ms 5.825 ms 5.840 ms
6 137.221.65.68 (137.221.65.68) 5.693 ms 5.808 ms 5.784 ms
7 137.221.68.32 (137.221.68.32) 5.608 ms 5.611 ms 5.606 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 6.296 ms 6.314 ms 6.313 ms
9 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 17.474 ms 17.448 ms 17.424 ms
10 ip70-177-168-232.ph.ph.cox. net (70.177.168.232) 24.285 ms 23.363 ms 27.427 ms
13/04/2019 18:35:55 UTC
TRACEROUTE:
traceroute to 70.177.168.232 (70.177.168.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.244 ms 0.250 ms 0.254 ms Blizzard(24.105.18.3) 0.522 ms 0.647 ms 0.663 ms
3 137.221.105.12 (137.221.105.12) 0.511 ms 0.635 ms 0.756 ms
4 137.221.66.16 (137.221.66.16) 0.641 ms 0.729 ms 0.750 ms
5 137.221.83.66 (137.221.83.66) 6.348 ms 6.364 ms 6.367 ms
6 137.221.65.68 (137.221.65.68) 6.326 ms 6.125 ms 6.086 ms
7 137.221.68.32 (137.221.68.32) 6.007 ms 6.027 ms 5.727 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.731 ms 5.731 ms 5.732 ms
9 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 17.527 ms 17.531 ms 17.382 ms
10 ip70-177-168-232.ph.ph.cox. net (70.177.168.232) 24.860 ms 24.530 ms 27.166 ms
13/04/2019 18:35:55 UTC
TRACEROUTE:
traceroute to 70.177.168.232 (70.177.168.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.166 ms 3.163 ms 3.165 ms
2 24.105.18.131 (24.105.18.131) 3.840 ms 3.860 ms 3.863 ms
3 137.221.105.12 (137.221.105.12) 3.912 ms 3.922 ms 3.925 ms
4 137.221.66.16 (137.221.66.16) 3.901 ms 3.920 ms 3.925 ms
5 137.221.83.66 (137.221.83.66) 9.184 ms 9.199 ms 9.205 ms
6 137.221.65.68 (137.221.65.68) 71.196 ms 64.411 ms 64.386 ms
7 137.221.68.32 (137.221.68.32) 5.717 ms 5.666 ms 5.648 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.443 ms 5.473 ms 5.455 ms
9 mcdldsrj01-ae1.0.rd.ph.cox. net (68.1.3.115) 16.846 ms 16.774 ms 16.846 ms
10 ip70-177-168-232.ph.ph.cox. net (70.177.168.232) 24.381 ms 26.317 ms 26.223 ms
13/04/2019 18:35:56 UTC
PING:
PING 70.177.168.232 (70.177.168.232) 56(84) bytes of data.
64 bytes from 70.177.168.232: icmp_seq=1 ttl=53 time=23.7 ms
64 bytes from 70.177.168.232: icmp_seq=2 ttl=53 time=24.0 ms
64 bytes from 70.177.168.232: icmp_seq=3 ttl=53 time=23.7 ms
64 bytes from 70.177.168.232: icmp_seq=4 ttl=53 time=23.9 ms
— 70.177.168.232 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 23.761/23.897/24.093/0.134 ms
13/04/2019 18:35:55 UTC
PING:
PING 70.177.168.232 (70.177.168.232) 56(84) bytes of data.
64 bytes from 70.177.168.232: icmp_seq=1 ttl=53 time=23.5 ms
64 bytes from 70.177.168.232: icmp_seq=2 ttl=53 time=24.4 ms
64 bytes from 70.177.168.232: icmp_seq=3 ttl=53 time=24.1 ms
64 bytes from 70.177.168.232: icmp_seq=4 ttl=53 time=27.3 ms
— 70.177.168.232 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 23.576/24.882/27.376/1.478 ms
13/04/2019 18:35:56 UTC
PING:
PING 70.177.168.232 (70.177.168.232) 56(84) bytes of data.
64 bytes from 70.177.168.232: icmp_seq=1 ttl=53 time=24.1 ms
— 70.177.168.232 ping statistics —
4 packets transmitted, 1 received, 75% packet loss, time 2998ms
rtt min/avg/max/mdev = 24.128/24.128/24.128/0.000 ms
13/04/2019 18:35:55 UTC
TRACEROUTE:
traceroute to 70.177.168.232 (70.177.168.232), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.636 ms 0.647 ms 0.649 ms
2 24.105.18.131 (24.105.18.131) 1.727 ms 1.748 ms 1.753 ms
3 137.221.105.12 (137.221.105.12) 1.988 ms 1.999 ms 2.028 ms
4 137.221.66.16 (137.221.66.16) 1.982 ms 1.992 ms 1.987 ms
5 137.221.83.66 (137.221.83.66) 12.231 ms 12.253 ms 12.258 ms
6 137.221.65.68 (137.221.65.68) 12.228 ms 8.218 ms 8.192 ms
7 137.221.68.32 (137.221.68.32) 8.162 ms 7.199 ms 7.176 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 7.146 ms 11.648 ms 11.643 ms
9 mcdldsrj01-ae1.0.rd.ph.cox. net (68.1.3.115) 23.069 ms 23.087 ms 23.089 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 18:35:59 UTC
PING:
PING 70.177.168.232 (70.177.168.232) 56(84) bytes of data.
— 70.177.168.232 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3010ms
13/04/2019 18:36:00 UTC
MTR:
Start: Sat Apr 13 18:35:56 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 1.3 0.0
2.|-- 24.105.18.131 0.0% 10 0.9 0.8 0.5 1.3 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.6 0.5 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 0.6 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 5.7 5.9 5.7 7.2 0.3
6.|-- 137.221.65.68 0.0% 10 6.9 25.5 5.6 140.3 42.7
7.|-- 137.221.68.32 0.0% 10 5.5 7.7 5.5 26.4 6.5
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.5 5.7 5.4 6.9 0.3
9.|-- mcdldsrj01-ae1.0.rd.ph.cox. net 0.0% 10 16.7 18.5 16.6 31.8 4.7
10.|-- ip70-177-168-232.ph.ph.cox. net 70.0% 10 23.1 23.9 23.1 24.6 0.7
13/04/2019 18:35:56 UTC
MTR:
Start: Sat Apr 13 18:35:55 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.6 0.2 3.4 0.7 Blizzard 0.0% 10 2.6 1.2 0.5 2.9 0.7
3.|-- 137.221.105.12 0.0% 10 0.5 0.6 0.5 0.9 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 0.6 0.5 0.7 0.0
5.|-- 137.221.83.66 0.0% 10 5.8 5.8 5.6 6.0 0.0
6.|-- 137.221.65.68 0.0% 10 36.2 24.7 5.7 133.0 40.2
7.|-- 137.221.68.32 0.0% 10 5.6 7.8 5.5 22.6 5.4
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 6.6 5.3 12.0 2.1
9.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 18.3 17.7 17.3 19.1 0.5
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 18:35:55 UTC
MTR:
Start: Sat Apr 13 18:35:56 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 0.5 0.9 0.5 4.5 1.0
3.|-- 137.221.105.12 0.0% 10 0.5 0.5 0.5 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 2.3 0.4 17.7 5.4
5.|-- 137.221.83.66 0.0% 10 5.7 5.7 5.7 5.9 0.0
6.|-- 137.221.65.68 0.0% 10 30.6 15.7 5.6 77.1 22.9
7.|-- 137.221.68.32 0.0% 10 8.9 5.9 5.4 8.9 1.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 6.1 5.5 5.3 6.1 0.0
9.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 17.3 19.6 17.3 34.3 5.3
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 18:35:55 UTC
MTR:
Start: Sat Apr 13 18:35:59 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 1.5 0.2 8.4 2.6
2.|-- 24.105.18.131 0.0% 10 0.6 0.6 0.5 0.9 0.0
3.|-- 137.221.105.12 0.0% 10 0.5 1.5 0.5 9.2 2.6
4.|-- 137.221.66.16 0.0% 10 0.6 0.8 0.5 1.9 0.3
5.|-- 137.221.83.66 0.0% 10 5.8 6.8 5.7 16.2 3.3
6.|-- 137.221.65.68 0.0% 10 5.8 11.5 5.7 37.2 12.0
7.|-- 137.221.68.32 0.0% 10 5.6 5.7 5.5 6.5 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 6.6 5.5 5.3 6.6 0.3
9.|-- mcdldsrj01-ae1.0.rd.ph.cox. net 0.0% 10 16.8 17.1 16.6 20.2 1.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 18:35:59 UTC
Have Cox in Virginia. A couple of hours ago it was working pretty good for me. But within the last 30 minutes the lag spikes are hitting hard. Getting up to 4500ms at times. Hoping for some stability soon.
1 Like
Cox user Rhode island cant do bgs or instances 2000ms spike hard!
I’m on Spectrum in Kansas, and was having this issue last night. it seemed to resolve itself somewhat around 3am, however now, at 1:40 pm, it’s back, and I am having issues logging in and/or staying logged on.
in Oklahoma too, it’s almost unbearable how much lag i’m getting in raids, makes it too much to play, and i know it’s not my pc because it plays other games without a hitch, just wow, and it seems that it started lastnight
Blizzard,
Figure your crap out. Get all your nerds on this issue to resolve it. This is a pay to play game. With that being said, I haven’t played for 3 days because of this crap with your servers. I am paying you guys right now to sit on your asses and say “we are working on it”
Stop working on it for 3 damn days and figure your crap out.
I’d post the looking glass results but forums won’t let me. Cox CT customer here. Unplayable.
ctrl + A and click the “preformatted text” button when posting
TRACEROUTE:
traceroute to 68.109.4.141 (68.109.4.141), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.338 ms 0.330 ms 0.337 ms
2 24.105.18.131 (24.105.18.131) 0.647 ms 0.785 ms 0.798 ms
3 137.221.105.16 (137.221.105.16) 0.518 ms 0.643 ms 0.813 ms
4 137.221.66.18 (137.221.66.18) 1.333 ms 1.408 ms 1.401 ms
5 137.221.83.66 (137.221.83.66) 362.212 ms 362.229 ms 362.239 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.417 ms 5.580 ms 5.562 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.411 ms 5.422 ms 5.376 ms
9 nrfkdsrj01-ae0.0.rd.hr.cox. net (68.1.0.25) 74.204 ms 73.750 ms 73.741 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 18:47:38 UTC
TRACEROUTE:
traceroute to 68.109.4.141 (68.109.4.141), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.515 ms 0.519 ms 0.510 ms Blizzard(24.105.18.3) 3.174 ms 3.183 ms 3.189 ms
3 137.221.105.16 (137.221.105.16) 3.046 ms 3.123 ms 3.132 ms
4 137.221.66.22 (137.221.66.22) 3.067 ms 3.078 ms 3.087 ms
5 137.221.83.68 (137.221.83.68) 349.463 ms 349.514 ms 349.534 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.841 ms 5.872 ms 5.893 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.593 ms 5.622 ms 5.795 ms
9 vbchdsrj01-ae0.0.rd.vb.cox. net (68.1.2.217) 66.667 ms 66.509 ms 66.535 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 18:47:38 UTC
PING:
PING 68.109.4.141 (68.109.4.141) 56(84) bytes of data.
— 68.109.4.141 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
13/04/2019 18:47:38 UTC
PING:
PING 68.109.4.141 (68.109.4.141) 56(84) bytes of data.
— 68.109.4.141 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3002ms
13/04/2019 18:47:38 UTC
TRACEROUTE:
traceroute to 68.109.4.141 (68.109.4.141), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.220 ms 0.262 ms 0.276 ms Blizzard(24.105.18.3) 0.517 ms 0.636 ms 0.823 ms
3 137.221.105.16 (137.221.105.16) 0.589 ms 0.770 ms 0.889 ms
4 137.221.66.22 (137.221.66.22) 0.824 ms 0.838 ms 0.836 ms
5 137.221.83.68 (137.221.83.68) 487.106 ms 487.146 ms 487.163 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.526 ms 5.667 ms 5.682 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.382 ms 5.414 ms 5.394 ms
9 vbchdsrj01-ae0.0.rd.vb.cox. net (68.1.2.217) 66.441 ms 66.472 ms 66.482 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 18:47:42 UTC
PING:
PING 68.109.4.141 (68.109.4.141) 56(84) bytes of data.
— 68.109.4.141 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
13/04/2019 18:47:43 UTC
TRACEROUTE:
traceroute to 68.109.4.141 (68.109.4.141), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.480 ms 0.466 ms 0.475 ms Blizzard(24.105.18.3) 0.805 ms 0.829 ms 1.021 ms
3 137.221.105.16 (137.221.105.16) 0.774 ms 0.826 ms 0.972 ms
4 137.221.66.22 (137.221.66.22) 0.714 ms 0.782 ms 0.815 ms
5 137.221.83.68 (137.221.83.68) 729.846 ms 729.881 ms 949.777 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.543 ms 5.656 ms 5.730 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.587 ms 5.601 ms 5.590 ms
9 vbchdsrj01-ae0.0.rd.vb.cox. net (68.1.2.217) 66.677 ms 66.747 ms 66.764 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 18:47:46 UTC
PING:
PING 68.109.4.141 (68.109.4.141) 56(84) bytes of data.
— 68.109.4.141 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
13/04/2019 18:47:48 UTC
MTR:
Start: Sat Apr 13 18:47:38 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.6 0.8 0.5 2.4 0.5
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 1.3 0.0
4.|-- 137.221.66.18 0.0% 10 0.8 1.0 0.5 4.2 1.0
5.|-- 137.221.83.66 0.0% 10 944.9 800.8 560.7 967.9 142.7
6.|-- 137.221.65.68 80.0% 10 13281 13188 13096 13281 130.7
7.|-- 137.221.68.32 0.0% 10 5.5 5.6 5.4 5.8 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 5.6 5.3 6.6 0.3
9.|-- nrfkdsrj01-ae0.0.rd.hr.cox. net 0.0% 10 86.0 74.1 66.5 88.1 7.9
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 18:47:38 UTC
MTR:
Start: Sat Apr 13 18:47:38 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.9 0.0 Blizzard 0.0% 10 0.8 0.7 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.9 0.7 0.5 0.9 0.0
4.|-- 137.221.66.22 0.0% 10 0.9 0.8 0.5 1.1 0.0
5.|-- 137.221.83.68 0.0% 10 964.8 819.7 593.6 979.5 127.7
6.|-- 137.221.65.68 80.0% 10 13284 13349 13284 13414 91.8
7.|-- 137.221.68.32 0.0% 10 5.7 7.5 5.6 23.6 5.6
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.5 5.9 5.3 10.0 1.3
9.|-- vbchdsrj01-ae0.0.rd.vb.cox. net 0.0% 10 66.7 67.5 66.3 74.3 2.3
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 18:47:38 UTC
MTR:
Start: Sat Apr 13 18:47:42 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.6 0.0 Blizzard 0.0% 10 0.6 1.1 0.5 5.1 1.4
3.|-- 137.221.105.16 0.0% 10 0.7 0.8 0.5 1.2 0.0
4.|-- 137.221.66.22 0.0% 10 0.8 0.8 0.6 1.2 0.0
5.|-- 137.221.83.68 0.0% 10 191.5 617.9 93.1 1020. 368.5
6.|-- 137.221.65.68 80.0% 10 13406 13260 13114 13406 207.0
7.|-- 137.221.68.32 0.0% 10 5.6 5.7 5.6 5.9 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 5.5 5.4 5.8 0.0
9.|-- vbchdsrj01-ae0.0.rd.vb.cox. net 0.0% 10 66.7 68.5 66.5 80.8 4.4
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 18:47:42 UTC
MTR:
Start: Sat Apr 13 18:47:43 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.6 0.0 Blizzard 0.0% 10 0.5 0.7 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 4.4 1.3 0.5 4.4 1.2
4.|-- 137.221.66.22 0.0% 10 1.3 0.8 0.6 1.3 0.0
5.|-- 137.221.83.68 0.0% 10 155.1 608.2 58.0 1106. 405.0
6.|-- 137.221.65.68 80.0% 10 13420 13353 13287 13420 94.2
7.|-- 137.221.68.32 0.0% 10 5.5 5.7 5.5 6.0 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.3 5.7 5.3 7.4 0.5
9.|-- vbchdsrj01-ae0.0.rd.vb.cox. net 0.0% 10 66.4 71.1 66.4 92.7 8.1
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0