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

[sniper_egg]

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

至於GOOGLE問題還在想辦法

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

剛剛用VPN連回公司再用Seednet線路測試到日本，結果一樣順暢無比。

華電是否在對外頻寬上有不足的地方了呢？

還是路由上真的有問題？都是值得研究的地方，畢竟上面有人用專業型的FTTB測出來數據都爛的要命，華電還敢收企業型的費用？

[supermaxfight]

反應時間在30ms...這會是在國外的主機？
google在台灣沒有設置網頁搜尋用的主機？

C:\Documents and Settings\####>tracert www.google.com.tw

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

  1     *       24 ms    17 ms  123-204-86-1.static.seed.net.tw [123.204.86.1]
  2    30 ms    23 ms    30 ms  sj235-66.dialup.seed.net.tw [139.175.235.66]
  3    94 ms    30 ms    34 ms  R57-37.seed.net.tw [139.175.57.37]
  4    37 ms    31 ms    29 ms  R59-202.seed.net.tw [139.175.59.202]
  5    36 ms    22 ms    26 ms  74.125.51.81
  6    18 ms    18 ms    18 ms  209.85.243.26
  7    37 ms    28 ms    38 ms  209.85.250.101
  8    42 ms    40 ms    32 ms  72.14.238.170
  9    62 ms    25 ms    19 ms  74.125.184.46
 10    30 ms    27 ms    36 ms  tc-in-f147.google.com [209.85.175.147]

Trace complete.

[BenLi]

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

至於GOOGLE問題還在想辦法

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

很明顯 HiNet 是在扯爛，Google 在全球主要國家都均設有伺服器
正常情況下該國 ISP 就連該國 Google 伺服器

[chiener]

昨天(12日)下午四時許突然恢復，我的IP是118段的。

[ahome]

怪,google主機不是架在速博嗎？
但是看hinet的路由卻是導向國外？
可見hinet的設定有問題..

[blueno]

真的很奇怪,剛剛trace發現,

為甚麼連到tw的google server 要繞到日本再繞到美國啊.....

hinet不是有美國直連的海纜.. 怎麼數字越來越難看了....

PS:雖然使用上是沒有差異就是了,,,,

[pooh]

威達5M/5M測試結果:

Pinging www.l.google.com [66.249.89.104] with 32 bytes of data:

Reply from 66.249.89.104: bytes=32 time=35ms TTL=243
Reply from 66.249.89.104: bytes=32 time=36ms TTL=243
Reply from 66.249.89.104: bytes=32 time=35ms TTL=243
Reply from 66.249.89.104: bytes=32 time=36ms TTL=243
Reply from 66.249.89.104: bytes=32 time=36ms TTL=243
Reply from 66.249.89.104: bytes=32 time=36ms TTL=243
Reply from 66.249.89.104: bytes=32 time=36ms TTL=243

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

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

1 1 ms <1 ms <1 ms my.router [192.168.0.1]
2 4 ms 10 ms 13 ms 253.110.254.121.static.tcol.com.tw [121.254.110.
253]
3 * * 2 ms 172.17.0.31
4 2 ms 2 ms 2 ms 172.17.0.150
5 2 ms 2 ms 2 ms TCNOC-R76-G3-4-YUNGDA.IX.kbtelecom.net [203.187.
9.133]
6 5 ms 4 ms 5 ms TPNOC3-C65-VL541-TCNOC.IX.kbtelecom.net [203.133
.92.1]
7 6 ms 6 ms 5 ms TPNOC3-P76-G8-7-C65.IX.kbtelecom.net [203.133.92
.42]
8 5 ms 5 ms 6 ms 72.14.196.9
9 6 ms 6 ms 5 ms 209.85.243.26
10 6 ms 8 ms 6 ms 209.85.250.101
11 11 ms 17 ms 18 ms 72.14.238.162
12 11 ms 17 ms 17 ms 74.125.185.42
13 6 ms 6 ms 6 ms tc-in-f147.google.com [209.85.175.147]

Trace complete.

[supermaxfight]

這次會變成當年無名主機在giga時的翻版嗎
google會妥協，改用hinet的專線嗎

[BenLi]

這次會變成當年無名主機在giga時的翻版嗎
google會妥協，改用hinet的專線嗎

不會，因為 Google 用的是自己的專線

