※ 引述《hbi (hbi)》之銘言：
: 剛tracert 一下 www.google.com.tw
我剛剛也用Hinet和Seednet的tracert試了一下,
Hinet到www.google.com.tw要80ms, Seednet只要1.87ms?
這也差太多了... 是因為Hinet去日本玩了一趟嗎~~
參考來源 http://trace.seed.net.tw/cgi-bin/trace.pl
http://traceroute.hinet.net/cgi-bin/tracert.pl
PS: 有個疑問, 為什麼hinet的tracert中間node的latency會比後來的還高啊?
Seednet的tracert
程式執行中...
traceroute to www.l.google.com (209.85.175.99), 25 hops max, 44 byte packets
1 139.175.55.3 (139.175.55.3) 0.517 ms 0.420 ms 0.367 ms
2 R57-133 (139.175.57.133) 0.387 ms 0.399 ms 0.363 ms
3 R59-202 (139.175.59.202) 0.527 ms 0.510 ms 0.526 ms
4 74.125.51.77 (74.125.51.77) 0.642 ms 0.580 ms 0.528 ms
5 209.85.243.26 (209.85.243.26) 0.558 ms 209.85.243.30 (209.85.243.30) 1.535 ms 1.604 ms
6 209.85.250.103 (209.85.250.103) 1.620 ms 1.605 ms 1.540 ms
7 72.14.238.166 (72.14.238.166) 1.799 ms 72.14.238.174 (72.14.238.174) 1.751 ms 72.14.238.170 (72.14.238.170) 4.897 ms
8 74.125.185.174 (74.125.185.174) 1.887 ms 74.125.185.46 (74.125.185.46) 13.582 ms 74.125.184.42 (74.125.184.42) 23.031 ms
9 tc-in-f99.google.com (209.85.175.99) 1.877 ms 1.870 ms 1.778 ms
Hinet的tracert
Tracing the route to www.l.google.com (66.249.89.147)
1 tp-s2-c6r16.router.hinet.net (210.65.161.22) 0 msec 0 msec 0 msec
2 tp-crs11.router.hinet.net (220.128.2.146) 0 msec 4 msec 0 msec
3 r33-s2.tp.hinet.net (220.128.2.161) 0 msec 0 msec 0 msec
4 211-72-233-89.HINET-IP.hinet.net (211.72.233.89) 80 msec * 80 msec
5 xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.238) 80 msec 84 msec
xe-2-0-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.102) 80 msec
6 xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 196 msec
xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.70) 228 msec
xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 208 msec
7 xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174) 84 msec 84 msec 84 msec
8 209.85.241.96 88 msec 84 msec 80 msec
9 216.239.47.54 92 msec 92 msec 88 msec
10 www.l.google.com (66.249.89.147) 80 msec 84 msec 80 msec
--
如果在世界上的頹廢,
可以換來對自己的負責,
那我寧願對自己負責....
--
: 剛tracert 一下 www.google.com.tw
我剛剛也用Hinet和Seednet的tracert試了一下,
Hinet到www.google.com.tw要80ms, Seednet只要1.87ms?
這也差太多了... 是因為Hinet去日本玩了一趟嗎~~
參考來源 http://trace.seed.net.tw/cgi-bin/trace.pl
http://traceroute.hinet.net/cgi-bin/tracert.pl
PS: 有個疑問, 為什麼hinet的tracert中間node的latency會比後來的還高啊?
Seednet的tracert
程式執行中...
traceroute to www.l.google.com (209.85.175.99), 25 hops max, 44 byte packets
1 139.175.55.3 (139.175.55.3) 0.517 ms 0.420 ms 0.367 ms
2 R57-133 (139.175.57.133) 0.387 ms 0.399 ms 0.363 ms
3 R59-202 (139.175.59.202) 0.527 ms 0.510 ms 0.526 ms
4 74.125.51.77 (74.125.51.77) 0.642 ms 0.580 ms 0.528 ms
5 209.85.243.26 (209.85.243.26) 0.558 ms 209.85.243.30 (209.85.243.30) 1.535 ms 1.604 ms
6 209.85.250.103 (209.85.250.103) 1.620 ms 1.605 ms 1.540 ms
7 72.14.238.166 (72.14.238.166) 1.799 ms 72.14.238.174 (72.14.238.174) 1.751 ms 72.14.238.170 (72.14.238.170) 4.897 ms
8 74.125.185.174 (74.125.185.174) 1.887 ms 74.125.185.46 (74.125.185.46) 13.582 ms 74.125.184.42 (74.125.184.42) 23.031 ms
9 tc-in-f99.google.com (209.85.175.99) 1.877 ms 1.870 ms 1.778 ms
Hinet的tracert
Tracing the route to www.l.google.com (66.249.89.147)
1 tp-s2-c6r16.router.hinet.net (210.65.161.22) 0 msec 0 msec 0 msec
2 tp-crs11.router.hinet.net (220.128.2.146) 0 msec 4 msec 0 msec
3 r33-s2.tp.hinet.net (220.128.2.161) 0 msec 0 msec 0 msec
4 211-72-233-89.HINET-IP.hinet.net (211.72.233.89) 80 msec * 80 msec
5 xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.238) 80 msec 84 msec
xe-2-0-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.102) 80 msec
6 xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 196 msec
xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.70) 228 msec
xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 208 msec
7 xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174) 84 msec 84 msec 84 msec
8 209.85.241.96 88 msec 84 msec 80 msec
9 216.239.47.54 92 msec 92 msec 88 msec
10 www.l.google.com (66.249.89.147) 80 msec 84 msec 80 msec
--
如果在世界上的頹廢,
可以換來對自己的負責,
那我寧願對自己負責....
--
All Comments