開放主機Ping功能

[GM Aron]

這幾天都很 Lag...昨天打壇時甚至出現停了快一分鐘, 人物才有反應 =_=

目前還很lag嗎? 我們一直在注意這個問題
但是必須看目前被lag影響的玩家個數和頻率才能確定到底目前lag的情況多嚴重

玩家出現lag時請記得提供以下資訊：
- ping 與 tracert數值，這樣可以讓我們釐清是網路問題或是主機負荷問題
- 時間，如果不在台灣的時區請記得註明你的時區
- 當時的線上人數

[frand]

這幾天都很 Lag...昨天打壇時甚至出現停了快一分鐘, 人物才有反應 =_=

[Rena]

昨天lag的時候問人家不lag嗎？

回答：lag啊

問：為什麽不po版呢？

回答：大家都不po版啊

如果台灣玩家有感到lag的話，大陸這邊肯定是受不了的。

我昨天上上下下不知道多少次，想躲旁邊點去補血，走兩步走不動了，上來就變鬼了。

之前有問另一位大陸玩家為什麽這幾天不上線，他說卡，走走停停，白天也卡，所以連掛機也不掛了。

之前香港的朋友也經常和我說lag，現在也不玩了。

昨天好像凌晨1點多，速度又變好了，但那個時候大家都不玩了。

po貼時5點半也沒timed out，主要是看晚上大家在玩的那個時間段。

[GM Aron]

我從美國連都還好，沒有timed out
維持在160ms左右

其他台灣玩家有問題嗎?
其他大陸或香港有沒有問題?

極其的lag，太多timed out，比昨天還要走不動

Pinging login.odyes.com [122.116.138.145] with 32 bytes of data:

Reply from 122.116.138.145: bytes=32 time=131ms TTL=114
Reply from 122.116.138.145: bytes=32 time=105ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=112ms TTL=114
Reply from 122.116.138.145: bytes=32 time=171ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=112ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=128ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=130ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=117ms TTL=114
Reply from 122.116.138.145: bytes=32 time=125ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=148ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114
Reply from 122.116.138.145: bytes=32 time=118ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=121ms TTL=114
Reply from 122.116.138.145: bytes=32 time=125ms TTL=114
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114

Ping statistics for 122.116.138.145:
Packets: Sent = 44, Received = 37, Lost = 7 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 171ms, Average = 120ms


Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms RTA230.home [192.168.1.1]
2 10 ms 10 ms 9 ms 218.1.60.249
3 9 ms 9 ms 8 ms 222.72.254.149
4 9 ms 10 ms 8 ms 124.74.210.141
5 9 ms 10 ms 9 ms 61.152.86.54
6 10 ms 9 ms 8 ms 202.97.35.74
7 12 ms 12 ms 11 ms 202.97.35.18
8 11 ms 11 ms 11 ms 202.97.35.33
9 10 ms 9 ms 10 ms 202.97.4.114
10 94 ms 90 ms 92 ms r36-s2.tp.hinet.net [211.72.233.234]
11 87 ms 90 ms 88 ms r35-s2.tp.hinet.net [210.65.254.249]
12 87 ms * 93 ms pr01-s2.tp.hinet.net [210.65.254.172]
13 94 ms 92 ms 93 ms tp-crs12.router.hinet.net [220.128.4.70]
14 * 92 ms 92 ms tp-pc1-t64-1.router.hinet.net [220.128.11.57]
15 100 ms * 92 ms tp [220.128.11.5]
16 * * * Request timed out.
17 131 ms * 125 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.145]

Trace complete.

[Rena]

極其的lag，太多timed out，比昨天還要走不動

Pinging login.odyes.com [122.116.138.145] with 32 bytes of data:

Reply from 122.116.138.145: bytes=32 time=131ms TTL=114
Reply from 122.116.138.145: bytes=32 time=105ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=112ms TTL=114
Reply from 122.116.138.145: bytes=32 time=171ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=112ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=128ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=130ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=117ms TTL=114
Reply from 122.116.138.145: bytes=32 time=125ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=148ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114
Reply from 122.116.138.145: bytes=32 time=118ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=122ms TTL=114
Reply from 122.116.138.145: bytes=32 time=121ms TTL=114
Reply from 122.116.138.145: bytes=32 time=125ms TTL=114
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114

Ping statistics for 122.116.138.145:
Packets: Sent = 44, Received = 37, Lost = 7 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 171ms, Average = 120ms


Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms RTA230.home [192.168.1.1]
2 10 ms 10 ms 9 ms 218.1.60.249
3 9 ms 9 ms 8 ms 222.72.254.149
4 9 ms 10 ms 8 ms 124.74.210.141
5 9 ms 10 ms 9 ms 61.152.86.54
6 10 ms 9 ms 8 ms 202.97.35.74
7 12 ms 12 ms 11 ms 202.97.35.18
8 11 ms 11 ms 11 ms 202.97.35.33
9 10 ms 9 ms 10 ms 202.97.4.114
10 94 ms 90 ms 92 ms r36-s2.tp.hinet.net [211.72.233.234]
11 87 ms 90 ms 88 ms r35-s2.tp.hinet.net [210.65.254.249]
12 87 ms * 93 ms pr01-s2.tp.hinet.net [210.65.254.172]
13 94 ms 92 ms 93 ms tp-crs12.router.hinet.net [220.128.4.70]
14 * 92 ms 92 ms tp-pc1-t64-1.router.hinet.net [220.128.11.57]
15 100 ms * 92 ms tp [220.128.11.5]
16 * * * Request timed out.
17 131 ms * 125 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.145]

