Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 2 ms 24.105.30.129
Trace complete.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 2 ms 24.105.30.129
Trace complete.
Got my tracert results now. Here:
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 2 ms 1 ms 1 ms Broadcom.Home [192.168.2.1]
2 16 ms 15 ms 15 ms loop0.13w.ba05.crbk.nf.aliant.net [142.163.63.251]
3 24 ms 20 ms 18 ms te-0-0-0-1-82.dr01.crbk.nf.aliant.net [142.163.37.209]
4 15 ms 15 ms 15 ms ae3-50.dr02.crbk.nf.aliant.net [142.166.181.54]
5 24 ms 24 ms 25 ms et-0-3-0.cr02.hlfx.ns.aliant.net [142.166.181.113]
6 25 ms 25 ms 25 ms hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net [142.166.149.93]
7 44 ms 42 ms 41 ms be19.bx01.nycm.ny.aliant.net [207.231.227.110]
8 43 ms 42 ms 43 ms lag-197.ear3.NewYork1.Level3.net [4.71.230.101]
9 41 ms 43 ms 41 ms 4.69.216.226
10 99 ms 42 ms 43 ms BLIZZARD-EN.ear1.NewYork5.Level3.net [4.35.72.34]
11 72 ms 71 ms 72 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
12 * * * Request timed out.
13 85 ms 73 ms 71 ms be2-pe02-eqch2.as57976.net [137.221.69.73]
14 73 ms 72 ms 73 ms 24.105.62.129
Trace complete.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 5 ms 2 ms 4 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 5 ms 3 ms 47.198.0.1
3 6 ms 10 ms 5 ms 172.99.45.78
4 19 ms 11 ms 14 ms ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
5 11 ms 10 ms 10 ms ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
6 * 11 ms 10 ms lag-101.ear3.Miami2.Level3.net [4.15.156.29]
7 * * * Request timed out.
8 11 ms 11 ms 19 ms BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198]
9 70 ms 70 ms 69 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
10 185 ms 169 ms 91 ms xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
11 71 ms 69 ms 70 ms et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
12 68 ms 71 ms 69 ms 137.221.65.122
13 140 ms 69 ms 76 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
14 70 ms 69 ms 68 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
15 70 ms 71 ms 77 ms 24.105.30.129
Trace complete.
Same here, just tried logging in but says lost connection to server. unable to log in. restart didnt help
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 11 ms 6 ms 7 ms 24.105.62.129
Trace complete.
Thanks for all of the information here, it’s been very useful during our troubleshooting. Our network engineers are working to isolate the problem and we’ll provide more updates as we get them, sorry for the disruption.
TRACEROUTE:
traceroute to 50.30.173.139 (50.30.173.139), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.283 ms 0.423 ms 0.442 ms
2 24.105.18.131 (24.105.18.131) 18.465 ms 18.725 ms 18.757 ms
3 137.221.105.16 (137.221.105.16) 0.727 ms 0.757 ms 0.764 ms
4 137.221.66.22 (137.221.66.22) 1.126 ms 1.145 ms 1.151 ms
5 137.221.83.68 (137.221.83.68) 2.428 ms 2.436 ms 2.442 ms
6 137.221.65.68 (137.221.65.68) 5.738 ms 5.758 ms 5.751 ms
7 137.221.68.32 (137.221.68.32) 5.813 ms 5.826 ms 6.163 ms
8 las-b21-link.telia.net (62.115.178.200) 5.391 ms 5.410 ms 5.478 ms
9 los-brdr-02.inet.qwest.net (63.146.27.249) 5.501 ms 5.617 ms 5.741 ms
10 abq-edge-07.inet.qwest.net (67.14.25.50) 26.465 ms 26.474 ms 26.456 ms
11 65.123.146.254 (65.123.146.254) 35.572 ms 35.773 ms 35.895 ms
12 host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia.net (50.30.172.1) 35.738 ms * *
13 * * *
14 * * *
15 * * *
19/08/2019 20:26:58 UTC
--------------------
TRACEROUTE:
traceroute to 50.30.173.139 (50.30.173.139), 15 hops max, 60 byte packets
1 Blizzard Blizzard 5.478 ms 5.479 ms 5.497 ms
2 24.105.18.131 (24.105.18.131) 25.655 ms 25.686 ms 25.918 ms
3 137.221.105.16 (137.221.105.16) 6.616 ms 6.639 ms 6.647 ms
4 137.221.66.22 (137.221.66.22) 6.677 ms 8.105 ms 8.296 ms
5 137.221.83.68 (137.221.83.68) 9.927 ms 9.949 ms 9.955 ms
6 137.221.65.68 (137.221.65.68) 10.814 ms 6.243 ms 6.234 ms
7 137.221.68.32 (137.221.68.32) 6.620 ms 6.640 ms 6.650 ms
8 las-b21-link.telia.net (62.115.178.200) 5.925 ms 5.961 ms 5.725 ms
9 los-brdr-02.inet.qwest.net (63.146.27.249) 5.501 ms 5.700 ms 5.708 ms
10 abq-edge-07.inet.qwest.net (67.14.25.50) 26.621 ms 26.460 ms 26.520 ms
11 65.123.146.254 (65.123.146.254) 35.542 ms 35.775 ms 35.923 ms
12 host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia.net (50.30.172.1) 34.405 ms 34.547 ms 34.590 ms
13 * * *
14 * * *
15 * * *
19/08/2019 20:26:58 UTC
--------------------
PING:
PING 50.30.173.139 (50.30.173.139) 56(84) bytes of data.
--- 50.30.173.139 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
19/08/2019 20:26:58 UTC
--------------------
PING:
PING 50.30.173.139 (50.30.173.139) 56(84) bytes of data.
--- 50.30.173.139 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
19/08/2019 20:26:58 UTC
--------------------
MTR:
Start: Mon Aug 19 20:26:58 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.5 0.3 0.7 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 4.4 0.6 36.2 11.2
3.|-- 137.221.105.16 0.0% 10 0.6 0.8 0.6 1.4 0.0
4.|-- 137.221.66.22 0.0% 10 0.8 2.9 0.8 17.8 5.2
5.|-- 137.221.83.68 0.0% 10 7.2 6.9 3.4 10.7 2.1
6.|-- 137.221.65.68 0.0% 10 6.0 61.1 5.7 449.4 139.7
7.|-- 137.221.68.32 0.0% 10 6.4 6.3 6.0 6.6 0.0
8.|-- las-b21-link.telia.net 0.0% 10 5.9 6.1 5.6 8.8 0.7
9.|-- los-brdr-02.inet.qwest.net 0.0% 10 12.3 15.7 6.3 28.7 6.2
10.|-- abq-edge-07.inet.qwest.net 0.0% 10 26.6 26.6 26.5 26.8 0.0
11.|-- 65.123.146.254 0.0% 10 31.7 35.5 31.7 50.7 5.5
12.|-- host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia.net 0.0% 10 34.3 33.1 31.0 42.9 3.6
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19/08/2019 20:26:58 UTC
--------------------
MTR:
Start: Mon Aug 19 20:26:58 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 0.9 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 4.2 0.5 36.3 11.2
3.|-- 137.221.105.16 0.0% 10 0.7 0.8 0.6 1.3 0.0
4.|-- 137.221.66.22 0.0% 10 1.3 3.1 1.0 17.8 5.2
5.|-- 137.221.83.68 0.0% 10 7.2 6.9 3.5 10.9 2.2
6.|-- 137.221.65.68 0.0% 10 6.1 84.6 5.7 683.7 212.7
7.|-- 137.221.68.32 0.0% 10 6.4 6.2 5.9 6.5 0.0
8.|-- las-b21-link.telia.net 0.0% 10 5.8 5.8 5.6 6.0 0.0
9.|-- sjp-brdr-05.inet.qwest.net 0.0% 10 12.4 15.8 6.5 28.9 6.2
10.|-- abq-edge-07.inet.qwest.net 0.0% 10 26.6 26.6 26.5 26.8 0.0
11.|-- 65.123.146.254 0.0% 10 35.2 35.7 31.9 50.9 5.5
12.|-- host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia.net 0.0% 10 34.3 33.0 31.1 42.2 3.3
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19/08/2019 20:26:58 UTC
--------------------
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.0.1
3 8 ms 8 ms 8 ms phn4-dsl-gw04.phn4.qwest.net [71.32.112.4]
4 15 ms 10 ms 8 ms 71-32-113-25.phn4.qwest.net [71.32.113.25]
5 8 ms 8 ms 8 ms 209.181.128.2
6 * * * Request timed out.
7 18 ms 18 ms 18 ms blizzard-en.ear3.losangeles1.level3.net [4.71.135.106]
8 529 ms 59 ms 39 ms ae1-br02-eqla1.as57976.net [137.221.68.35]
9 19 ms 18 ms 18 ms be2-pe02-eqla1.as57976.net [137.221.68.73]
10 30 ms 18 ms 19 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
11 19 ms 18 ms 19 ms 24.105.30.129
Trace complete.
Hello everyone,
Our network engineers continue to investigate the connectivity issues and we would like to request some fresh traceroutes using a different IP address.
Please feel free to run a new traceroute to 24.105.62.129 and post the results.
The more information we gather here the better, so it is very much appreciated. Thanks to everyone who has already helped out so far.
8 hours later and still only on this point? Reset the servers …
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.0.1
3 34 ms 43 ms 13 ms phn4-dsl-gw04.phn4.qwest.net [71.32.112.4]
4 13 ms 7 ms 15 ms 71-32-113-25.phn4.qwest.net [71.32.113.25]
5 9 ms 8 ms 8 ms 209.181.128.2
6 * * * Request timed out.
7 32 ms 25 ms 25 ms blizzard-en.ear3.losangeles1.level3.net [4.71.135.106]
8 * * * Request timed out.
9 62 ms 63 ms 61 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
10 62 ms * 62 ms 137.221.65.133
11 62 ms 63 ms 62 ms be1-pe02-eqch2.as57976.net [137.221.69.69]
12 64 ms 63 ms 63 ms 24.105.62.129
Trace complete.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 4 ms 1 ms 1 ms modem.Home [192.168.0.1]
2 25 ms 3 ms 3 ms tukw-dsl-gw66.tukw.qwest.net [63.231.10.66]
3 9 ms 4 ms 3 ms tukw-agw1.inet.qwest.net [63.226.198.9]
4 6 ms 9 ms 8 ms sea-brdr-03.inet.qwest.net [67.14.41.150]
5 * * * Request timed out.
6 4 ms 4 ms 5 ms ae-2-3613.edge1.Seattle3.Level3.net [4.69.160.73]
7 5 ms 5 ms 4 ms BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146]
8 53 ms 53 ms 55 ms ae1-br02-eqse2.as57976.net [137.221.73.35]
9 53 ms 53 ms * xe-0-0-1-1-br02-eqch2.as57976.net [137.221.65.42]
10 57 ms 55 ms 54 ms be2-pe02-eqch2.as57976.net [137.221.69.73]
11 54 ms 54 ms 54 ms chi-eqch2-ia-bons-04.as57976.net [137.221.66.15]
12 54 ms 55 ms 54 ms 24.105.62.129
Trace complete.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 2 ms 2 ms 3 ms 24.105.62.129
Trace complete.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 15 ms 7 ms 10 ms 24.105.30.129Trace complete.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 1 ms 1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 5 ms 5 ms 6 ms 24.105.62.129
Trace complete.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 16 ms 12 ms 9 ms 24.105.62.129
Trace complete.
Americas region.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 3 ms 1 ms 170.238.151.234
3 6 ms 3 ms 1 ms 170.238.151.233
4 4 ms 3 ms 3 ms 177.36.88.237
5 4 ms 4 ms 1 ms 10.62.67.2
6 35 ms 19 ms 20 ms 100.80.1.6
7 25 ms 25 ms 24 ms 100.72.8.31
8 26 ms 24 ms 25 ms 100.66.8.201
9 * * * Request timed out.
10 222 ms 230 ms 178 ms 137.221.71.33
11 * 157 ms 157 ms 137.221.65.8
12 157 ms 154 ms 156 ms 137.221.69.71
13 159 ms 157 ms 157 ms 24.105.62.129
Fios customer in Richmond VA area, tried to enter a toon and it hung, then couldnt get in
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 8 ms 9 ms 24.105.30.129
Trace complete.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 13 ms 8 ms 9 ms 24.105.62.129
Trace complete.
tracert 24.105.30.129
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 82 ms 2 ms 2 ms 192.168.43.1
2 151 ms 49 ms 39 ms [66.174.43.225]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 209 ms 23 ms 32 ms [69.83.107.242]
7 36 ms 32 ms 43 ms [69.83.107.138]
8 46 ms 38 ms 40 ms [69.83.99.28]
9 56 ms 54 ms 42 ms [69.83.99.28]
10 46 ms 42 ms 44 ms [69.83.98.21]
11 45 ms 44 ms 31 ms [204.148.39.1]
12 183 ms 60 ms 48 ms [140.222.225.165]
13 58 ms 49 ms 64 ms 204.255.168.254
14 288 ms 58 ms 49 ms [12.122.141.182]
15 46 ms 49 ms 64 ms [12.122.96.89]
16 56 ms 57 ms 44 ms 12.247.68.74
17 104 ms 97 ms 91 ms [137.221.75.33]
18 108 ms 83 ms 88 ms [137.221.65.48]
19 215 ms 164 ms 91 ms [137.221.65.20]
20 148 ms 98 ms 91 [137.221.68.73]
21 98 ms 100 ms 98 ms 24.105.30.129
Trace complete.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 5 ms 5 ms 4 ms hitronhub.home [192.168.0.1]
2 13 ms 13 ms 13 ms 10.178.128.1
3 15 ms 14 ms 16 ms ve51-cr01-mlxe16.cpc.md.atlanticbb. net [146.168.176.166]
4 14 ms 13 ms 13 ms ve14-cr01-mlxe16.phi.pa.atlanticbb. net [146.168.176.136]
5 20 ms 18 ms 20 ms static-146-168-176-128.md.cpe.atlanticbb. net [146.168.176.128]
6 20 ms 23 ms 20 ms static-207-255-30-162.paw.cpe.atlanticbb. net [207.255.30.162]
7 21 ms 20 ms 20 ms ash-b1-link.telia. net [62.115.61.252]
8 38 ms 39 ms 47 ms ash-bb3-link.telia. net [62.115.143.78]
9 * 33 ms 42 ms nyk-bb3-link.telia. net [62.115.141.245]
10 37 ms 37 ms 37 ms chi-b21-link.telia. net [80.91.246.162]
11 54 ms 41 ms 50 ms blizzard-ic-348622-chi-b21.c.telia. net [62.115.178.249]
12 96 ms * * ae1-br02-eqch2.as57976. net [137.221.69.35]
13 84 ms 115 ms 72 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
14 89 ms 54 ms 105 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
15 82 ms 115 ms 67 ms 24.105.62.129
Trace complete.