小弟有一套遊戲,必須連線到日本的伺服器,使用華奠的線路,不論何種速率,只要晩上18:00以後,就會出現LAG的情形,PING日本伺服器IP:202.177.202.70,
大概每10次就會出現TIME OUT,因為有許多台灣玩家都有此種現象,造成困擾,想請教各位先進,不知還有哪家的ISP連日本比較穩定?或是哪位不是使用華奠線路的先進方便帮小弟PING看看?如蒙回覆,不勝感激!

贊助商連結

最初由 l560816 發表
小弟有一套遊戲,必須連線到日本的伺服器,使用華奠的線路,不論何種速率,只要晩上18:00以後,就會出現LAG的情形,PING日本伺服器IP:202.177.202.70,
大概每10次就會出現TIME OUT,因為有許多台灣玩家都有此種現象,造成困擾,想請教各位先進,不知還有哪家的ISP連日本比較穩定?或是哪位不是使用華奠線路的先進方便帮小弟PING看看?如蒙回覆,不勝感激!

華電 1.5/384 固8
Pinging 202.177.202.70 with 32 bytes of data:



Reply from 202.177.202.70: bytes=32 time=101ms TTL=50

Reply from 202.177.202.70: bytes=32 time=98ms TTL=50

Reply from 202.177.202.70: bytes=32 time=100ms TTL=50

Reply from 202.177.202.70: bytes=32 time=99ms TTL=50



Ping statistics for 202.177.202.70:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 98ms, Maximum = 101ms, Average = 99ms

我是用速博3M/512K固一的
測了30次

Pinging 202.177.202.70 with 32 bytes of data:

Reply from 202.177.202.70: bytes=32 time=90ms TTL=47
Reply from 202.177.202.70: bytes=32 time=89ms TTL=47
Reply from 202.177.202.70: bytes=32 time=85ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=89ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=92ms TTL=47
Reply from 202.177.202.70: bytes=32 time=91ms TTL=47
Reply from 202.177.202.70: bytes=32 time=90ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=86ms TTL=47
Reply from 202.177.202.70: bytes=32 time=86ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=86ms TTL=47
Reply from 202.177.202.70: bytes=32 time=90ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=86ms TTL=47

Ping statistics for 202.177.202.70:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 92ms, Average = 87ms

SEEDNET 1.5/64 DHCP

Pinging 202.177.202.70 with 32 bytes of data:

Reply from 202.177.202.70: bytes=32 time=81ms TTL=53
Reply from 202.177.202.70: bytes=32 time=81ms TTL=53
Reply from 202.177.202.70: bytes=32 time=84ms TTL=53
Reply from 202.177.202.70: bytes=32 time=83ms TTL=53

Ping statistics for 202.177.202.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 84ms, Average = 82ms

多謝三位的回覆,不過會LAG是在每天的18:00以後,抱歉小弟沒說清楚,還請有空的話再幚個忙,多謝!!

一樣30次，不過is.net已經掛了，最後的謝幕......

Pinging 202.177.202.70 with 32 bytes of data:

Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=94ms TTL=52
Reply from 202.177.202.70: bytes=32 time=62ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=93ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=93ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=93ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=93ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=93ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52
Reply from 202.177.202.70: bytes=32 time=78ms TTL=52

Ping statistics for 202.177.202.70:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 94ms, Average = 80ms

可能用戶斷線的斷線跳槽的跳槽，所以看起來還不錯:corkysm:
......好感傷竟然用倒一家ISP......:corkysm:
（......瘟神來了怎知道、LordVader來報到......
往後哪家ISP看到我上門可能會嚇死:eye:）

最初由 LordVader 發表
一樣30次，不過is.net已經掛了，最後的謝幕......

可能用戶斷線的斷線跳槽的跳槽，所以看起來還不錯:corkysm:
......好感傷竟然用倒一家ISP......:corkysm:
（......瘟神來了怎知道、LordVader來報到......
往後哪家ISP看到我上門可能會嚇死:eye:）

呵呵
老大就不要傷心了
舊的不去新的不來啊
祝您找到好用又便宜的拍賣帳號

剛剛測的
6:35分

Pinging 202.177.202.70 with 32 bytes of data:

