Reply from 184.105.64.250: bytes=32 time=205ms TTL=117
Reply from 184.105.64.250: bytes=32 time=204ms TTL=117
Reply from 184.105.64.250: bytes=32 time=205ms TTL=117
Reply from 184.105.64.250: bytes=32 time=205ms TTL=117
Tracing route to 184.105.64.250 over a maximum of 30 hops
1 16 ms 18 ms 16 ms 123.149.36.1
2 22 ms 16 ms 17 ms 219.147.62.5
3 33 ms 28 ms 16 ms 221.123.85.222.broad.zz.ha.dynamic.163data.
n [222.85.123.221]
4 17 ms 16 ms 18 ms 141.123.85.222.broad.zz.ha.dynamic.163data.
n [222.85.123.141]
5 27 ms 27 ms 26 ms 202.97.54.21
6 27 ms 27 ms 27 ms 202.97.53.82
7 26 ms 26 ms 27 ms 202.97.53.222
8 181 ms 181 ms 183 ms 202.97.52.170
9 192 ms 191 ms 191 ms 202.97.49.158
10 182 ms 181 ms 181 ms 10gigabitethernet6-1.core1.lax1.he.net [64.
1.133]
11 190 ms 191 ms 199 ms 10gigabitethernet1-3.core1.pao1.he.net [72.
.21]
12 206 ms 199 ms 204 ms 10gigabitethernet1-2.core1.fmt1.he.net [66.
58.241]
13 204 ms 204 ms 203 ms 184.105.64.250
Tracing route to 184.105.64.250 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Vita [192.168.1.1]
2 3 ms 1 ms 1 ms 1.124.71.222.broad.xw.sh.dynamic.163data.com.c
[222.71.124.1]
3 2 ms 1 ms 1 ms 124.74.59.101
4 3 ms 2 ms 2 ms 124.74.210.173
5 3 ms 2 ms 2 ms 61.152.86.42
6 4 ms 3 ms 2 ms 202.97.50.250
7 96 ms 93 ms 93 ms 202.97.35.18
8 334 ms 344 ms 393 ms 202.97.51.150
9 390 ms 393 ms 388 ms 202.97.50.62
10 238 ms 233 ms 239 ms 10gigabitethernet4-3.core1.sjc2.he.net [64.71.
1.129]
11 299 ms 304 ms 299 ms 10gigabitethernet1-1.core1.fmt1.he.net [72.52.
.109]
12 238 ms 241 ms 238 ms 184.105.64.250