但是改成 ping www.yahoo.com.tw or www.kimo.com.tw就很好看
而且開網頁速度也改善很多
ping www.google.com.tw
Ping statistics for 72.14.235.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 46ms, Average = 42ms
ping google.com
Ping statistics for 72.14.205.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 212ms, Maximum = 213ms, Average = 212ms
ping www.google.com
Ping statistics for 66.249.89.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 84ms, Average = 73ms
www.google.com.tw→72.14.235.99 Average = 42ms
google.com→72.14.205.100 Average = 212ms
怎會差這麼多
附上出ISP的tracert
www.google.com.tw
7 39 ms 40 ms 40 ms 209.85.243.26
8 41 ms 41 ms 50 ms 209.85.243.23
9 50 ms 54 ms 46 ms 72.14.238.166
10 67 ms 54 ms 54 ms 74.125.185.42
11 42 ms 52 ms 41 ms tc-in-f99.google.com [209.85.175.99]
google.com
6 48 ms 57 ms 39 ms 74.125.51.77
7 40 ms 40 ms 63 ms 209.85.243.26
8 85 ms 71 ms 70 ms 209.85.250.91
9 156 ms 159 ms 157 ms 216.239.47.237
10 173 ms 159 ms 158 ms 216.239.48.32
11 159 ms 195 ms 166 ms 64.233.174.97
12 166 ms 167 ms 160 ms 209.85.251.129
13 171 ms 163 ms 163 ms 74.125.31.2
14 182 ms 160 ms 159 ms cg-in-f100.google.com [209.85.171.100]
https://tinyurl.com/4ah27wpx (短網址為01停權星粉H先生網址)
慎入
seednet線路
Tracing route to jp-in-f99.google.com [66.249.89.99]
over a maximum of 30 hops:
1 18 ms 18 ms 18 ms 123-204-86-1.static.seed.net.tw [123.204.86.1]
2 18 ms 17 ms 18 ms sj235-67.dialup.seed.net.tw [139.175.235.67]
3 18 ms 18 ms 18 ms R57-133.seed.net.tw [139.175.57.133]
4 18 ms 18 ms 18 ms R59-202.seed.net.tw [139.175.59.202]
5 19 ms 18 ms 37 ms h210-192-72-123.seed.net.tw [192.72.123.210]
6 18 ms 18 ms 18 ms 209.85.243.26
7 92 ms 74 ms 74 ms 209.85.250.91
8 50 ms 48 ms 48 ms 209.85.241.101
9 60 ms 53 ms 54 ms 216.239.47.54
10 49 ms 49 ms 49 ms jp-in-f99.google.com [66.249.89.99]
Trace complete.
====================
同時間hinet的線路
Tracing route to jp-in-f99.google.com [66.249.89.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 20 ms 21 ms 21 ms 122-120-112-254.dynamic.hinet.net [122.120.112.254]
3 20 ms 20 ms 20 ms tp-sc-c76r1.router.hinet.net [168.95.170.106]
4 20 ms 20 ms 20 ms tp-sc-t64-1.router.hinet.net [220.128.5.166]
5 21 ms 21 ms 20 ms tp-crs11.router.hinet.net [220.128.3.18]
6 20 ms 20 ms 20 ms r33-s2.tp.hinet.net [220.128.1.161]
7 102 ms 102 ms 101 ms 211-72-233-89.HINET-IP.hinet.net [211.72.233.89]
8 101 ms 103 ms 101 ms xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.238]
9 57 ms 55 ms 57 ms xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.66]
10 101 ms 100 ms 101 ms xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.174]
11 63 ms 62 ms 65 ms 209.85.241.96
12 71 ms 69 ms 59 ms 216.239.47.54
13 60 ms 62 ms 70 ms jp-in-f99.google.com [66.249.89.99]
johnhjwu wrote:
回覆你的問題, 也順...在network design 中 shortest route的確是被考慮的重點, 但是設計歸設計, 實作歸實作, ISP想和國內外ISP互連不代表一定可以直接相連。
(恕刪)
這些設計理論只有在 backbone 頻寬無限大時才可能真的實作最佳化
有空去 TWNIC 看一下各家 ISP的網路頻寬及連線圖吧
有的 ISP 只拉大水管進各 TWIX, 自己最多拉幾個小水管出國
其它 ISP 憑什麼要拉大水管出國, 然後透過 TWIX 幫你運送流量出國?
traceroute 過得去, 真正流量上來時, 是不最後一定走這條又很難說了
但 Google 的 load balance, 應該就會根據你的 IP "儘可能"塞近的Server 給你
只是, 實體的遠近跟網路的速度, 未必有正相關
by the way, Hinet 最近確實有點問題. 至少到香港這段是怪怪的
即使前幾天海纜修復後, 內部 routing 看起來怪怪的
會卡在某些地方過不太過去
i travell, therefore i am...
http://juan.tw
內文搜尋
從 APP 打開
X