well, it happened again, log as follows
在上限 30 個躍點上追蹤 159.153.70.90 的路由
1 1 ms <1 ms 1 ms localhost
2 5 ms 7 ms 1 ms n140-h254.150.118.dynamic.da.net.twx
4]
3 7 ms 7 ms 5 ms 10.254.0.17
4 4 ms 3 ms 3 ms 10.254.0.77
5 11 ms 3 ms 13 ms 10.254.0.25
6 2 ms 1 ms 2 ms 10.254.0.245
7 2 ms 2 ms 2 ms 202-153-197-17-static.unigate.net.tw [202.153.197.1
7]
8 2 ms 2 ms 2 ms 45-60-41-175.TWGATE-IP.twgate.net [175.41.60.45]
9 3 ms 3 ms 3 ms 203.78.181.133
10 155 ms 155 ms 156 ms 6-60-41-175.TWGATE-IP.twgate.net [175.41.60.6]
11 145 ms 145 ms 145 ms xe-9-0-0.bar1.SanFrancisco1.Level3.net [4.53.132.17
]
12 * * * 要求等候逾時。
13 * * * 要求等候逾時。
14 162 ms 161 ms 162 ms 4.28.172.102
15 151 ms 151 ms 151 ms 159.153.68.46
16 153 ms 153 ms 153 ms 159.153.70.90
追蹤完成。
The tracert looks fine, but a tracert is a snapshot of the instant you ran it.
pathping or pingplotter is better to look for issues, but looking at the tracert it looks fine at the time it was ran.
hops 12 and 13 can be ignored just means ICMP is currently set to ignore and isnt affecting forward path