Trace complete.

[server]

北京有好的嗎?
下半年可能會在北京度過 有推薦好的ISP嗎?

isp.jimdo


你看看 是否滿意
(經由朋友的,朋友轉述的)

isp.jimdo.com/aayo.php

[Rena]

tracert多次，好像問題是出在第16的位置
h165.s75.ts.hinet.net [168.95.75.165]

凌晨3點半還是一樣的走走停停，很多timed out。

[Rena]

11點時水晶有65人，2:20水晶剩下33人，好像有不少人是被踢掉的

以下代廣東玩家GodMage po 凌晨2：20

說“上去走几步停一停的，白天也是”

Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:

1 6 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms <1 ms 113.105.10.81
3 1 ms 1 ms 1 ms 61.144.12.41
4 1 ms 1 ms 1 ms 61.144.3.18
5 26 ms 26 ms 26 ms 202.97.35.57
6 26 ms 26 ms 26 ms 202.97.33.206
7 26 ms 27 ms 26 ms 202.97.33.2
8 26 ms 26 ms 29 ms 202.97.35.234
9 26 ms 26 ms 26 ms 202.97.4.114
10 70 ms 65 ms 61 ms r36-s2.tp.hinet.net [211.72.233.234]
11 71 ms 72 ms 68 ms r35-s2.tp.hinet.net [210.65.254.249]
12 76 ms 79 ms 78 ms pr01-s2.tp.hinet.net [210.65.254.172]
13 81 ms 80 ms 80 ms tp-crs12.router.hinet.net [220.128.4.70]
14 82 ms 65 ms 87 ms tp-pc1-t64-1.router.hinet.net [220.128.11.57]
15 73 ms 71 ms 76 ms tp-pc1-c76r2.router.hinet.net [220.128.11.5]
16 * * * Request timed out.
17 106 ms 110 ms 108 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.
145]

Trace complete.

[Rena]

凌晨1點多還12%的timed out，走走停停，一下子變無聲世界，完全不動，上來就黑白屏，慘！


Reply from 122.116.138.145: bytes=32 time=118ms TTL=114
Reply from 122.116.138.145: bytes=32 time=117ms TTL=114
Reply from 122.116.138.145: bytes=32 time=119ms TTL=114
Reply from 122.116.138.145: bytes=32 time=112ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=102ms TTL=114
Reply from 122.116.138.145: bytes=32 time=102ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114
Reply from 122.116.138.145: bytes=32 time=105ms TTL=114
Reply from 122.116.138.145: bytes=32 time=106ms TTL=114
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=112ms TTL=114
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=109ms TTL=114
Reply from 122.116.138.145: bytes=32 time=103ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=108ms TTL=114
Reply from 122.116.138.145: bytes=32 time=108ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=112ms TTL=114

Ping statistics for 122.116.138.145:
Packets: Sent = 1188, Received = 1041, Lost = 147 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 155ms, Average = 115ms




Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms RTA230.home [192.168.1.1]
2 11 ms 9 ms 10 ms 218.1.60.249
3 10 ms 7 ms 8 ms 222.72.254.149
4 9 ms 10 ms 9 ms 124.74.210.141
5 9 ms 8 ms 9 ms 61.152.86.54
6 9 ms 9 ms 9 ms 202.97.35.74
7 10 ms 9 ms 8 ms 202.97.35.18
8 9 ms 8 ms 9 ms 202.97.35.33
9 10 ms 9 ms 10 ms 202.97.4.114
10 80 ms 86 ms 82 ms r36-s2.tp.hinet.net [211.72.233.234]
11 83 ms 79 ms 84 ms r35-s2.tp.hinet.net [210.65.254.249]
12 83 ms 81 ms 86 ms pr01-s2.tp.hinet.net [210.65.254.172]
13 86 ms 87 ms 85 ms tp-crs12.router.hinet.net [220.128.4.70]
14 86 ms 88 ms 88 ms tp-pc1-t64-1.router.hinet.net [220.128.11.57]
15 84 ms 86 ms 83 ms tp [220.128.11.5]
16 * * * Request timed out.
17 109 ms 107 ms 113 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.
145]

Trace complete.