HiNet
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) 4 msec 0 msec 4 msec
3 r33-s2.tp.hinet.net (220.128.2.161) 0 msec 4 msec 0 msec
4 211-72-233-89.HINET-IP.hinet.net (211.72.233.89) 84 msec 84 msec 80 msec
5 xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.238) 36 msec 36 msec
xe-2-0-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.102) 40 msec
6 xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.70) 36 msec 40 msec
xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 36 msec
7 xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174) 36 msec 40 msec 40 msec
8 209.85.241.96 80 msec 84 msec 84 msec
9 216.239.47.54 92 msec 88 msec 88 msec
10 *
www.l.google.com (66.249.89.147) 84 msec 84 msec

Seednet
traceroute to www.l.google.com (72.14.235.99), 25 hops max, 44 byte packets
1 139.175.55.3 (139.175.55.3) 0.413 ms 0.363 ms 0.334 ms
2 R57-94 (139.175.57.94) 0.392 ms 0.426 ms 0.374 ms
3 R59-194 (139.175.59.194) 0.508 ms 0.548 ms 0.668 ms
4 74.125.51.77 (74.125.51.77) 0.573 ms 0.695 ms 0.560 ms
5 209.85.243.26 (209.85.243.26) 0.669 ms 209.85.243.30 (209.85.243.30) 1.674 ms 1.561 ms
6 209.85.250.103 (209.85.250.103) 1.668 ms 1.552 ms 1.549 ms
7 72.14.238.174 (72.14.238.174) 6.881 ms 1.694 ms 72.14.238.162 (72.14.238.162) 2.171 ms
8 74.125.185.142 (74.125.185.142) 14.950 ms 74.125.184.10 (74.125.184.10) 13.029 ms 74.125.185.14 (74.125.185.14) 1.949 ms
9 tw-in-f99.google.com (72.14.235.99) 2.008 ms 2.063 ms 1.874 ms

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

1 1 ms <1 ms <1 ms 192.168.0.1
2 15 ms 14 ms 18 ms xxx-xxx-xxx-xxx.static.tfn.net.tw [xxx.xxx.xxx.xxx]
3 13 ms 13 ms 13 ms 10.36.21.33
4 14 ms 27 ms 13 ms 60-199-6-105.static.tfn.net.tw [60.199.6.105]
5 13 ms 13 ms 13 ms 60-199-6-78.static.tfn.net.tw [60.199.6.78]
6 13 ms 13 ms 18 ms 72.14.196.17
7 14 ms 13 ms 13 ms 209.85.243.26
8 14 ms 14 ms 14 ms 209.85.243.21
9 22 ms 15 ms 20 ms 72.14.238.162
10 22 ms 17 ms 18 ms 74.125.185.174
11 15 ms 16 ms 16 ms tc-in-f104.google.com [209.85.175.104]

Trace complete.

KBT
traceroute to www.google.com.tw (209.85.175.147) ...
1 u93-254.user.kbtelecom.net (203.133.93.254) 0.590 ms 0.475 ms 0.552 ms
2 TPNOC1-G65-CORE.IX.kbtelecom.net (203.133.2.252) 0.866 ms 0.388 ms 0.413 ms
3 TPNOC3-C65-TenG4-1-TPNOC1.IX.kbtelecom.net (203.133.92.90) 0.640 ms 0.543 ms 0.556 ms
4 TPNOC3-P76-G8-7-C65.IX.kbtelecom.net (203.133.92.42) 0.655 ms TPNOC3-P76-G8-10-C65.IX.kbtelecom.net (203.187.6.125) 0.542 ms TPNOC3-P76-G9-7-C65.IX.kbtelecom.net (203.133.92.130) 0.549 ms
5 72.14.196.9 (72.14.196.9) 0.645 ms 0.548 ms 0.557 ms
6 209.85.243.30 (209.85.243.30) 1.683 ms 1.721 ms 1.583 ms
7 209.85.243.23 (209.85.243.23) 1.683 ms 209.85.250.101 (209.85.250.101) 1.721 ms 1.574 ms
8 72.14.236.94 (72.14.236.94) 1.824 ms 72.14.236.210 (72.14.236.210) 7.152 ms 72.14.238.166 (72.14.238.166) 5.100 ms
9 74.125.184.46 (74.125.184.46) 1.824 ms 74.125.185.170 (74.125.185.170) 5.682 ms 74.125.185.42 (74.125.185.42) 15.077 ms
10 tc-in-f104.google.com (209.85.175.104) 1.958 ms 1.866 ms 1.878 ms

