大家有發現最近google變很慢嗎？

[sayhi2000]

不知道hinet是為把流量分開還是怎樣~
以前就喜歡這樣連來連去~

google全球性的企業，什麼服務都敢開發~
應該沒理由不讓hinet連~
是不是頻寬不足，所以hinet把fttb的用戶流量轉開?

hinet fttb的用戶，可以寫mail跟hinet反應此事。
說不定頻寬又會擴充！

[rogershu]

一堆客戶用gmail，都念的要死，他們的共同點就是皆為Hinet用戶

[blueno]

我沒有感覺 O.O
可能固定制的關係吧..

[genius82213]

上星期就有這樣的感覺耶！！

我還以為是我家電腦有問題！

[石之軒]

以下存屬猜測,
大概又是錢的關係吧??
若是HINET跟GOOGLE直連,誰要付$$$呢?
HINET自持是台灣龍頭老大,在台灣誰跟我連都要付錢!
GOOGLE是服務提供者,沒道理還要付費兼提供服務吧.
所以就發生HINET用戶需經由第三地轉接的情形.

這時就要比誰的聯外水管比較大了

C:\>tracert www.google.com.tw

Tracing route to www.l.google.com [209.85.175.104]
over a maximum of 30 hops:

1 23 ms 23 ms 23 ms 122-121-0-254.dynamic.hinet.net [122.121.0.254]

2 23 ms 23 ms 23 ms kh-fs-c12r2.router.hinet.net [168.95.35.58]
3 24 ms 23 ms 23 ms kh-c12r12.router.hinet.net [220.128.25.174]
4 30 ms 30 ms 30 ms tp-crs11.router.hinet.net [220.128.2.206]
5 30 ms 30 ms 30 ms r33-s2.tp.hinet.net [220.128.2.161]
6 * 109 ms 111 ms 211-72-233-89.HINET-IP.hinet.net [211.72.233.89]
7 * 109 ms 110 ms xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.238]
8 68 ms 64 ms 67 ms xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.66]
9 * 110 ms 110 ms xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.174]
10 101 ms 99 ms 112 ms 209.85.241.94
11 177 ms 134 ms 141 ms 209.85.250.90
12 140 ms 115 ms 116 ms 209.85.243.23
13 116 ms 131 ms 155 ms 72.14.236.94
14 146 ms 143 ms 144 ms 74.125.184.174
15 143 ms 141 ms 141 ms tc-in-f104.google.com [209.85.175.104]

Trace complete.

就在台灣而已,為何還要繞道日本去呢?
HINET是在堅持什麼,
堅持到消費者的權益都可以不用顧了..
跟NCC投訴不知道有沒有用

有個問題
HINET跟遊戲橘子互連,誰付錢呢?
其他ISP跟遊戲橘子互連,又是誰付錢呢?

[sniper_egg]

個人在公司用速博和Seednet的專線測試，出來的數據還蠻漂亮的。

速博乙太專線線路

Tracing route to www.l.google.com [209.85.175.104]
over a maximum of 30 hops:

1 2 ms 2 ms 5 ms
2 10 ms 10 ms 10 ms
3 7 ms 10 ms 10 ms 122.147.10.xxx
4 11 ms 10 ms 12 ms 211.78.129.78
5 8 ms 11 ms 10 ms 211.78.129.41
6 8 ms 10 ms 10 ms 211.78.150.204
7 8 ms 10 ms 10 ms 72.14.196.21
8 6 ms 10 ms 10 ms 209.85.243.26
9 4 ms 4 ms 3 ms 209.85.243.21
10 19 ms 15 ms 15 ms 72.14.236.206
11 20 ms 20 ms 15 ms 74.125.184.42
12 4 ms 4 ms 3 ms tc-in-f104.google.com [209.85.175.104]

Seednet 10M/2M 3IP線路

Tracing route to www.l.google.com [209.85.175.104]
over a maximum of 30 hops:

1 1 ms 5 ms 5 ms
2 6 ms 10 ms 10 ms
3 28 ms 18 ms 33 ms 203.67.31.xxx
4 26 ms 18 ms 18 ms 139.175.70.2
5 39 ms 18 ms 18 ms R59-19.seed.net.tw [139.175.59.19]
6 29 ms 18 ms 18 ms R57-37.seed.net.tw [139.175.57.37]
7 18 ms 18 ms 18 ms R59-202.seed.net.tw [139.175.59.202]
8 18 ms 40 ms 28 ms h210-192-72-123.seed.net.tw [192.72.123.210]
9 34 ms 18 ms 19 ms 209.85.243.26
10 28 ms 28 ms 19 ms 209.85.243.23
11 19 ms 37 ms 19 ms 72.14.236.98
12 33 ms 22 ms 39 ms 74.125.185.42
13 20 ms 19 ms 19 ms tc-in-f104.google.com [209.85.175.104]