Tracing route to login.odyes.com [122.116.138.145]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms RTA230.home [192.168.1.1]
2 12 ms 10 ms 10 ms 218.1.60.249
3 9 ms 8 ms 9 ms 222.72.254.149
4 9 ms 9 ms 9 ms 124.74.210.141
5 9 ms 9 ms 10 ms 61.152.86.54
6 10 ms 9 ms 10 ms 202.97.35.74
7 10 ms 10 ms 9 ms 202.97.35.18
8 11 ms 10 ms 9 ms 202.97.35.33
9 9 ms 9 ms 9 ms 202.97.4.114
10 68 ms 75 ms 77 ms r36-s2.tp.hinet.net [211.72.233.234]
11 80 ms 83 ms 86 ms r35-s2.tp.hinet.net [210.65.254.249]
12 78 ms 79 ms 83 ms pr01-s2.tp.hinet.net [210.65.254.172]
13 84 ms 81 ms 83 ms tp-crs12.router.hinet.net [220.128.4.70]
14 * 87 ms 97 ms tp-pc1-t64-1.router.hinet.net [220.128.11.57]
15 87 ms 84 ms 87 ms tp [220.128.11.5]
16 * * * Request timed out.
17 110 ms 109 ms 111 ms 122-116-138-145.HINET-IP.hinet.net [122.116.138.
145]

Trace complete.

[power]

Ping login.odyes.com [122.116.138.145] (使用 32 位元組的資料):
回覆自 122.116.138.145: 位元組=32 時間=52ms TTL=120
回覆自 122.116.138.145: 位元組=32 時間=50ms TTL=121
回覆自 122.116.138.145: 位元組=32 時間=47ms TTL=121
要求等候逾時。

122.116.138.145 的 Ping 統計資料:
封包: 已傳送 = 4，已收到 = 3, 已遺失 = 1 (25% 遺失)，
大約的來回時間 (毫秒):
最小值 = 47ms，最大值 = 52ms，平均 = 49ms

------------------------------------------------------
6.28分測的~還是LAG
----------------------------------------
台灣台中上的~

[GM Aron]

要命的速度，開個會被踢下去四五次，timed out太多了

Pinging login.odyes.com [122.116.138.145] with 32 bytes of data:

Reply from 122.116.138.145: bytes=32 time=101ms TTL=114
Reply from 122.116.138.145: bytes=32 time=98ms TTL=114
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Reply from 122.116.138.145: bytes=32 time=101ms TTL=114
Reply from 122.116.138.145: bytes=32 time=104ms TTL=114
Reply from 122.116.138.145: bytes=32 time=98ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=108ms TTL=114
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=102ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=117ms TTL=114
....
Request timed out.
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114
Reply from 122.116.138.145: bytes=32 time=121ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114

Ping statistics for 122.116.138.145:
Packets: Sent = 78, Received = 64, Lost = 14 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 130ms, Average = 111ms

遇到問題請記得用tracert看一下瓶頸出在哪裡

[spiky0209]

北京有好的嗎?
下半年可能會在北京度過 有推薦好的ISP嗎?

[Rena]

要命的速度，開個會被踢下去四五次，timed out太多了

Pinging login.odyes.com [122.116.138.145] with 32 bytes of data:

Reply from 122.116.138.145: bytes=32 time=101ms TTL=114
Reply from 122.116.138.145: bytes=32 time=98ms TTL=114
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Reply from 122.116.138.145: bytes=32 time=101ms TTL=114
Reply from 122.116.138.145: bytes=32 time=104ms TTL=114
Reply from 122.116.138.145: bytes=32 time=98ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=108ms TTL=114
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=102ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=117ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114
Reply from 122.116.138.145: bytes=32 time=118ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=125ms TTL=114
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114
Reply from 122.116.138.145: bytes=32 time=118ms TTL=114
Request timed out.
Request timed out.
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=101ms TTL=114
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=98ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=108ms TTL=114
Reply from 122.116.138.145: bytes=32 time=108ms TTL=114
Reply from 122.116.138.145: bytes=32 time=108ms TTL=114
Reply from 122.116.138.145: bytes=32 time=103ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=128ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=117ms TTL=114
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Reply from 122.116.138.145: bytes=32 time=104ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114
Reply from 122.116.138.145: bytes=32 time=130ms TTL=114
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=111ms TTL=114
Reply from 122.116.138.145: bytes=32 time=116ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=105ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=118ms TTL=114
Reply from 122.116.138.145: bytes=32 time=110ms TTL=114
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114
Reply from 122.116.138.145: bytes=32 time=105ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=115ms TTL=114
Reply from 122.116.138.145: bytes=32 time=109ms TTL=114
Reply from 122.116.138.145: bytes=32 time=118ms TTL=114
Request timed out.
Reply from 122.116.138.145: bytes=32 time=113ms TTL=114
Reply from 122.116.138.145: bytes=32 time=114ms TTL=114
Reply from 122.116.138.145: bytes=32 time=107ms TTL=114
Reply from 122.116.138.145: bytes=32 time=121ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114
Reply from 122.116.138.145: bytes=32 time=120ms TTL=114

Ping statistics for 122.116.138.145:
Packets: Sent = 78, Received = 64, Lost = 14 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 130ms, Average = 111ms

[server]

上海電信

你人在上海 啊!

可惜，香港有一家 风评不错业者，不过钱稍微有点贵

[Rena]

上海電信