心血來潮，從公司tracert回家，路由竟然是....，傑克，這真是太神奇了~~
不知SEEDNET又在搞什麼鬼??
Tracing route to 221-169-70-XXX.adsl.static.seed.net.tw [221.169.70.XXX]
1 * * * Request timed out.
2 3 ms 2 ms 2 ms 211.22.98.XXX
3 * * * Request timed out.
4 53 ms 53 ms 54 ms as080027.seed.net.tw [139.175.80.27]
5 56 ms 56 ms 57 ms ty-fo-c12r1.router.hinet.net [211.22.39.2]
6 56 ms 54 ms 55 ms tp-s2-c12r1.router.hinet.net [210.65.2.234]
7 55 ms 56 ms 56 ms clnbg-76.seed.net.tw [139.175.80.76]
8 * * * Request timed out.
9 * 109 ms 111 ms ge-7-0-3.a20.tokyjp01.jp.ra.verio.net [61.200.92
118]
10 * * * Request timed out.
11 116 ms 117 ms 115 ms ge-3-0-0.r00.tokyjp01.jp.bb.verio.net[129.250.3.146]
12 151 ms 187 ms 151 ms p4-0-2-0.r00.taiptw01.tw.bb.verio.net [129.250.4
214]
13 148 ms 149 ms 152 ms ge-0-0-0.a01.taiptw01.tw.ra.verio.net [61.58.32.
5]
14 151 ms 148 ms * ge-0-0-0.a01.taiptw01.tw.ra.verio.net [61.58.32.
5]
15 114 ms 114 ms 113 ms r59-169.seed.net.tw [139.175.59.169]
16 111 ms 111 ms 112 ms r56-216.seed.net.tw [139.175.56.216]
17 * 113 ms 112 ms r56-216.seed.net.tw [139.175.56.216]
18 110 ms * * r58-30.seed.net.tw [139.175.58.30]
19 111 ms 113 ms * r121-163.seed.net.tw [192.72.121.163]
20 * * 113 ms clnbg-76.seed.net.tw [139.175.80.76]
21 111 ms 111 ms * clnbg-76.seed.net.tw [139.175.80.76]

贊助商連結

做了一下測試,發現hinet連到seednet固一ip(221開頭)的路由如同您所測試的結果一般,蠻怪異的

Tracing route to sw*-*-*.adsl.seed.net.tw [221.*.*.*]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 61 ms 59 ms 59 ms tp-s2-c12r2.router.hinet.net [210.65.200.34]
6 60 ms 59 ms 58 ms tp-s2-c12r32.router.hinet.net [211.72.233.27]
7 101 ms 100 ms 106 ms 211.22.33.217
8 106 ms 100 ms 104 ms ge-7-1-0.a20.tokyjp01.jp.ra.verio.net [61.213.162.54]
9 104 ms 105 ms 99 ms xe-0-0-0.r20.tokyjp01.jp.bb.verio.net [61.213.162.237]
10 102 ms 106 ms 105 ms ge-0-0-0.r00.tokyjp01.jp.bb.verio.net [129.250.3.121]
11 140 ms 137 ms 140 ms p4-0-2-0.r00.taiptw01.tw.bb.verio.net [129.250.4.214]
12 138 ms 138 ms 137 ms ge-0-0-0.a01.taiptw01.tw.ra.verio.net [61.58.32.35]
14 139 ms 103 ms 141 ms 61.58.33.126
15 97 ms 102 ms 96 ms R56-37.seed.net.tw [139.175.56.37]
16 102 ms 104 ms 97 ms R56-209.seed.net.tw [139.175.56.209]
17 110 ms 107 ms 105 ms R58-162.seed.net.tw [139.175.58.162]
18 * 106 ms * R122-134.seed.net.tw [192.72.122.134]
19 117 ms * * sw*-*-*.adsl.seed.net.tw [221.*.*.*]

而連往浮動ip則看似正常

