【問題】想請教各位PING日本的反應時間多少?尤其是SEEDNET的大大

小弟喜歡玩網路遊戲 SO-NET和台固也歡迎測試 因為我知道這三家連日本很快
不過台版的該遊戲倒閉了
跑去玩日版伺服器
很要求PING的速率

該IP為59.128.7.23
可以麻煩各位測個速給在下嗎?
因為考慮要辦哪家ISP
HINET就真的不用了 因為連外PING的速率會吐血
ping 59.128.7.23 -t
謝謝

個人目前使用 光特快(暫時)它是CABLE
目前所在 新竹市 南大路這裡
用ping的
[IMG]http://a.imagehost.org/0258/1.jpg[/IMG]
用tracert的
[IMG]http://a.imagehost.org/0604/2.jpg[/IMG]

樓下有幾位大大 沒有說明一下哪個ISP (最好加地區)
有空麻煩補充一下嚕

Adam Kuo那位大大的反應時間33~34 ms
你家住hinet骨幹嗎... 路徑有seed也有hinet....
我之前注公司宿舍用hinet優先權線路1M/4M
PING起來也是76ms...

第二頁 第一位大大是hinet的
不過根據我之前使用狀況
在國內階段 就不知道搞啥比其他isp多 1x 2xms
其他isp就是各位數 x1xms
出了國 hinet很多區域 例如日本馬上1兩百 (線上遊戲十幾個人,目前有在玩的都把hinet開除了)
那位大大算在不錯的區域了

第二頁第二位大大謝謝你
終於有人願意證實hinet連外的龜速了
其他isp連外全國幾乎都一樣
hinet就特定地區快而已

今日第二頁又多了兩三位HINET用戶提供資料
TRACERT會TIME OUT是因為該節點伺服器不想顯示出來
所以會TIME
今日的結論 HINET我想還是特殊地段和特殊的線路才會快
我還是比較期待SO-NET和SEEDNET還有台固的大大
因為據說 有3*的反應速度+.+...

[IMG]http://a.imagehost.org/0844/cable.jpg[/IMG]
東森 Cacle 8M/512k

這數值是在同時跑 eMule、uTorrent 的環境下測得。

參考樓下石兄的做法補 PO 一張：
[IMG]http://a.imagehost.org/0412/cable2.jpg[/IMG]

台固 10m cable

C:\>tracert 59.128.7.23

Tracing route to cm-ote235.kddnet.ad.jp [59.128.7.23]
over a maximum of 30 hops:

1 7 ms 7 ms 9 ms 10.20.0.254
2 9 ms 7 ms 13 ms 192.168.10.12
3 11 ms 7 ms 11 ms 60-198-191-253.static.tfn.net.tw [60.198.191.253]
4 8 ms 7 ms 7 ms 60-199-7-149.static.tfn.net.tw [60.199.7.149]
5 13 ms 25 ms 15 ms 60-199-4-109.static.tfn.net.tw [60.199.4.109]
6 22 ms 14 ms 13 ms 60-199-6-70.static.tfn.net.tw [60.199.6.70]
7 13 ms 14 ms 12 ms 60-199-6-230.static.tfn.net.tw [60.199.6.230]
8 19 ms 13 ms 12 ms ge-3-1-0.gw3.tpe3.asianetcom.net [203.192.170.101]
9 13 ms 13 ms 16 ms ge-3-0-0-0.gw2.tpe3.asianetcom.net [202.147.24.77]
10 53 ms 59 ms 49 ms po3-2.cr1.nrt1.asianetcom.net [202.147.49.66]
11 49 ms 65 ms 55 ms te3-1.gw2.nrt2.asianetcom.net [202.147.0.86]
12 57 ms 54 ms 53 ms KDDI.Te4-1.gw2.nrt2.asianetcom.net [203.192.129.62]
13 51 ms 52 ms 50 ms otecbb104.kddnet.ad.jp [124.211.33.3]
14 51 ms 53 ms 51 ms otejbb203.kddnet.ad.jp [203.181.96.142]
15 52 ms 54 ms 51 ms cm-ote235.kddnet.ad.jp [59.128.7.23]

Trace complete.