Reply from 202.177.202.70: bytes=32 time=93ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=86ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=89ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=99ms TTL=47
Reply from 202.177.202.70: bytes=32 time=86ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=89ms TTL=47
Reply from 202.177.202.70: bytes=32 time=85ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=89ms TTL=47
Reply from 202.177.202.70: bytes=32 time=89ms TTL=47
Reply from 202.177.202.70: bytes=32 time=86ms TTL=47
Reply from 202.177.202.70: bytes=32 time=90ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=94ms TTL=47
Reply from 202.177.202.70: bytes=32 time=87ms TTL=47
Reply from 202.177.202.70: bytes=32 time=96ms TTL=47
Reply from 202.177.202.70: bytes=32 time=90ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=92ms TTL=47
Reply from 202.177.202.70: bytes=32 time=89ms TTL=47
Reply from 202.177.202.70: bytes=32 time=88ms TTL=47
Reply from 202.177.202.70: bytes=32 time=92ms TTL=47

Ping statistics for 202.177.202.70:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 99ms, Average = 88ms

也是剛剛測的... 18:58, Seednet T3 LeasedLine.

C:\Documents and Settings\noodles>ping -n 30 202.177.202.70

Pinging 202.177.202.70 with 32 bytes of data:

Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52
Reply from 202.177.202.70: bytes=32 time=47ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52
Reply from 202.177.202.70: bytes=32 time=47ms TTL=52
Reply from 202.177.202.70: bytes=32 time=47ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=47ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=55ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52
Reply from 202.177.202.70: bytes=32 time=46ms TTL=52
Reply from 202.177.202.70: bytes=32 time=45ms TTL=52

Ping statistics for 202.177.202.70:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 55ms, Average = 46ms

再補一個給你參考, Test time: 19:04, Seednet T1/384 Bridge Mode ADSL.

[root@firewall root]# ping -s 24 -c 30 202.177.202.70
PING 202.177.202.70 (202.177.202.70) 24(52) bytes of data.
32 bytes from 202.177.202.70: icmp_seq=1 ttl=53 time=80.7 ms
32 bytes from 202.177.202.70: icmp_seq=2 ttl=53 time=78.8 ms
32 bytes from 202.177.202.70: icmp_seq=3 ttl=53 time=77.7 ms
32 bytes from 202.177.202.70: icmp_seq=4 ttl=53 time=76.8 ms
32 bytes from 202.177.202.70: icmp_seq=5 ttl=53 time=76.5 ms
32 bytes from 202.177.202.70: icmp_seq=6 ttl=53 time=77.9 ms
32 bytes from 202.177.202.70: icmp_seq=7 ttl=53 time=75.7 ms
32 bytes from 202.177.202.70: icmp_seq=8 ttl=53 time=78.8 ms
32 bytes from 202.177.202.70: icmp_seq=9 ttl=53 time=75.8 ms
32 bytes from 202.177.202.70: icmp_seq=10 ttl=53 time=77.8 ms
32 bytes from 202.177.202.70: icmp_seq=11 ttl=53 time=75.9 ms
32 bytes from 202.177.202.70: icmp_seq=12 ttl=53 time=78.7 ms
32 bytes from 202.177.202.70: icmp_seq=13 ttl=53 time=76.8 ms
32 bytes from 202.177.202.70: icmp_seq=14 ttl=53 time=77.4 ms
32 bytes from 202.177.202.70: icmp_seq=15 ttl=53 time=76.6 ms
32 bytes from 202.177.202.70: icmp_seq=16 ttl=53 time=78.9 ms
32 bytes from 202.177.202.70: icmp_seq=17 ttl=53 time=76.4 ms
32 bytes from 202.177.202.70: icmp_seq=18 ttl=53 time=79.8 ms
32 bytes from 202.177.202.70: icmp_seq=19 ttl=53 time=76.8 ms
32 bytes from 202.177.202.70: icmp_seq=20 ttl=53 time=78.5 ms
32 bytes from 202.177.202.70: icmp_seq=21 ttl=53 time=76.6 ms
32 bytes from 202.177.202.70: icmp_seq=22 ttl=53 time=78.3 ms
32 bytes from 202.177.202.70: icmp_seq=23 ttl=53 time=80.8 ms
32 bytes from 202.177.202.70: icmp_seq=24 ttl=53 time=77.6 ms
32 bytes from 202.177.202.70: icmp_seq=25 ttl=53 time=75.4 ms
32 bytes from 202.177.202.70: icmp_seq=26 ttl=53 time=77.6 ms
32 bytes from 202.177.202.70: icmp_seq=27 ttl=53 time=75.5 ms
32 bytes from 202.177.202.70: icmp_seq=28 ttl=53 time=77.5 ms
32 bytes from 202.177.202.70: icmp_seq=29 ttl=53 time=76.7 ms
32 bytes from 202.177.202.70: icmp_seq=30 ttl=53 time=77.8 ms

--- 202.177.202.70 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29290ms
rtt min/avg/max/mdev = 75.480/77.581/80.822/1.392 ms
[root@firewall root]#