Tracing route to 203-*-*-*.adsl.dynamic.seed.net.tw [203.*.*.*]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 65 ms 59 ms 59 ms tp-s2-c12r2.router.hinet.net [210.65.200.34]
6 63 ms 66 ms 59 ms tp-twix-r6.router.hinet.net [211.22.32.201]
7 63 ms 59 ms 60 ms 211.22.41.241
8 63 ms 67 ms 66 ms snback3.seed.net.tw [139.175.56.205]
9 69 ms 71 ms 72 ms R58-162.seed.net.tw [139.175.58.162]
10 71 ms 73 ms 64 ms R122-134.seed.net.tw [192.72.122.134]
11 69 ms 65 ms 71 ms br169068.seed.net.tw [139.175.169.68]
12 97 ms 97 ms 99 ms 203-*-*-*.adsl.dynamic.seed.net.tw [203.*.*.*]

hinet連seednet的61.59/16也有同樣狀況,
跟hinet反應回覆是下面這樣,不知道是哪家嫌國際頻寬太大所以惡搞!?

有關台端反應的問題,經轉HiNet骨幹查測應為SeedNet調整不讓HiNet直接連接而繞道日本,
將會與SeedNet查詢並協調處理.

好像已經恢復正常了~~
最近SEEDNET常常怪怪的
我昨天ping seednet網站居然可以到3000 ms（從seednet adsl),不過今天又恢復正常了∼∼

唉!
商業競爭，害死消費者!

剛測了一下,還是一樣啊........

traceroute to 61.59.100.254 (61.59.100.254), 64 hops max, 44 byte packets
4 tp-s2-c12r1.router.hinet.net (210.65.2.18) 36.688 ms 36.947 ms 36.982 ms
5 tp-s2-c12r32.router.hinet.net (211.72.108.11) 38.296 ms 37.812 ms 38.170 ms
6 211.22.33.217 (211.22.33.217) 92.534 ms 93.024 ms 78.535 ms
7 xe-7-0-1.a20.tokyjp01.jp.ra.verio.net (61.120.144.86) 76.225 ms ge-7-1-0.a20.tokyjp01.jp.ra.verio.net (61.213.162.54) 75.601 ms 75.575 ms
8 xe-1-0-0.r21.tokyjp01.jp.bb.verio.net (61.213.162.233) 77.032 ms 75.823 ms 77.348 ms
9 ge-1-0-0.r00.tokyjp01.jp.bb.verio.net (129.250.3.138) 79.462 ms ge-1-0-0.r01.tokyjp01.jp.bb.verio.net (129.250.3.182) 78.698 ms ge-1-0-0.r00.tokyjp01.jp.bb.verio.net (129.250.3.138) 79.305 ms
10 p4-0-2-0.r00.taiptw01.tw.bb.verio.net (129.250.4.214) 114.643 ms 115.353 ms 115.420 ms
11 ge-0-0-0.a01.taiptw01.tw.ra.verio.net (61.58.32.35) 115.969 ms 112.896 ms ge-1-0-0.r00.taiptw01.tw.bb.verio.net (129.250.4.73) 157.448 ms
12 61.58.33.126 (61.58.33.126) 117.249 ms ge-0-0-0.a01.taiptw01.tw.ra.verio.net (61.58.32.35) 155.791 ms 61.58.33.126 (61.58.33.126) 119.844 ms
13 R56-37.seed.net.tw (139.175.56.37) 77.458 ms 76.851 ms 61.58.33.126 (61.58.33.126) 154.766 ms
14 R56-65.seed.net.tw (139.175.56.65) 77.031 ms 78.075 ms 76.922 ms
15 R58-74.seed.net.tw (139.175.58.74) 83.965 ms 82.821 ms R56-65.seed.net.tw (139.175.56.65) 116.645 ms
16 R56-158.seed.net.tw (139.175.56.158) 85.542 ms 84.876 ms 84.259 ms