[billhi]

晚上使用google簡直是在活受罪,掉封包率高達19%

C:\>tracert www.google.com.tw

Tracing route to www.l.google.com [66.249.89.104]
over a maximum of 30 hops:

1 13 ms 13 ms 13 ms 59-121-208-254.dynamic.hinet.net [59.121.208.254]
2 13 ms 13 ms 13 ms tp-gs-c6r2.router.hinet.net [168.95.73.62]
3 13 ms 13 ms 14 ms tp-crs11.router.hinet.net [220.128.2.42]
4 14 ms 13 ms 13 ms r33-s2.tp.hinet.net [220.128.2.161]
5 299 ms 301 ms 298 ms 211-72-233-89.HINET-IP.hinet.net [211.72.233.89]

6 311 ms 310 ms 295 ms xe-2-0-0.a21.tokyjp01.jp.ra.gin.ntt.net [61.213.162.102]
7 304 ms * 320 ms xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.70]
8 * 299 ms 300 ms xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.174]
9 301 ms 300 ms 302 ms 209.85.241.96
10 304 ms 303 ms 305 ms 216.239.47.54
11 303 ms 307 ms 307 ms jp-in-f104.google.com [66.249.89.104]

Trace complete.

[mis_waiszli]

原來是HINET的問題~
這幾天同事也是有一直反應連GOOGLE很慢~
多謝以上學長分享相關數據及感覺
小弟也分享一下好了~"~
HINET FTTB 2M/2M 32IP 7000元
C:\Documents and Settings\Administrator>tracert www.google.com.tw

Tracing route to www.l.google.com [72.14.235.104]
over a maximum of 30 hops:

1 1 ms 4 ms 16 ms 192.168.7.254
2 <1 ms <1 ms <1 ms 192.168.2.250
3 1 ms <1 ms <1 ms 10.100.100.100
4 5 ms 3 ms 4 ms 60-248-xxx-xxx.hinet-ip.hinet.net [60.248.xxx.xxx]
5 4 ms 4 ms 4 ms tp-s2-c76r6.router.hinet.net [168.95.81.194]
6 4 ms 4 ms 3 ms tp-crs11.router.hinet.net [220.128.1.234]
7 3 ms 3 ms 3 ms r33-s2.tp.hinet.net [220.128.1.161]
8 83 ms 83 ms 84 ms 211-72-233-89.hinet-ip.hinet.net [211.72.233.89]
9 79 ms 85 ms 94 ms xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.110]
10 40 ms 40 ms 40 ms xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.66]
11 83 ms 83 ms 86 ms xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net [61.213.169.174]
12 83 ms 84 ms 83 ms 209.85.241.94
13 111 ms 110 ms 114 ms 209.85.250.86
14 114 ms 110 ms 107 ms 209.85.250.101
15 120 ms 119 ms 122 ms 72.14.236.206
16 123 ms 129 ms 124 ms 74.125.184.142
17 115 ms 114 ms 116 ms tw-in-f104.google.com [72.14.235.104]
Trace complete.

Ping statistics for 72.14.235.104:
Packets: Sent = 236, Received = 221, Lost = 15 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 125ms, Average = 115ms

真的是太誇張了~
企業用的不是QOS比較高@@" 可是感覺還是很慢耶並沒有比較高阿~
還是付的價格不夠高才會有這樣的數質，及上網的速度@@"

[mis_waiszli]

小弟再補一下另外三家ISP (台灣大寬頻&中嘉和網&億聯科技)

台固FTTB 10M/10M
C:\Documents and Settings\Administrator>tracert www.google.com.tw

Tracing route to www.l.google.com [66.249.89.147]
over a maximum of 30 hops:

1 1 ms 7 ms 16 ms 192.168.7.254
2 <1 ms <1 ms <1 ms 192.168.2.250
3 <1 ms <1 ms <1 ms 10.100.100.100
4 2 ms 2 ms 3 ms 219-87-xxx-xxx.static.tfn.net.tw [219.87.xxx.xxx]
5 2 ms 2 ms 2 ms 10.10.24.225
6 2 ms 2 ms 1 ms 10.10.0.22
7 2 ms 1 ms 2 ms 10.68.240.78
8 2 ms 2 ms 1 ms 10.36.16.57
9 9 ms 1 ms 26 ms 60-199-6-25.static.tfn.net.tw [60.199.6.25]
10 2 ms 1 ms 1 ms 60-199-6-10.static.tfn.net.tw [60.199.6.10]
11 2 ms 2 ms 3 ms 72.14.196.17
12 2 ms 2 ms 2 ms 209.85.243.26
13 32 ms 54 ms 32 ms 209.85.250.91
14 33 ms 33 ms 167 ms 209.85.241.101
15 42 ms 35 ms 35 ms 216.239.47.54
16 32 ms 32 ms 32 ms jp-in-f147.google.com [66.249.89.147]

Trace complete.

Ping statistics for 66.249.89.147:
Packets: Sent = 177, Received = 177, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 46ms, Average = 33ms

KBT FTTB 2M/2M
C:\Documents and Settings\Administrator>tracert www.google.com.tw

Tracing route to www.l.google.com [66.249.89.147]
over a maximum of 30 hops:

1 1 ms 12 ms 14 ms 192.168.7.254
2 <1 ms <1 ms <1 ms 192.168.2.250
3 <1 ms <1 ms <1 ms 10.100.100.100
4 2 ms 1 ms 1 ms 61-63-xxx-hostxxx.kbtelecom.net.tw [61.63.xxx.xxx]
5 3 ms 2 ms 3 ms 61-63-71-host110.kbtelecom.net.tw [61.63.71.110]
6 4 ms 3 ms 3 ms 61-63-71-host49.kbtelecom.net.tw [61.63.71.49]
7 8 ms 4 ms 3 ms 61-63-71-host105.kbtelecom.net.tw [61.63.71.105]
8 7 ms 5 ms 4 ms 61-63-71-host254.kbtelecom.net.tw [61.63.71.254]
9 5 ms 8 ms 4 ms 61-63-63-host122.kbtelecom.net.tw [61.63.63.122]
10 5 ms 4 ms 4 ms 72.14.196.9
11 5 ms 15 ms 5 ms 209.85.243.26
12 38 ms 35 ms 44 ms 209.85.250.91
13 35 ms 34 ms 34 ms 209.85.241.101
14 36 ms 35 ms 35 ms 216.239.47.54
15 38 ms 35 ms 35 ms jp-in-f147.google.com [66.249.89.147]

Trace complete.

Ping statistics for 66.249.89.147:
Packets: Sent = 161, Received = 161, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 72ms, Average = 36ms

Extra-Lan FTTC 20M/20M
C:\Documents and Settings\Administrator>tracert www.google.com.tw
Tracing route to www.l.google.com [72.14.235.147]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms my.router [192.168.1.254]
2 5 ms 6 ms 3 ms 123.50.49.254
3 * 4 ms 7 ms 10.10.20.174
4 4 ms 5 ms 2 ms 10.10.10.194
5 133 ms 324 ms 274 ms 10.10.10.177
6 28 ms 41 ms 5 ms 211.78.151.93
7 5 ms 6 ms 7 ms 211.78.150.204
8 5 ms 13 ms 9 ms 72.14.196.21
9 5 ms 6 ms 7 ms 209.85.243.30
10 6 ms 7 ms 7 ms 209.85.250.101
11 15 ms 20 ms 16 ms 72.14.236.94
12 13 ms 22 ms 16 ms 74.125.184.10
13 5 ms 8 ms 6 ms tw-in-f147.google.com [72.14.235.147]
Trace complete.

Ping statistics for 72.14.235.104:
Packets: Sent = 118, Received = 118, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 27ms, Average = 8ms

這三家都比中華便宜，怎麼會比中華還要順~
貴的一定比較好嗎~
看來該把中華的FTTB的服務移到另外二條上，該是做下一步的時候了~

[RIDER]

問過hinet了
HINET說Google伺服器一個在美國一個在日本NTT
HINET走的是日本(上面大大SEEDNET走的應該是美國)
但是HINET表示最近連日本不管是NTT或是KDDI都已經超出預期頻寬
上月才加一條NTT海纜目前還在和日本要求增加連線頻寬
要到明年才能解決日本連線頻寬

至於GOOGLE問題還在想辦法

難怪最近晚上連日本簡直就是噩夢