SEEDNET
[url]http://trace.seed.net.tw/cgi-bin/trace.pl[/url]
traceroute to 59.128.7.23 (59.128.7.23), 25 hops max, 44 byte packets
1 139.175.239.251 (139.175.239.251) 6.243 ms 2.236 ms 0.646 ms
2 R56-190 (139.175.56.190) 0.352 ms 0.344 ms 0.326 ms
3 R58-82 (139.175.58.82) 31.566 ms 31.460 ms 31.569 ms
4 AS2516-2.ix.jpix.ad.jp (210.171.224.94) 215.995 ms 215.735 ms 230.355 ms
5 cm-ote235.kddnet.ad.jp (59.128.7.23) 216.417 ms 218.228 ms 218.904 ms

Seednet 光纖 10M/2M
===========================================
Pinging 59.128.7.23 with 32 bytes of data:

Reply from 59.128.7.23: bytes=32 time=47ms TTL=59
Reply from 59.128.7.23: bytes=32 time=52ms TTL=59
Reply from 59.128.7.23: bytes=32 time=46ms TTL=59
Reply from 59.128.7.23: bytes=32 time=55ms TTL=59
Reply from 59.128.7.23: bytes=32 time=47ms TTL=59
Reply from 59.128.7.23: bytes=32 time=56ms TTL=59
Reply from 59.128.7.23: bytes=32 time=48ms TTL=59
Reply from 59.128.7.23: bytes=32 time=59ms TTL=59
Reply from 59.128.7.23: bytes=32 time=51ms TTL=59
Reply from 59.128.7.23: bytes=32 time=46ms TTL=59
Reply from 59.128.7.23: bytes=32 time=52ms TTL=59
Reply from 59.128.7.23: bytes=32 time=46ms TTL=59
Reply from 59.128.7.23: bytes=32 time=54ms TTL=59
Reply from 59.128.7.23: bytes=32 time=46ms TTL=59
Reply from 59.128.7.23: bytes=32 time=57ms TTL=59
Reply from 59.128.7.23: bytes=32 time=48ms TTL=59
Reply from 59.128.7.23: bytes=32 time=59ms TTL=59
Reply from 59.128.7.23: bytes=32 time=50ms TTL=59

===========================================

C:\>tracert 59.128.7.23

Tracing route to cm-ote235.kddnet.ad.jp [59.128.7.23]
over a maximum of 30 hops:

1 13 ms 13 ms 13 ms tp240-7.dialup.seed.net.tw [139.175.XXX.XXX]
2 14 ms 14 ms 13 ms sj235-66.dialup.seed.net.tw [139.175.235.66]
3 14 ms 13 ms 14 ms R56-190.seed.net.tw [139.175.56.190]
4 45 ms 44 ms 44 ms R58-82.seed.net.tw [139.175.58.82]
5 64 ms 203 ms 211 ms AS2516-2.ix.jpix.ad.jp [210.171.224.94]
6 52 ms 54 ms 53 ms cm-ote235.kddnet.ad.jp [59.128.7.23]

Trace complete.

===========================================
報告完畢

1 <1 ms <1 ms <1 ms my.router [10.153.52.10]
2 2 ms 1 ms 1 ms 218-160-32-254.dynamic.hinet.net [218.160.32.254]
3 * 1 ms 1 ms sj235-66.dialup.seed.net.tw [139.175.235.66]
4 1 ms 1 ms 1 ms tp-crs11.router.hinet.net [220.128.3.14]
5 1 ms 33 ms 1 ms tp-jpr3.router.hinet.net [220.128.1.178]
6 33 ms 201 ms 34 ms AS2516-2.ix.jpix.ad.jp [210.171.224.94]
7 224 ms 38 ms 223 ms otecbb103.kddnet.ad.jp [124.211.33.65]
8 34 ms 209 ms 34 ms otejbb204.kddnet.ad.jp [59.128.7.2]

C:\Users\USER>ping 59.128.7.23 -t

Ping 59.128.7.23 具有 32 位元組的資料:
回覆自 59.128.7.23: 位元組=32 時間=73ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=73ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=79ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=73ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=82ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=72ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=81ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=73ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=83ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=76ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=72ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=78ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=73ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=78ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=75ms TTL=56
回覆自 59.128.7.23: 位元組=32 時間=81ms TTL=56