traceroute to 221.169.70.2 (221.169.70.2), 64 hops max, 44 byte packets
4 tp-s2-c12r2.router.hinet.net (210.65.200.18) 39.527 ms 39.067 ms 38.614 ms
5 tp-s2-c12r32.router.hinet.net (211.72.233.27) 38.740 ms 38.136 ms 37.606 ms
6 211.22.33.185 (211.22.33.185) 93.479 ms 109.327 ms 92.801 ms
7 xe-7-0-1.a20.tokyjp01.jp.ra.verio.net (61.120.144.86) 92.735 ms ge-7-1-0.a20.tokyjp01.jp.ra.verio.net (61.213.162.54) 91.913 ms 91.728 ms
8 xe-0-0-0.r20.tokyjp01.jp.bb.verio.net (61.213.162.237) 91.684 ms 91.917 ms 92.615 ms
9 ge-0-0-0.r00.tokyjp01.jp.bb.verio.net (129.250.3.121) 94.982 ms 97.409 ms ge-3-0-0.r01.tokyjp01.jp.bb.verio.net (129.250.3.178) 92.816 ms
10 p4-0-2-0.r00.taiptw01.tw.bb.verio.net (129.250.4.214) 131.292 ms p4-1-1-0.r01.taiptw01.tw.bb.verio.net (129.250.4.94) 125.774 ms 126.568 ms
11 ge-0-0-0.a01.taiptw01.tw.ra.verio.net (61.58.32.35) 129.162 ms ge-1-0-0.r00.taiptw01.tw.bb.verio.net (129.250.4.73) 128.590 ms ge-0-0-0.a01.taiptw01.tw.ra.verio.net (61.58.32.35) 132.480 ms
12 61.58.33.126 (61.58.33.126) 128.912 ms ge-0-0-0.a01.taiptw01.tw.ra.verio.net (61.58.32.35) 129.111 ms 61.58.33.126 (61.58.33.126) 129.200 ms
13 61.58.33.126 (61.58.33.126) 127.987 ms 125.633 ms R59-169.seed.net.tw (139.175.59.169) 93.416 ms
14 R59-169.seed.net.tw (139.175.59.169) 90.005 ms R56-216.seed.net.tw (139.175.56.216) 93.389 ms 94.033 ms
15 R56-216.seed.net.tw (139.175.56.216) 90.075 ms R58-30.seed.net.tw (139.175.58.30) 93.976 ms R56-216.seed.net.tw (139.175.56.216) 90.586 ms
16 R58-30.seed.net.tw (139.175.58.30) 89.826 ms R121-163.seed.net.tw (192.72.121.163) 93.369 ms R58-30.seed.net.tw (139.175.58.30) 89.868 ms
17 clnbg-36.seed.net.tw (139.175.80.36) 93.114 ms 94.028 ms R121-163.seed.net.tw (192.72.121.163) 89.347 ms
18 clnbg-76.seed.net.tw (139.175.80.76) 94.932 ms clnbg-36.seed.net.tw (139.175.80.36) 90.178 ms clnbg-76.seed.net.tw (139.175.80.76) 95.387 ms
19 clnbg-76.seed.net.tw (139.175.80.76) 90.648 ms

X...hinet又在起肖說謊了

最初由 supermaxfight 發表
X...hinet又在起肖說謊了

hinet又再起肖說謊? 是知道什麼內幕嗎?



剛測了一下,
hinet連往這幾個TWNIC上登記為seednet的IP網段都會繞去日本
211.74.0.0/18
61.59.0.0/16
221.169.0.0/16

不知道這些是不是都在seednet固定IP的網段裡?

最初由 darksnow 發表
hinet又再起肖說謊? 是知道什麼內幕嗎?



剛測了一下,
hinet連往這幾個TWNIC上登記為seednet的IP網段都會繞去日本
211.74.0.0/18
61.59.0.0/16
221.169.0.0/16

不知道這些是不是都在seednet固定IP的網段裡?
我測了，但是懶得貼
基本上是不會故意跑日本在繞回台灣，對網路管理方面稍微瞭解的人，應該都知道這是啥回事吧...(我不知道別問我...):D

最初由 supermaxfight 發表
我測了，但是懶得貼
基本上是不會故意跑日本在繞回台灣，對網路管理方面稍微瞭解的人，應該都知道這是啥回事吧...(我不知道別問我...):D

我真的不知道是怎麼回事~~~~沒待過像SEEDNET那種"大"公司