| 會員  | 回覆: 大家有發現最近google變很慢嗎？ 的確如果主機在美國不可能反應速度到20毫秒，用目前知道最快的速度光速去算 光速乘 20毫秒 = 5 995.84916 公里 我用Google earth拉直線跨過太平洋從台灣到美國西岸要10000公里，拉到太平洋一半就不止20秒了，而且這還是光速，不考慮router處理的速度 我在想，如果從世界各地去ping某個主機，從最短的反應速度看來，似乎可以大概定位出在哪裡的樣子 XD? |
| 回覆 |
| 明誠科技小峰 | 回覆: 大家有發現最近google變很慢嗎？ 這次好玩了,其實hinet到google慢也不是一天兩天了,以往youtube用hinet的10M/2M有時候就是慢到不行,如果情況如大家所推測,我想近期應該就得坐下來談判了. |
| 回覆 |
| 豬生廢猿 | 回覆: 大家有發現最近google變很慢嗎？ 引用:
有沒有可能是Google的台灣資料中心要向Hinet收錢, 但Hinet不想付呢? Google是營利事業, 雖然有網路廣告可以收錢, 但這應該還不足以支付各項免費服務的營運成本, 所以也不能排除Google向各互連ISP收費的可能性. 大家如果進一步查詢, 就不難發現, 除了Hinet用戶之外, 各位以trcert追蹤路由, 出了ISP的節點後, 都是屬於Google網內的節點. 另一個蠻有趣的現象是, 即使和台灣Google有互連的ISP的使用者連入Google, 有些仍會被Google本身的網路處理機制把連線導向日本的伺服器. 只不過Google在台日之間的連線都是走自有的10GbE光纖骨幹, 封包來回延遲大約只有30ms, 許多用戶根本感覺不出來.... (ADSL使用者在本地線路的延遲都要30～70ms起跳了) 而Hinet用戶先前不太感覺得到Lag的原因, 應該是之前連NTT還算順暢, 但接二連三發生連往日本和北美的海纜故障維修, 新建連日海纜又要明年才能啟用, 然後Google的服務愈來愈多....... 再加上Hinet的光纖用戶數持續大幅成長, 於是連往日本的頻寬終於爆了.... | |
| 回覆 |
| 會員 | 回覆: 大家有發現最近google變很慢嗎？ 另一個好玩的狀況 使用了Seednet DNS跟使用了Hinet DNS的差異  Seednet DNS: 使用FTTB一般DHCP取得 139.175.55.244 139.175.252.16 Hinet DNS: 一般耳熟能詳的168.95.192.1及168.95.1.1 線路:家中Seednet FTTB 使用Seednet DNS C:\Documents and Settings\Administrator>tracert www.google.com Tracing route to www.l.google.com [209.85.175.104] over a maximum of 30 hops: 1 17 ms 17 ms 17 ms 59-105-193-1.static.seed.net.tw [59.105.193.1] 2 * * 74 ms 139.175.15.62 3 17 ms 17 ms 19 ms R122-9.seed.net.tw [192.72.122.9] 4 24 ms 23 ms 29 ms R58-49.seed.net.tw [139.175.58.49] 5 23 ms 25 ms 24 ms R56-20.seed.net.tw [139.175.56.20] 6 24 ms 24 ms 30 ms R57-133.seed.net.tw [139.175.57.133] 7 24 ms 24 ms 33 ms R59-202.seed.net.tw [139.175.59.202] 8 23 ms 24 ms 29 ms h210-192-72-123.seed.net.tw [192.72.123.210] 9 24 ms 24 ms 24 ms 209.85.243.26 10 25 ms 25 ms 24 ms 209.85.250.101 11 24 ms 25 ms 29 ms 72.14.238.174 12 25 ms 33 ms 35 ms 74.125.184.42 13 25 ms 25 ms 28 ms tc-in-f104.google.com [209.85.175.104] Trace complete. C:\Documents and Settings\Administrator>ping www.google.com Pinging www.l.google.com [209.85.175.104] with 32 bytes of data: Reply from 209.85.175.104: bytes=32 time=25ms TTL=243 Reply from 209.85.175.104: bytes=32 time=24ms TTL=243 Reply from 209.85.175.104: bytes=32 time=25ms TTL=243 Reply from 209.85.175.104: bytes=32 time=25ms TTL=243 Ping statistics for 209.85.175.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 24ms, Maximum = 25ms, Average = 24ms 使用Hinet DNS: C:\Documents and Settings\Administrator>tracert www.google.com Tracing route to www.l.google.com [66.249.89.99] over a maximum of 30 hops: 1 17 ms 17 ms 17 ms 59-105-193-1.static.seed.net.tw [59.105.193.1] 2 * 17 ms 20 ms 139.175.15.62 3 17 ms 22 ms 17 ms R122-202.seed.net.tw [192.72.122.202] 4 61 ms 23 ms 23 ms R58-109.seed.net.tw [139.175.58.109] 5 23 ms 23 ms 23 ms R56-20.seed.net.tw [139.175.56.20] 6 23 ms 24 ms 23 ms R57-94.seed.net.tw [139.175.57.94] 7 24 ms 24 ms 24 ms R59-194.seed.net.tw [139.175.59.194] 8 27 ms 24 ms 24 ms 74.125.51.81 9 52 ms 24 ms 31 ms 209.85.243.26 10 62 ms 60 ms 57 ms 209.85.250.91 11 61 ms 55 ms 54 ms 209.85.241.101 12 55 ms 54 ms 54 ms 216.239.47.54 13 54 ms 66 ms 55 ms jp-in-f99.google.com [66.249.89.99] Trace complete. C:\Documents and Settings\Administrator>ping www.google.com Pinging www.l.google.com [66.249.89.99] with 32 bytes of data: Reply from 66.249.89.99: bytes=32 time=56ms TTL=243 Reply from 66.249.89.99: bytes=32 time=62ms TTL=243 Reply from 66.249.89.99: bytes=32 time=62ms TTL=243 Reply from 66.249.89.99: bytes=32 time=57ms TTL=243 Ping statistics for 66.249.89.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 56ms, Maximum = 62ms, Average = 59ms 此篇文章於 2008-12-15 10:58 AM 被 tvirus 編輯。. 原因: 改編排 |
| 回覆 |
| 會員  | 回覆: 大家有發現最近google變很慢嗎？ 基本上我不認為google會向Hinet收費...Google主要收入是廣告,靠這個收費會餓死的 Hinet鴨霸不是一兩天的事,以hinet的立場來說,可以跟客戶(一般使用者)說因為Google的問題,所以連線速度慢,你看,對其他業者 (例如Y...)速度都很快唷,不要用Google改用Y...吧~ 一旦Google失去Hinet將近7成的用戶(當然有點誇張) 請問他廣告打給誰看? 現在就看龍頭與王者的戰爭誰勝誰負了... |
| 回覆 |
| 會員 | 回覆: 大家有發現最近google變很慢嗎？ Seednet FTTB 固八 使用SeedNet 萬用南部DNS 139.175.10.20 [root@xxxxxx etc]# traceroute www.google.com traceroute to www.google.com (72.14.235.104), 30 hops max, 40 byte packets 1 210-68-16-1.static.seed.net.tw (210.68.16.1) 16.456 ms 16.625 ms 16.598 ms 2 ks23-2.dialup.seed.net.tw (139.175.23.2) 17.290 ms 17.271 ms 17.474 ms 3 R58-109.seed.net.tw (139.175.58.109) 24.443 ms 24.918 ms * 4 R59-19.seed.net.tw (139.175.59.19) 25.369 ms 26.000 ms 26.079 ms 5 R57-37.seed.net.tw (139.175.57.37) 26.304 ms 26.528 ms 27.204 ms 6 R59-202.seed.net.tw (139.175.59.202) 27.906 ms 23.900 ms 22.624 ms 7 h210-192-72-123.seed.net.tw (192.72.123.210) 23.574 ms 23.559 ms 74.125.51.81 (74.125.51.81) 24.038 ms 8 209.85.243.26 (209.85.243.26) 23.995 ms 24.449 ms 24.968 ms 9 209.85.250.103 (209.85.250.103) 26.147 ms 209.85.250.101 (209.85.250.101) 26.130 ms 26.355 ms 10 72.14.238.170 (72.14.238.170) 29.813 ms 29.795 ms 72.14.238.174 (72.14.238.174) 35.244 ms 11 74.125.185.10 (74.125.185.10) 28.483 ms 74.125.184.14 (74.125.184.14) 28.675 ms 74.125.185.10 (74.125.185.10) 26.472 ms 12 tw-in-f104.google.com (72.14.235.104) 26.956 ms 27.160 ms 27.197 ms [root@xxxxxx etc]# ping www.google.com -c 5 PING www.l.google.com (72.14.235.147) 56(84) bytes of data. 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=1 ttl=244 time=26.8 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=2 ttl=244 time=26.4 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=3 ttl=244 time=26.7 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=4 ttl=244 time=24.6 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=5 ttl=244 time=27.1 ms --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 24.656/26.346/27.130/0.874 ms 使用Seednet FTTB DHCP時的DNS(同上一篇) [root@xxxxxx etc]# traceroute www.google.com traceroute to www.google.com (72.14.235.99), 30 hops max, 40 byte packets 1 210-68-16-1.static.seed.net.tw (210.68.16.1) 18.152 ms 18.320 ms 18.539 ms 2 139.175.15.129 (139.175.15.129) 19.225 ms 19.462 ms 19.704 ms 3 R58-153.seed.net.tw (139.175.58.153) 26.651 ms 26.865 ms * 4 R59-19.seed.net.tw (139.175.59.19) 27.333 ms 27.534 ms 27.755 ms 5 R56-190.seed.net.tw (139.175.56.190) 27.725 ms 28.188 ms 28.413 ms 6 R59-194.seed.net.tw (139.175.59.194) 29.125 ms 22.666 ms 24.899 ms 7 h210-192-72-123.seed.net.tw (192.72.123.210) 25.327 ms 74.125.51.81 (74.125.51.81) 26.079 ms 74.125.51.77 (74.125.51.77) 26.058 ms 8 209.85.243.30 (209.85.243.30) 27.014 ms 27.986 ms 27.965 ms 9 209.85.243.23 (209.85.243.23) 28.427 ms 28.920 ms 209.85.243.21 (209.85.243.21) 28.901 ms 10 72.14.238.166 (72.14.238.166) 32.616 ms 72.14.236.98 (72.14.236.98) 32.599 ms 72.14.238.174 (72.14.238.174) 38.286 ms 11 74.125.185.10 (74.125.185.10) 33.266 ms 74.125.184.10 (74.125.184.10) 33.228 ms 74.125.185.10 (74.125.185.10) 26.740 ms 12 tw-in-f99.google.com (72.14.235.99) 25.749 ms 25.464 ms 25.430 ms [root@xxxxxx etc]# ping www.google.com -c 5 PING www.l.google.com (72.14.235.147) 56(84) bytes of data. 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=1 ttl=244 time=26.5 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=2 ttl=244 time=26.2 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=3 ttl=244 time=27.1 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=4 ttl=244 time=24.6 ms 64 bytes from tw-in-f147.google.com (72.14.235.147): icmp_seq=5 ttl=244 time=26.5 ms --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 24.660/26.244/27.166/0.844 ms 使用Hinet DNS(同上一篇) [root@xxxxxx etc]# traceroute www.google.com traceroute to www.google.com (66.249.89.99), 30 hops max, 40 byte packets 1 210-68-16-1.static.seed.net.tw (210.68.16.1) 18.352 ms 18.525 ms 18.756 ms 2 139.175.18.130 (139.175.18.130) 19.470 ms 19.668 ms 19.885 ms 3 R58-109.seed.net.tw (139.175.58.109) 27.129 ms 27.324 ms * 4 R59-19.seed.net.tw (139.175.59.19) 27.787 ms 28.230 ms 28.715 ms 5 R56-190.seed.net.tw (139.175.56.190) 28.685 ms 29.165 ms 29.143 ms 6 R59-194.seed.net.tw (139.175.59.194) 29.843 ms 23.022 ms 25.379 ms 7 74.125.51.77 (74.125.51.77) 25.806 ms 26.034 ms 26.747 ms 8 209.85.243.26 (209.85.243.26) 26.985 ms 27.687 ms 27.915 ms 9 209.85.250.91 (209.85.250.91) 67.417 ms 67.647 ms 67.635 ms 10 209.85.241.101 (209.85.241.101) 58.552 ms 59.012 ms 59.245 ms 11 216.239.47.54 (216.239.47.54) 65.966 ms 65.927 ms 58.961 ms 12 jp-in-f99.google.com (66.249.89.99) 55.491 ms 55.714 ms 55.992 ms [root@xxxxxx etc]# ping www.google.com -c 5 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.5 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=2 ttl=244 time=56.0 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=3 ttl=244 time=56.2 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=4 ttl=244 time=55.0 ms 64 bytes from jp-in-f99.google.com (66.249.89.99): icmp_seq=5 ttl=244 time=55.7 ms --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 55.085/55.723/56.203/0.397 ms 此篇文章於 2008-12-15 11:12 AM 被 tvirus 編輯。. |
| 回覆 |
| 會員 | 回覆: 大家有發現最近google變很慢嗎？ Hinet FTTB固三 使用Hinet DNS(同上上篇) [root@oooooo etc]# traceroute www.google.com traceroute to www.google.com (66.249.89.147), 30 hops max, 60 byte packets 1 60-249-136-254.HINET-IP.hinet.net (60.249.136.254) 16.449 ms 17.286 ms 17.913 ms 2 kh-c76r1.router.hinet.net (168.95.32.218) 16.811 ms 17.261 ms 18.122 ms 3 kh-c12r12.router.hinet.net (220.128.25.194) 76.306 ms kh-c12r12.router.hinet.net (220.128.25.150) 76.279 ms 76.174 ms 4 tp-crs11.router.hinet.net (220.128.2.14) 25.994 ms tp-crs11.router.hinet.net (220.128.1.14) 25.629 ms tp-crs11.router.hinet.net (220.128.2.14) 26.524 ms 5 r33-s2.tp.hinet.net (220.128.1.161) 216.449 ms 216.383 ms r33-s2.tp.hinet.net (220.128.2.161) 216.309 ms 6 211-72-233-89.HINET-IP.hinet.net (211.72.233.89) 164.338 ms 160.332 ms 160.593 ms 7 xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.238) 164.918 ms xe-1-0-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.230) 160.332 ms xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.110) 165.474 ms 8 xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.70) 161.588 ms xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 168.761 ms 168.893 ms 9 xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174) 163.064 ms 161.149 ms 161.513 ms 10 209.85.241.96 (209.85.241.96) 284.856 ms 220.279 ms 220.194 ms 11 216.239.47.54 (216.239.47.54) 169.781 ms 169.722 ms 169.826 ms 12 jp-in-f147.google.com (66.249.89.147) 163.244 ms 169.904 ms 170.042 ms [root@oooooo etc]# ping www.google.com -c 5 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=161 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=4 ttl=237 time=161 ms 64 bytes from jp-in-f147.google.com (66.249.89.147): icmp_seq=5 ttl=234 time=165 ms --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4166ms rtt min/avg/max/mdev = 161.691/164.807/168.152/2.570 ms 使用SeedNet FTTB DHCP配發的DNS(同上上篇) [root@oooooo etc]# traceroute www.google.com traceroute to www.google.com (209.85.175.104), 30 hops max, 60 byte packets 1 60-249-136-254.HINET-IP.hinet.net (60.249.136.254) 16.857 ms 17.485 ms 17.586 ms 2 kh-c76r2.router.hinet.net (168.95.33.222) 17.155 ms 17.301 ms 17.461 ms 3 kh-c12r11.router.hinet.net (220.128.24.150) 17.608 ms kh-c12r12.router.hinet.net (220.128.25.146) 18.254 ms kh-c12r11.router.hinet.net (220.128.24.150) 18.412 ms 4 tp-crs11.router.hinet.net (220.128.2.78) 26.586 ms tp-crs11.router.hinet.net (220.128.1.14) 25.749 ms 26.174 ms 5 r33-s2.tp.hinet.net (220.128.1.161) 27.010 ms r33-s2.tp.hinet.net (220.128.2.161) 27.400 ms r33-s2.tp.hinet.net (220.128.1.161) 27.526 ms 6 211-72-233-89.HINET-IP.hinet.net (211.72.233.89) 171.186 ms 172.147 ms 169.706 ms 7 xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.110) 163.595 ms xe-1-0-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.230) 169.191 ms 169.359 ms 8 xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 164.489 ms xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.70) 170.648 ms xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 164.823 ms 9 xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174) 172.945 ms 173.123 ms 173.504 ms 10 209.85.241.94 (209.85.241.94) 170.657 ms 209.85.241.90 (209.85.241.90) 166.813 ms 166.728 ms 11 209.85.250.90 (209.85.250.90) 229.327 ms 222.503 ms 209.85.250.86 (209.85.250.86) 224.109 ms 12 209.85.243.21 (209.85.243.21) 233.434 ms 244.589 ms 209.85.243.23 (209.85.243.23) 231.607 ms 13 72.14.236.206 (72.14.236.206) 210.707 ms 72.14.238.166 (72.14.238.166) 208.107 ms 72.14.236.210 (72.14.236.210) 207.337 ms 14 74.125.185.42 (74.125.185.42) 219.400 ms 74.125.184.42 (74.125.184.42) 217.818 ms 74.125.184.174 (74.125.184.174) 207.864 ms 15 tc-in-f104.google.com (209.85.175.104) 226.971 ms 192.879 ms 193.522 ms [root@oooooo etc]# ping www.google.com -c 5 PING www.l.google.com (209.85.175.147) 56(84) bytes of data. 64 bytes from tc-in-f147.google.com (209.85.175.147): icmp_seq=1 ttl=234 time=206 ms 64 bytes from tc-in-f147.google.com (209.85.175.147): icmp_seq=2 ttl=234 time=227 ms 64 bytes from tc-in-f147.google.com (209.85.175.147): icmp_seq=3 ttl=234 time=224 ms 64 bytes from tc-in-f147.google.com (209.85.175.147): icmp_seq=4 ttl=235 time=216 ms 64 bytes from tc-in-f147.google.com (209.85.175.147): icmp_seq=5 ttl=235 time=192 ms --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4195ms rtt min/avg/max/mdev = 192.731/213.703/227.466/12.681 ms 使用SeedNet 萬年DNS(同上上篇) [root@oooooo etc]# traceroute www.google.com traceroute to www.google.com (72.14.235.147), 30 hops max, 60 byte packets 1 60-249-136-254.HINET-IP.hinet.net (60.249.136.254) 62.554 ms 63.123 ms 63.515 ms 2 kh-c76r1.router.hinet.net (168.95.32.218) 62.410 ms 62.865 ms 62.965 ms 3 kh-c12r12.router.hinet.net (220.128.25.150) 63.358 ms kh-c12r11.router.hinet.net (220.128.24.194) 63.783 ms kh-c12r12.router.hinet.net (220.128.25.150) 63.914 ms 4 tp-crs11.router.hinet.net (220.128.1.6) 71.761 ms 71.710 ms tp-crs11.router.hinet.net (220.128.2.14) 71.925 ms 5 r33-s2.tp.hinet.net (220.128.2.161) 72.354 ms 72.574 ms * 6 211-72-233-89.HINET-IP.hinet.net (211.72.233.89) 209.971 ms 167.609 ms 164.120 ms 7 xe-2-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.110) 170.296 ms xe-1-0-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.230) 163.657 ms 164.040 ms 8 xe-2-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.70) 165.160 ms xe-1-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.66) 169.821 ms 169.950 ms 9 xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174) 167.945 ms 167.873 ms 167.799 ms 10 209.85.241.94 (209.85.241.94) 166.845 ms 209.85.241.90 (209.85.241.90) 173.990 ms 209.85.241.94 (209.85.241.94) 167.421 ms 11 209.85.250.86 (209.85.250.86) 200.180 ms 209.85.250.90 (209.85.250.90) 195.806 ms 209.85.250.86 (209.85.250.86) 206.485 ms 12 209.85.243.23 (209.85.243.23) 206.373 ms 209.85.243.21 (209.85.243.21) 206.890 ms 209.85.250.101 (209.85.250.101) 205.603 ms 13 72.14.236.210 (72.14.236.210) 221.064 ms 220.177 ms 72.14.236.98 (72.14.236.98) 203.776 ms 14 74.125.184.142 (74.125.184.142) 218.205 ms 74.125.184.138 (74.125.184.138) 204.634 ms 74.125.184.142 (74.125.184.142) 217.225 ms 15 tw-in-f147.google.com (72.14.235.147) 224.625 ms 224.728 ms 216.078 ms [root@oooooo etc]# ping www.google.com -c 5 PING www.l.google.com (72.14.235.99) 56(84) bytes of data. 64 bytes from tw-in-f99.google.com (72.14.235.99): icmp_seq=1 ttl=234 time=240 ms 64 bytes from tw-in-f99.google.com (72.14.235.99): icmp_seq=2 ttl=235 time=191 ms 64 bytes from tw-in-f99.google.com (72.14.235.99): icmp_seq=3 ttl=235 time=208 ms 64 bytes from tw-in-f99.google.com (72.14.235.99): icmp_seq=4 ttl=234 time=228 ms 64 bytes from tw-in-f99.google.com (72.14.235.99): icmp_seq=5 ttl=234 time=217 ms --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4221ms rtt min/avg/max/mdev = 191.727/217.390/240.825/16.819 ms 就算Seednet線路指到了日本Google伺服器,還是比Hinet快.... 總結: 請大家去用Hinet吧  (別來搶) 此篇文章於 2008-12-15 09:14 PM 被 tvirus 編輯。. |
| 回覆 |
| 會員 | 回覆: 大家有發現最近google變很慢嗎？ 晚上用Hinet FTTB 10M/2M ping google都大於300ms以上 |
| 回覆 |
| 人工智能80 | 回覆: 大家有發現最近google變很慢嗎？ 如果這次google屈服於hinet 以前我常說現在我們落後日本五年 可能要改成即將落後日本十年以上... |
| 回覆 |
| 明誠科技小峰 | 回覆: 大家有發現最近google變很慢嗎？ 不知道如果HINET用戶把DNS指向別的ISP速度會不會變快. |
| 回覆 |
| XML | RSS 2.0 | RSS |
本論壇所有文章僅代表留言者個人意見，並不代表本站之立場，討論區以「即時留言」方式運作，故無法完全監察所有即時留言，若您發現文章可能有異議，請 email :[email protected] 處理。