59.128.7.23 的 Ping 統計資料:
封包: 已傳送 = 16，已收到 = 16, 已遺失 = 0 (0% 遺失)，
大約的來回時間 (毫秒):
最小值 = 72ms，最大值 = 83ms，平均 = 76ms

樓主還真慘，明明和我一樣都是同一家的產品，結果經過的 Router 數量卻差這麼多，沒想到樓主要經過12個才能到目的地（ISP 不算的話），我才經過4個，也難怪樓主會覺得慢了。（我是台北北投的光特快）

樓主真要參考，應該是看 a-bin 兄的數據，他經過的 Router 數量最少，時間最短。

高雄市SEEDNET 10M/2M光纖(固3)
================= ping ====================
Pinging 59.128.7.23 with 32 bytes of data:
Reply from 59.128.7.23: bytes=32 time=58ms TTL=57
Reply from 59.128.7.23: bytes=32 time=66ms TTL=57
Reply from 59.128.7.23: bytes=32 time=64ms TTL=57
Reply from 59.128.7.23: bytes=32 time=68ms TTL=57

Ping statistics for 59.128.7.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 68ms, Average = 64ms
=======================================

================ Trace ===================
Tracing route to cm-ote235.kddnet.ad.jp [59.128.7.23]
over a maximum of 30 hops:
1 19 ms 19 ms 19 ms h203-67-134-1.host-dial.seed.net.tw [203.67.134.1]
2 20 ms 20 ms 19 ms 139.175.22.2
3 24 ms 24 ms 24 ms R58-109.seed.net.tw [139.175.58.109]
4 25 ms 25 ms 25 ms R56-20.seed.net.tw [139.175.56.20]
5 24 ms 24 ms 24 ms R57-94.seed.net.tw [139.175.57.94]
6 55 ms 55 ms 55 ms R58-82.seed.net.tw [139.175.58.82]
7 58 ms 56 ms 72 ms AS2516-2.ix.jpix.ad.jp [210.171.224.94]
8 67 ms 59 ms 65 ms cm-ote235.kddnet.ad.jp [59.128.7.23]

Trace complete.

台固CM 8M
======================================
Reply from 59.128.7.23: bytes=32 time=51ms TTL=50
Reply from 59.128.7.23: bytes=32 time=75ms TTL=50
Reply from 59.128.7.23: bytes=32 time=48ms TTL=50
Reply from 59.128.7.23: bytes=32 time=58ms TTL=50
Reply from 59.128.7.23: bytes=32 time=50ms TTL=50
Reply from 59.128.7.23: bytes=32 time=57ms TTL=50
Reply from 59.128.7.23: bytes=32 time=49ms TTL=50

Ping statistics for 59.128.7.23:
Packets: Sent = 57, Received = 57, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 75ms, Average = 54ms
======================================
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 WHR-G54S.Router [192.168.1.1]
2 7 ms 7 ms 8 ms 10.13.0.1
3 7 ms 8 ms 8 ms 61-56-191-113.ubbn.net [61.56.191.113]
4 7 ms 8 ms 10 ms 61-31-252-1.static.tfn.net.tw [61.31.252.1]
5 9 ms 15 ms 7 ms 60-199-6-105.static.tfn.net.tw [60.199.6.105]
6 8 ms 7 ms 8 ms 60-199-6-70.static.tfn.net.tw [60.199.6.70]
7 9 ms 10 ms 9 ms 60-199-6-210.static.tfn.net.tw [60.199.6.210]
8 10 ms 11 ms 9 ms TFN.csgw1.hkg3.asianetcom.net [122.152.186.129]

9 30 ms 9 ms 9 ms ge-3-0-0-0.gw2.tpe3.asianetcom.net [202.147.24.7
7]
10 57 ms 47 ms 46 ms po9-2.cr1.nrt1.asianetcom.net [202.147.49.122]
11 46 ms 49 ms 45 ms te3-1.gw2.nrt2.asianetcom.net [202.147.0.86]
12 57 ms 53 ms 54 ms KDDI.Te4-1.gw2.nrt2.asianetcom.net [203.192.129.
62]
13 46 ms 46 ms 45 ms otecbb104.kddnet.ad.jp [124.211.33.3]
14 49 ms 47 ms 46 ms otejbb203.kddnet.ad.jp [59.128.4.69]
15 51 ms 54 ms 55 ms cm-ote235.kddnet.ad.jp [59.128.7.23]

