大家有發現最近google變很慢嗎? 我是用google當首頁 但最近常常網頁都開不出來或要等很久才開出來 ping google 封包loss率都在10%上下 但ping 其他像雅虎,PCHOME,Hinet都正常 不知有沒有人和我一樣呢? |
回覆: 大家有發現最近google變很慢嗎? 同感 樓主也是用hinet的吧? 因為我用 hinet 最近這幾個月明顯感受的到連線反應變慢 封包常常丟失 打電話問客服都牽拖給google:mad: |
回覆: 大家有發現最近google變很慢嗎? 的確..尤其到晚上時上youtube...連影片預覽圖很多都開不出來.. 上Google查詢, 總是要多按幾次才有辦法查 我也是用黑net的 |
回覆: 大家有發現最近google變很慢嗎? 我也是受害者,HINET加GOOGLE反應奇慢,都直接跳過了。 |
回覆: 大家有發現最近google變很慢嗎? 沒錯!我是使用Hinet FTTB 10M/2M 網路搜尋了一下,好像只有Hinet FTTB用戶才會這樣子 好像是IP段118開頭才會, |
回覆: 大家有發現最近google變很慢嗎? 1 個附加檔案 youtube並沒有問題,我ping的結果都不會掉封包 但Ping [url]www.google.com[/url] 或[url]www.google.com.tw[/url] 每隔幾個就Request timed out Request timed out. Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Request timed out. Reply from 66.249.89.99: bytes=32 time=152ms TTL=239 Request timed out. Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Request timed out. Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Request timed out. Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Reply from 66.249.89.99: bytes=32 time=160ms TTL=239 Ping statistics for 66.249.89.99: Packets: Sent = 443, Received = 408, Lost = 35 (7% loss), Approximate round trip times in milli-seconds: Minimum = 152ms, Maximum = 162ms, Average = 159ms Control-C ^C |
回覆: 大家有發現最近google變很慢嗎? 小弟是CHT FTTB 10M/2M 用戶,上星期有時是連google都連不上。 |
回覆: 大家有發現最近google變很慢嗎? bb CABLE 8M上GOOGLE,很順也很快~ 而且速度有比以前快很多~以前gmail反應也慢,不過現在也很快。 |
回覆: 大家有發現最近google變很慢嗎? 變慢的應該只有 HiNet 用戶 因為 HiNet 連 Google 連到日本那邊去了 不太可能是 HiNet 故意不連台灣 Google 伺服器,所以就是台灣 Google 伺服器不爽給 HiNet 直連 |
回覆: 大家有發現最近google變很慢嗎? [CODE][root@xxxxxx ~]# ping www.google.com -c 10 PING www.l.google.com (66.249.89.99) 56(84) bytes of data. 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=1 ttl=244 time=55.6 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=2 ttl=244 time=54.9 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=3 ttl=244 time=56.3 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=4 ttl=244 time=54.1 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=5 ttl=244 time=55.9 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=6 ttl=244 time=55.8 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=7 ttl=244 time=55.5 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=8 ttl=244 time=54.2 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=9 ttl=244 time=55.1 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=10 ttl=244 time=56.3 ms --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9004ms rtt min/avg/max/mdev = 54.183/55.401/56.327/0.768 ms [root@xxxxxx ~]# [root@oooooo ~]# ping www.google.com -c 10 PING www.l.google.com (66.249.89.147) 56(84) bytes of data. 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=1 ttl=234 time=166 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=2 ttl=234 time=168 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=3 ttl=237 time=162 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=4 ttl=237 time=162 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=5 ttl=237 time=162 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=6 ttl=234 time=169 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=7 ttl=237 time=162 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=8 ttl=234 time=166 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=9 ttl=234 time=168 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=10 ttl=234 time=166 ms --- www.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9175ms rtt min/avg/max/mdev = 162.037/165.409/169.018/2.725 ms [root@oooooo ~]# traceroute www.google.com traceroute to www.google.com (66.249.89.104), 30 hops max, 60 byte packets 1 60-249-136-254.HINET-IP.hinet.net (60.249.136.254) 16.522 ms 17.087 ms 17.524 ms 2 kh-c76r2.router.hinet.net (168.95.33.222) 17.141 ms 17.347 ms 17.696 ms 3 kh-c12r11.router.hinet.net (220.128.24.150) 18.096 ms kh-c12r12.router.hinet.net (220.128.25.146) 18.476 ms 18.608 ms 4 tp-crs11.router.hinet.net (220.128.2.206) 26.075 ms tp-crs11.router.hinet.net (220.128.1.206) 26.201 ms tp-crs11.router.hinet.net (220.128.2.206) 25.778 ms 5 r33-s2.tp.hinet.net (220.128.1.161) 26.108 ms 26.525 ms * 6 211-72-233-89.HINET-IP.hinet.net (211.72.233.89) 164.319 ms 160.225 ms 160.126 ms 7 xe-2-0-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.102) 160.235 ms xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.110) 166.655 ms xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.238) 167.277 ms 8 xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 285.204 ms xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.70) 160.239 ms 160.192 ms 9 xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174) 161.519 ms 161.374 ms 161.783 ms 10 209.85.241.96 (209.85.241.96) 166.664 ms 166.824 ms 167.724 ms 11 216.239.47.54 (216.239.47.54) 176.053 ms 175.967 ms 175.892 ms 12 jp-in-f104.google.com (66.249.89.104) 164.323 ms 164.485 ms 164.876 ms [root@oooooo ~]# [/CODE] xxxxxx 的是Seednet 10M/2M 固八FTTB線路上的Linux主機 ooooo 的是Hinet 10M/2M 固三FTTB線路上的Linux主機 種花的路由也許也真的怪怪的吧?不過trace起來好像是Hinet問題? |
所有時間均為 +8。現在的時間是 12:38 AM。 |
XML | RSS 2.0 | RSS |
本論壇所有文章僅代表留言者個人意見,並不代表本站之立場,討論區以「即時留言」方式運作,故無法完全監察所有即時留言,若您發現文章可能有異議,請 email :[email protected] 處理。