Tracing route to gi1-24.ccr01.jfk03.atlas.cogentco.com [38.104.70.125]
over a maximum of 30 hops:
1 8 ms 8 ms 8 ms 218.1.60.200
2 7 ms 8 ms 8 ms 218.1.62.49
3 46 ms 33 ms 9 ms 124.74.210.241
4 9 ms 9 ms 8 ms 61.152.86.46
5 84 ms 11 ms 11 ms 202.97.33.62
6 19 ms 8 ms 9 ms 202.97.33.102
7 292 ms 303 ms 303 ms 202.97.51.54
8 176 ms 176 ms 177 ms 202.97.50.26
9 207 ms 208 ms 209 ms 218.30.54.110
10 197 ms 197 ms 197 ms te0-2-0-7.mpd21.lax01.atlas.cogentco.com [154.54
.24.61]
11 202 ms 202 ms 202 ms te0-1-0-6.mpd21.iah01.atlas.cogentco.com [154.54
.5.101]
12 219 ms 219 ms 348 ms te3-2.mpd01.atl01.atlas.cogentco.com [154.54.24.
5]
13 299 ms 250 ms 266 ms te0-5-0-7.mpd21.dca01.atlas.cogentco.com [154.54
.25.253]
14 309 ms 298 ms 277 ms te0-4-0-7.mpd21.jfk02.atlas.cogentco.com [154.54
.41.22]
15 268 ms 267 ms 268 ms te9-1.mpd01.jfk01.atlas.cogentco.com [154.54.1.1
73]
16 244 ms 244 ms 246 ms gi1-24.ccr01.jfk03.atlas.cogentco.com [38.104.70
.125]
Tracing route to gi1-24.ccr01.jfk03.atlas.cogentco.com [38.104.70.125]
over a maximum of 30 hops:
1 8 ms 8 ms 8 ms 21 ...
大哥你又错了,你tracert了NYC的IP,不是优化的IP
Tracing route to enotch.gigabitethernet2-4.core1.nyc1.he.net [216.66.41.202]
over a maximum of 30 hops:
1 3 ms 3 ms 2 ms 124.74.22.242
2 3 ms 4 ms 2 ms 124.74.22.242
3 3 ms 2 ms 3 ms 124.74.23.105
4 8 ms 6 ms 17 ms 124.74.209.57
5 3 ms 3 ms 3 ms 61.152.86.142
6 4 ms 4 ms 4 ms 202.97.35.158
7 7 ms 6 ms 7 ms 202.97.35.26
8 198 ms 202 ms 196 ms 202.97.51.178
9 196 ms 196 ms 196 ms 202.97.49.118
10 173 ms 175 ms 173 ms 10gigabitethernet6-1.core1.lax1.he.net [64.71.13
1.133]
11 263 ms 256 ms 266 ms 10gigabitethernet4-3.core1.nyc4.he.net [72.52.92
.225]
12 255 ms 262 ms 254 ms 10gigabitethernet1-2.core1.nyc1.he.net [72.52.92
.46]
13 241 ms 236 ms 235 ms enotch.gigabitethernet2-4.core1.nyc1.he.net [216
.66.41.202]