Trace complete.

我這是光特快CM （台北），10m/1M; 時間 AM 11
[SIZE="2"][COLOR="DarkOrchid"]追蹤 cm-ote235.kddnet.ad.jp [59.128.7.23] 的路由:

1 <1 ms <1 ms <1 ms 2910G.kbronet.net [192.168.1.1]
2 10 ms 10 ms 9 ms 10.71.0.1
3 12 ms 10 ms 11 ms 211-76-116-1.static.kbronet.com.tw [211.76.116.1]
4 12 ms 9 ms 17 ms h18-192-72-108.seed.net.tw [192.72.108.18]
5 23 ms 9 ms 12 ms R57-37.seed.net.tw [139.175.57.37]
6 42 ms 44 ms 42 ms R58-38.seed.net.tw [139.175.58.38]
7 44 ms 41 ms 42 ms AS2516-2.ix.jpix.ad.jp [210.171.224.94]
8 46 ms 53 ms 54 ms cm-ote235.kddnet.ad.jp [59.128.7.23]
- - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - -
回覆自 59.128.7.23: 位元組=32 時間=57ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=49ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=44ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=53ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=44ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=54ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=46ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=42ms TTL=57
回覆自 59.128.7.23: 位元組=32 時間=49ms TTL=57

59.128.7.23 的 Ping 統計資料:
封包: 已傳送 = 83，已收到 = 83, 已遺失 = 0 (0% 遺失)，
大約的來回時間 (毫秒):
最小值 = 41ms，最大值 = 68ms，平均 = 49ms[/COLOR][/SIZE]
＝ = = = = = = = = = = = = =
[url]http://trace.seed.net.tw/cgi-bin/trace.pl[/url] 【SEEDNET 網路測試工具 traceroute】 at PM 17:20
traceroute to 59.128.7.23 (59.128.7.23), 25 hops max, 44 byte packets
[SIZE="2"][COLOR="SeaGreen"]1 139.175.55.3 (139.175.55.3) 0.466 ms 0.371 ms 0.329 ms
2 R57-133 (139.175.57.133) 0.360 ms 0.364 ms 0.380 ms
3 R58-38 (139.175.58.38) 31.960 ms 31.563 ms 31.497 ms
4 AS2516-2.ix.jpix.ad.jp (210.171.224.94) 48.795 ms 48.862 ms 48.869 ms
5 cm-ote235.kddnet.ad.jp (59.128.7.23) 48.726 ms 48.192 ms 51.692 ms[/COLOR][/SIZE]

Hinet 10m/2m(參考即可..固定跟浮動差很多= =

來看看慢的吧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.

hinet 固3 ip
4m/1m

[img]http://cenet.talkce.com/userupload/a108271521.jpg[/img]

[img]http://cenet.talkce.com/userupload/a208271601.jpg[/img]

再附上 seednet 固3 ip
4m/1m

tracert不知為何,都是 timeout...,但明明 ping的到

[img]http://cenet.talkce.com/userupload/a108272255.jpg[/img]

[img]http://cenet.talkce.com/userupload/a108272425.jpg[/img]

Hinet 多機型固定 2M at AM 2:00
追蹤 cm-ote235.kddnet.ad.jp [59.128.7.23] 的路由:

[SIZE="2"][COLOR="SeaGreen"]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][/COLOR][/SIZE]
- - - - - - - - - - - - - - - - - - - -
[COLOR="SeaGreen"][SIZE="2"]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 [/SIZE][/COLOR]

公司中華電信 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

均在使用中測試

so-net 光纖 10M/2M PPPoe 1固+7動 ip
剛測試,冋時有用bt抓檔中..看來品質還不錯
供您參考

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]

最後我辦了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只能當參考
明明就是事實不是嗎?不曉得有無高手指導我一下
要如何說明 工程部那邊才知道怎麼去設定我的路由

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>

設定路由?
想太多

建議你早點跳到台固比較合適

[QUOTE=tvirus;1025458]設定路由?
想太多

建議你早點跳到台固比較合適[/QUOTE]

可是板上其他版友文章
也是有使用台固線路
ping起來也是5x...沒有絕對和一定

