| 會員  | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 Hinet 10m/2m(參考即可..固定跟浮動差很多= = |
| 回覆 |
| 會員  | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 來看看慢的吧XD HINET 光纖 Tracing route to cm-ote235.kddnet.ad.jp [59.128.7.23] over a maximum of 30 hops: 1 12 ms 12 ms 12 ms 218-174-32-254.dynamic.hinet.net [218.174.32.254 ] 2 12 ms 11 ms 12 ms tn-st-c6r1.router.hinet.net [168.95.54.74] 3 11 ms 12 ms 11 ms 220-128-26-150.HINET-IP.hinet.net [220.128.26.15 0] 4 20 ms 19 ms 19 ms kh-c12r11.router.hinet.net [220.128.24.30] 5 19 ms 19 ms 19 ms 220-128-1-206.HINET-IP.hinet.net [220.128.1.206] 6 19 ms 19 ms 20 ms tp-jpr3.router.hinet.net [220.128.1.186] 7 531 ms 532 ms 541 ms 59.128.15.45 8 545 ms 546 ms 537 ms otecbb103.kddnet.ad.jp [124.211.33.65] 9 543 ms 538 ms 532 ms otejbb204.kddnet.ad.jp [59.128.4.169] 10 573 ms 569 ms 585 ms cm-ote235.kddnet.ad.jp [59.128.7.23] Trace complete. |
| 回覆 |
| 會員 | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 hinet 固3 ip 4m/1m   |
| 回覆 |
| 會員 | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 再附上 seednet 固3 ip 4m/1m tracert不知為何,都是 timeout...,但明明 ping的到   |
| 回覆 |
| 會員  | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 Hinet 多機型固定 2M at AM 2:00 追蹤 cm-ote235.kddnet.ad.jp [59.128.7.23] 的路由: 1 42 ms 42 ms 42 ms 59-124-124-xxx.HINET-IP.hinet.net [59.124.124.254] 2 41 ms 42 ms 41 ms tp-e4-c76r2.router.hinet.net [168.95.85.226] 3 41 ms 41 ms 40 ms tp-e4-c12r1.router.hinet.net [211.22.36.42] 4 42 ms 42 ms 42 ms tp-crs11.router.hinet.net [220.128.1.110] 5 42 ms 42 ms 42 ms tp-jpr3.router.hinet.net [220.128.1.186] 6 81 ms 81 ms 81 ms 203.181.102.225 7 101 ms 105 ms 101 ms otecbb103.kddnet.ad.jp [124.211.33.65] 8 85 ms 80 ms 84 ms otejbb204.kddnet.ad.jp [203.181.96.138] 9 102 ms 116 ms 108 ms cm-ote235.kddnet.ad.jp [59.128.7.23] - - - - - - - - - - - - - - - - - - - - Ping 59.128.7.23 具有 32 位元組的資料: 回覆自 59.128.7.23: 位元組=32 時間=97ms TTL=56 回覆自 59.128.7.23: 位元組=32 時間=98ms TTL=56 回覆自 59.128.7.23: 位元組=32 時間=103ms TTL=56 回覆自 59.128.7.23: 位元組=32 時間=95ms TTL=56 59.128.7.23 的 Ping 統計資料: 封包: 已傳送 = 4，已收到 = 4, 已遺失 = 0 (0% 遺失)， 大約的來回時間 (毫秒): 最小值 = 95ms，最大值 = 103ms，平均 = 98ms |
| 回覆 |
| 會員  | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 公司中華電信 FTTB 2M對稱光纖專業型 64 bytes from 59.128.7.23: icmp_seq=1 ttl=56 time=51.3 ms 64 bytes from 59.128.7.23: icmp_seq=2 ttl=56 time=46.7 ms 64 bytes from 59.128.7.23: icmp_seq=3 ttl=56 time=52.2 ms 64 bytes from 59.128.7.23: icmp_seq=4 ttl=56 time=47.9 ms 64 bytes from 59.128.7.23: icmp_seq=5 ttl=56 time=56.5 ms 64 bytes from 59.128.7.23: icmp_seq=6 ttl=56 time=51.9 ms 64 bytes from 59.128.7.23: icmp_seq=7 ttl=56 time=50.0 ms 64 bytes from 59.128.7.23: icmp_seq=8 ttl=56 time=54.5 ms 64 bytes from 59.128.7.23: icmp_seq=9 ttl=56 time=47.5 ms 64 bytes from 59.128.7.23: icmp_seq=10 ttl=56 time=57.6 ms 64 bytes from 59.128.7.23: icmp_seq=11 ttl=56 time=50.2 ms 64 bytes from 59.128.7.23: icmp_seq=12 ttl=56 time=52.8 ms 64 bytes from 59.128.7.23: icmp_seq=13 ttl=56 time=61.0 ms 64 bytes from 59.128.7.23: icmp_seq=14 ttl=56 time=47.9 ms 64 bytes from 59.128.7.23: icmp_seq=15 ttl=56 time=61.0 ms 64 bytes from 59.128.7.23: icmp_seq=16 ttl=56 time=57.5 ms 64 bytes from 59.128.7.23: icmp_seq=17 ttl=56 time=50.3 ms 64 bytes from 59.128.7.23: icmp_seq=18 ttl=56 time=57.3 ms 64 bytes from 59.128.7.23: icmp_seq=19 ttl=56 time=48.2 ms 64 bytes from 59.128.7.23: icmp_seq=20 ttl=56 time=59.3 ms 64 bytes from 59.128.7.23: icmp_seq=21 ttl=56 time=57.5 ms 64 bytes from 59.128.7.23: icmp_seq=22 ttl=56 time=47.0 ms 64 bytes from 59.128.7.23: icmp_seq=23 ttl=56 time=58.5 ms 64 bytes from 59.128.7.23: icmp_seq=24 ttl=56 time=50.5 ms 64 bytes from 59.128.7.23: icmp_seq=25 ttl=56 time=46.5 ms --- 59.128.7.23 ping statistics --- 25 packets transmitted, 25 received, 0% packet loss, time 23999ms rtt min/avg/max/mdev = 46.523/52.911/61.066/4.701 ms 公司中華電信ADSL 6M/640KB 固三IP 64 bytes from 59.128.7.23: icmp_seq=1 ttl=56 time=78.6 ms 64 bytes from 59.128.7.23: icmp_seq=2 ttl=56 time=87.0 ms 64 bytes from 59.128.7.23: icmp_seq=3 ttl=56 time=79.1 ms 64 bytes from 59.128.7.23: icmp_seq=4 ttl=56 time=89.0 ms 64 bytes from 59.128.7.23: icmp_seq=5 ttl=56 time=80.1 ms 64 bytes from 59.128.7.23: icmp_seq=6 ttl=56 time=90.3 ms 64 bytes from 59.128.7.23: icmp_seq=7 ttl=56 time=82.1 ms 64 bytes from 59.128.7.23: icmp_seq=8 ttl=56 time=80.2 ms 64 bytes from 59.128.7.23: icmp_seq=9 ttl=56 time=83.9 ms 64 bytes from 59.128.7.23: icmp_seq=10 ttl=56 time=78.8 ms 64 bytes from 59.128.7.23: icmp_seq=11 ttl=56 time=85.5 ms 64 bytes from 59.128.7.23: icmp_seq=12 ttl=56 time=78.6 ms 64 bytes from 59.128.7.23: icmp_seq=13 ttl=56 time=87.5 ms 64 bytes from 59.128.7.23: icmp_seq=14 ttl=56 time=79.1 ms 64 bytes from 59.128.7.23: icmp_seq=15 ttl=56 time=126 ms 64 bytes from 59.128.7.23: icmp_seq=16 ttl=56 time=86.6 ms 64 bytes from 59.128.7.23: icmp_seq=17 ttl=56 time=91.3 ms 64 bytes from 59.128.7.23: icmp_seq=18 ttl=56 time=87.4 ms 64 bytes from 59.128.7.23: icmp_seq=19 ttl=56 time=78.8 ms 64 bytes from 59.128.7.23: icmp_seq=20 ttl=56 time=86.0 ms 64 bytes from 59.128.7.23: icmp_seq=21 ttl=56 time=79.3 ms 64 bytes from 59.128.7.23: icmp_seq=22 ttl=56 time=88.0 ms 64 bytes from 59.128.7.23: icmp_seq=23 ttl=56 time=81.1 ms 64 bytes from 59.128.7.23: icmp_seq=24 ttl=56 time=90.9 ms 64 bytes from 59.128.7.23: icmp_seq=25 ttl=56 time=81.9 ms ^C --- 59.128.7.23 ping statistics --- 25 packets transmitted, 25 received, 0% packet loss, time 24505ms rtt min/avg/max/mdev = 78.609/85.536/126.022/9.297 ms 家中Seednet 10M/2M DHCP的固定IP 64 bytes from 59.128.7.23: icmp_seq=1 ttl=56 time=62.5 ms 64 bytes from 59.128.7.23: icmp_seq=2 ttl=56 time=55.9 ms 64 bytes from 59.128.7.23: icmp_seq=3 ttl=56 time=65.9 ms 64 bytes from 59.128.7.23: icmp_seq=4 ttl=56 time=58.6 ms 64 bytes from 59.128.7.23: icmp_seq=5 ttl=56 time=56.1 ms 64 bytes from 59.128.7.23: icmp_seq=6 ttl=56 time=62.6 ms 64 bytes from 59.128.7.23: icmp_seq=7 ttl=56 time=55.9 ms 64 bytes from 59.128.7.23: icmp_seq=8 ttl=56 time=66.4 ms 64 bytes from 59.128.7.23: icmp_seq=9 ttl=56 time=58.9 ms 64 bytes from 59.128.7.23: icmp_seq=10 ttl=56 time=70.0 ms 64 bytes from 59.128.7.23: icmp_seq=11 ttl=56 time=80.9 ms 64 bytes from 59.128.7.23: icmp_seq=12 ttl=56 time=56.2 ms 64 bytes from 59.128.7.23: icmp_seq=13 ttl=56 time=67.0 ms 64 bytes from 59.128.7.23: icmp_seq=14 ttl=56 time=78.2 ms 64 bytes from 59.128.7.23: icmp_seq=15 ttl=56 time=71.2 ms 64 bytes from 59.128.7.23: icmp_seq=16 ttl=56 time=64.0 ms 64 bytes from 59.128.7.23: icmp_seq=17 ttl=56 time=56.5 ms 64 bytes from 59.128.7.23: icmp_seq=18 ttl=56 time=67.2 ms 64 bytes from 59.128.7.23: icmp_seq=19 ttl=56 time=79.2 ms 64 bytes from 59.128.7.23: icmp_seq=20 ttl=56 time=56.5 ms 64 bytes from 59.128.7.23: icmp_seq=21 ttl=56 time=64.3 ms 64 bytes from 59.128.7.23: icmp_seq=22 ttl=56 time=56.8 ms 64 bytes from 59.128.7.23: icmp_seq=23 ttl=56 time=67.9 ms 64 bytes from 59.128.7.23: icmp_seq=24 ttl=56 time=61.5 ms 64 bytes from 59.128.7.23: icmp_seq=25 ttl=56 time=55.8 ms ^C --- 59.128.7.23 ping statistics --- 25 packets transmitted, 25 received, 0% packet loss, time 24384ms rtt min/avg/max/mdev = 55.842/63.892/80.982/7.499 ms 均在使用中測試 |
| 回覆 |
| 會員 | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 so-net 光纖 10M/2M PPPoe 1固+7動 ip 剛測試,冋時有用bt抓檔中..看來品質還不錯 供您參考 |
| 回覆 |
| 會員 | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 Seednet 2M/256 (基隆) Reply from 59.128.7.23: bytes=32 time=61ms TTL=58 Reply from 59.128.7.23: bytes=32 time=70ms TTL=58 Reply from 59.128.7.23: bytes=32 time=62ms TTL=58 Reply from 59.128.7.23: bytes=32 time=61ms TTL=58 Reply from 59.128.7.23: bytes=32 time=68ms TTL=58 Reply from 59.128.7.23: bytes=32 time=61ms TTL=58 Reply from 59.128.7.23: bytes=32 time=72ms TTL=58 Reply from 59.128.7.23: bytes=32 time=64ms TTL=58 Reply from 59.128.7.23: bytes=32 time=61ms TTL=58 Reply from 59.128.7.23: bytes=32 time=68ms TTL=58 Reply from 59.128.7.23: bytes=32 time=61ms TTL=58 Reply from 59.128.7.23: bytes=32 time=72ms TTL=58 Reply from 59.128.7.23: bytes=32 time=64ms TTL=58 Reply from 59.128.7.23: bytes=32 time=62ms TTL=58 Reply from 59.128.7.23: bytes=32 time=69ms TTL=58 Reply from 59.128.7.23: bytes=32 time=62ms TTL=58 Reply from 59.128.7.23: bytes=32 time=60ms TTL=58 Reply from 59.128.7.23: bytes=32 time=68ms TTL=58 Reply from 59.128.7.23: bytes=32 time=61ms TTL=58 Ping statistics for 59.128.7.23: Packets: Sent = 53, Received = 53, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 60ms, Maximum = 72ms, Average = 64ms Tracing route to cm-ote235.kddnet.ad.jp [59.128.7.23] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 29 ms 27 ms 28 ms sw169-53-1.adsl.seed.net.tw [221.169.53.1] 3 28 ms 27 ms 27 ms sj235-130.dialup.seed.net.tw [139.175.235.130] 4 27 ms 28 ms 27 ms R56-190.seed.net.tw [139.175.56.190] 5 60 ms 59 ms 59 ms R58-82.seed.net.tw [139.175.58.82] 6 60 ms 59 ms 59 ms AS2516-2.ix.jpix.ad.jp [210.171.224.94] 7 64 ms 72 ms 71 ms cm-ote235.kddnet.ad.jp [59.128.7.23] |
| 回覆 |
| 會員 | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 最後我辦了SEEDNET 不過 真的很失望,不能達到3Xms(台固很多朋友都有3xms) C:\>tracert 124.211.52.99 Tracing route to 124.211.52.099.mgame.co.jp [124.211.52.99] over a maximum of 30 hops: 1 27 ms 30 ms 30 ms 123-204-42-1.static.seed.net.tw [123.204.42.1] 2 30 ms 30 ms 30 ms sh39-189.seed.net.tw [139.175.39.189] 3 30 ms 30 ms 30 ms R121-98.seed.net.tw [192.72.121.98] 4 30 ms 30 ms 30 ms R58-189.seed.net.tw [139.175.58.189] 5 30 ms 30 ms 30 ms R59-19.seed.net.tw [139.175.59.19] 6 30 ms 30 ms 30 ms R56-190.seed.net.tw [139.175.56.190] 7 62 ms 61 ms 61 ms R58-82.seed.net.tw [139.175.58.82] 8 61 ms 61 ms 61 ms AS2516-2.ix.jpix.ad.jp [210.171.224.94] 9 62 ms 62 ms 61 ms cm-ote235.kddnet.ad.jp [59.128.7.23] C:\>PING 59.128.7.23 -t Pinging 59.128.7.23 with 32 bytes of data: Reply from 59.128.7.23: bytes=32 time=53ms TTL=56 Reply from 59.128.7.23: bytes=32 time=63ms TTL=56 Reply from 59.128.7.23: bytes=32 time=56ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Reply from 59.128.7.23: bytes=32 time=56ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Reply from 59.128.7.23: bytes=32 time=58ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Reply from 59.128.7.23: bytes=32 time=59ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Reply from 59.128.7.23: bytes=32 time=61ms TTL=56 Reply from 59.128.7.23: bytes=32 time=52ms TTL=56 Reply from 59.128.7.23: bytes=32 time=63ms TTL=56 Reply from 59.128.7.23: bytes=32 time=55ms TTL=56 Reply from 59.128.7.23: bytes=32 time=50ms TTL=56 Reply from 59.128.7.23: bytes=32 time=57ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Reply from 59.128.7.23: bytes=32 time=58ms TTL=56 Reply from 59.128.7.23: bytes=32 time=50ms TTL=56 Reply from 59.128.7.23: bytes=32 time=60ms TTL=56 Reply from 59.128.7.23: bytes=32 time=52ms TTL=56 Reply from 59.128.7.23: bytes=32 time=62ms TTL=56 Reply from 59.128.7.23: bytes=32 time=54ms TTL=56 Reply from 59.128.7.23: bytes=32 time=65ms TTL=56 Reply from 59.128.7.23: bytes=32 time=55ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Reply from 59.128.7.23: bytes=32 time=58ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Reply from 59.128.7.23: bytes=32 time=60ms TTL=56 Reply from 59.128.7.23: bytes=32 time=51ms TTL=56 Ping statistics for 59.128.7.23: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 65ms, Average = 55ms 問他們工程部 給我回應是 ping和tracert只能當參考 明明就是事實不是嗎?不曉得有無高手指導我一下 要如何說明 工程部那邊才知道怎麼去設定我的路由 |
| 回覆 |
| 苦命人 | 回覆: 【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大 hinet 固3 10m/2m Reply from 59.128.7.23: bytes=32 time=60ms TTL=55 Reply from 59.128.7.23: bytes=32 time=73ms TTL=55 Reply from 59.128.7.23: bytes=32 time=66ms TTL=55 Reply from 59.128.7.23: bytes=32 time=69ms TTL=55 Reply from 59.128.7.23: bytes=32 time=75ms TTL=55 Reply from 59.128.7.23: bytes=32 time=69ms TTL=55 Reply from 59.128.7.23: bytes=32 time=76ms TTL=55 Reply from 59.128.7.23: bytes=32 time=71ms TTL=55 Reply from 59.128.7.23: bytes=32 time=83ms TTL=55 Reply from 59.128.7.23: bytes=32 time=68ms TTL=55 Reply from 59.128.7.23: bytes=32 time=66ms TTL=55 Reply from 59.128.7.23: bytes=32 time=63ms TTL=55 Reply from 59.128.7.23: bytes=32 time=65ms TTL=55 Reply from 59.128.7.23: bytes=32 time=71ms TTL=55 Reply from 59.128.7.23: bytes=32 time=66ms TTL=55 Reply from 59.128.7.23: bytes=32 time=66ms TTL=55 Reply from 59.128.7.23: bytes=32 time=55ms TTL=55 Reply from 59.128.7.23: bytes=32 time=73ms TTL=55 Reply from 59.128.7.23: bytes=32 time=59ms TTL=55 Reply from 59.128.7.23: bytes=32 time=64ms TTL=55 Reply from 59.128.7.23: bytes=32 time=66ms TTL=55 Reply from 59.128.7.23: bytes=32 time=76ms TTL=55 Reply from 59.128.7.23: bytes=32 time=73ms TTL=55 Reply from 59.128.7.23: bytes=32 time=66ms TTL=55 Reply from 59.128.7.23: bytes=32 time=72ms TTL=55 Reply from 59.128.7.23: bytes=32 time=70ms TTL=55 Reply from 59.128.7.23: bytes=32 time=83ms TTL=55 Reply from 59.128.7.23: bytes=32 time=86ms TTL=55 Reply from 59.128.7.23: bytes=32 time=77ms TTL=55 Reply from 59.128.7.23: bytes=32 time=74ms TTL=55 Reply from 59.128.7.23: bytes=32 time=69ms TTL=55 Reply from 59.128.7.23: bytes=32 time=57ms TTL=55 Reply from 59.128.7.23: bytes=32 time=65ms TTL=55 Reply from 59.128.7.23: bytes=32 time=58ms TTL=55 Reply from 59.128.7.23: bytes=32 time=68ms TTL=55 Reply from 59.128.7.23: bytes=32 time=65ms TTL=55 Reply from 59.128.7.23: bytes=32 time=78ms TTL=55 Ping statistics for 59.128.7.23: Packets: Sent = 374, Received = 374, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 121ms, Average = 76ms C:\Documents and Settings\Administrator>tracert 59.128.7.23 Tracing route to cm-ote235.kddnet.ad.jp [59.128.7.23] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 2 17 ms 13 ms 15 ms 59-120-3-254.HINET-IP.hinet.net [59.120.3.254] 3 15 ms 13 ms 14 ms 172.16.1.1 4 13 ms 19 ms 16 ms tp-s2-c76r5.router.hinet.net [168.95.82.202] 5 13 ms 17 ms 13 ms tp-crs11.router.hinet.net [220.128.2.230] 6 26 ms 15 ms 15 ms r03-s2.tp.hinet.net [220.128.2.190] 7 68 ms 82 ms 75 ms 59.128.15.113 8 74 ms 85 ms 78 ms otecbb103.kddnet.ad.jp [124.211.33.1] 9 91 ms 77 ms 72 ms otejbb203.kddnet.ad.jp [59.128.4.61] 10 97 ms 86 ms 90 ms cm-ote235.kddnet.ad.jp [59.128.7.23] Trace complete. C:\Documents and Settings\Administrator> |
| 回覆 |
| XML | RSS 2.0 | RSS |
本論壇所有文章僅代表留言者個人意見，並不代表本站之立場，討論區以「即時留言」方式運作，故無法完全監察所有即時留言，若您發現文章可能有異議，請 email :[email protected] 處理。