So-net
Tracing the path to www.google.com.tw (72.14.235.104) on TCP port 80, 30 hops max
1 219.84.214.2 (219.84.214.2) 7.713 ms 5.406 ms 9.888 ms
2 72.14.196.33 (72.14.196.33) 9.833 ms 5.975 ms 9.886 ms
3 209.85.243.26 (209.85.243.26) 9.923 ms 0.884 ms 9.864 ms
4 209.85.250.101 (209.85.250.101) 9.905 ms 6.428 ms 9.894 ms
5 72.14.236.210 (72.14.236.210) 11.363 ms 4.321 ms 5.956 ms
6 74.125.185.142 (74.125.185.142) 11.433 ms 10.347 ms 1.882 ms
7 tw-in-f104.google.com (72.14.235.104) [open] 8.675 ms 6.270 ms 9.987 ms

APOL
1 router (203.79.224.254) 0.448 ms 0.403 ms 0.400 ms
2 192.168.101.29 (192.168.101.29) 0.333 ms 0.283 ms 0.335 ms
3 211-76-96-125.ebix.net.tw (211.76.96.125) 0.463 ms 0.356 ms 0.329 ms
4 72.14.196.13 (72.14.196.13) 0.579 ms 0.557 ms 0.553 ms
5 209.85.243.30 (209.85.243.30) 1.588 ms 209.85.243.26 (209.85.243.26) 0.641 ms 0.617 ms
6 209.85.250.103 (209.85.250.103) 3.230 ms 1.554 ms 209.85.250.101 (209.85.250.101) 1.582 ms
7 72.14.236.98 (72.14.236.98) 1.770 ms 72.14.238.170 (72.14.238.170) 2.052 ms 72.14.238.174 (72.14.238.174) 1.719 ms
8 74.125.185.42 (74.125.185.42) 11.173 ms 74.125.185.174 (74.125.185.174) 2.052 ms 74.125.185.42 (74.125.185.42) 10.141 ms
9 tc-in-f99.google.com (209.85.175.99) 1.975 ms 1.847 ms 1.942 ms

Academia Sinica Network 中研院
0 140.109.13.2 (140.109.13.2) 28.65 km 3.69 ms 0.765 ms 0.573 ms
1 140.109.254.181 (140.109.254.181) Neighbor 0.24 ms 0.27 ms 0.542 ms
2 140.109.251.77 (ge-0-2-0.br0.tpe.tw.rt.ascc.net) Neighbor 0.4 ms 0.362 ms 0.447 ms
3 202.169.174.206 (202.169.174.206) Neighbor 0.477 ms 0.436 ms 0.472 ms
4 202.169.174.42 (202.169.174.42) 52.5 km 1.07 ms 1.05 ms 1.11 ms
5 209.85.243.26 (209.85.243.26) 51.5 km 1.03 ms 1.07 ms 1.06 ms
6 209.85.250.103 (209.85.250.103) 93.5 km 2.26 ms 1.87 ms 3.45 ms
7 72.14.238.170 (72.14.238.170) 128 km 12.3 ms 14.4 ms 2.56 ms
8 74.125.185.46 (74.125.185.46) 140 km 15.4 ms 2.8 ms 3.01 ms
9 209.85.175.99 www.l.google.com 105.5 km 2.17 ms 2.21 ms 2.11 ms

由以上數據可以看出除了 HiNet 有經過第三網路供應商(NTT)之外
其餘 ISP 都是與 Google 直連，所以與 wretch 情況完全不同

而且推測 Google 機房可能一個位於台北、一個位於台中
與 HiNet 所說 Google 機房一個位於美國、一個位於日本可以說不攻自破
而是各主要國家中的各主要城市都可能設有 Google 機房

所以最後小弟猜測最有可能就是 #15 樓所說
HiNet 自持是台灣龍頭老大，在台灣誰跟我連都要付錢！
於是 Google 不爽就跟 HiNet 說，那你就慢慢繞道日本去吧

[billhi]

今天發現連google都不會loss封包
不知道是不是因為今天是星期日的關係
好久沒享受到使用google暢快的感覺了