看起來您胸有成足
請問您是否有更詳細一點的解答呢?
麻煩您告知了
因為就那幾個字我很難理解 你的實際用意

其實很難講
我是玩OPEN NAP

一樣也是要連日本伺服器
原本是HINET但是覺得有時候太慢
所以心一橫違約跳到SEEDNET
但是更慘的是伺服器連的更慢而且檔案還無法傳送
而神奇的是不管你PING或是TRACERT都正常數字也很漂亮
所以不到一星期又轉回HINET
我因為是線上申請所以一星期鑑賞時間沒收費
只了了兩次設定費

給你參考

所以你可以先申請和他說要試用一下
不行的話馬上換

還有你要連的IP是 KDDI的
按照我的經驗HINET連KDDI的(還有ODN軟銀的)都很快
會出問題的都是NTT的

宜蘭
台灣大寬頻
2M/384K

Reply from 59.128.7.23: bytes=32 time=1371ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1368ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1045ms TTL=51
Reply from 59.128.7.23: bytes=32 time=974ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1452ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1498ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1390ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1189ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1062ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1043ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1154ms TTL=51
Reply from 59.128.7.23: bytes=32 time=866ms TTL=51
Reply from 59.128.7.23: bytes=32 time=399ms TTL=51
Reply from 59.128.7.23: bytes=32 time=227ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1647ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1007ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1101ms TTL=51
Reply from 59.128.7.23: bytes=32 time=990ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1123ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1069ms TTL=51
Reply from 59.128.7.23: bytes=32 time=1010ms TTL=51
Reply from 59.128.7.23: bytes=32 time=952ms TTL=51
Reply from 59.128.7.23: bytes=32 time=356ms TTL=51
Reply from 59.128.7.23: bytes=32 time=365ms TTL=51

emule開著
但有cfoss加註

貼出 台灣大寬頻 IP : [COLOR="Red"]61.31.143.232 [/COLOR](61-31-143-232.dynamic.tfn.net.tw)
[img]http://www.pczone.com.tw/attachment.php?attachmentid=15709&stc=1&d=1217727577[/img]

此數據還過得去。 因為ADSL速率等級是中等的。

以下是我的 kbro 今日走seednet 的路由與測試速度，與第一頁對照，沒有退步。 最後4個節點，與seednet 直營是相同的。
追蹤 cm-ote235.kddnet.ad.jp [59.128.7.23] 的路由:
[SIZE="2"] 1 <1 ms <1 ms <1 ms 2910G.kbronet.net [192.168.1.1]
2 12 ms 15 ms 9 ms 10.71.0.1
3 9 ms 9 ms 9 ms 211-76-116-1.static.kbronet.com.tw [211.76.116.1]
4 11 ms 9 ms 9 ms h18-192-72-108.seed.net.tw [192.72.108.18]
5 9 ms 11 ms 9 ms R56-190.seed.net.tw [139.175.56.190]
6 48 ms 41 ms 68 ms R58-82.seed.net.tw [139.175.58.82]
7 41 ms 41 ms 41 ms AS2516-2.ix.jpix.ad.jp [210.171.224.94]
8 46 ms 53 ms 54 ms cm-ote235.kddnet.ad.jp [59.128.7.23] [/SIZE]
追蹤完成。

與樓主相比， 是用戶端點到 Seednet 公司的速度有差別。 出國路由是走相同的路徑。

在全速下載或苛刻要求時，建議別經過 IP 分享器， 速率有差別。 小弟6000元的分享器都有明顯差別了，何況其他經濟價格取向的一般 IP分享器。
用好一點的網路卡，直接連MODEM （例如網路上口碑 有搶頻寬的 3com 905c , 或是 Intel gigabits 伺服器網卡）

一般而言,
ADSL在用戶迴路本身就有15ms～70ms不等的延遲,
VDSL則有10ms～20ms的戶迴路的延遲.
EPON FTTH的用戶迴路則會因用戶多寡, 一般會有2ms～10ms不等的延遲,
CM則看系統的設定和HFC用戶承載多寡, 可能會有3ms～30ms不等的延遲.
(乙太)專線型的FTTx一般在用戶段的延遲都在5ms以下.
把這些因素考慮進去, 再加上ISP和遠端連線的IP之間的路由的延遲,
就是大家ping這些IP時的回應時間了.