Tree of Savior (English Ver.)

Tree of Savior (English Ver.)

查看统计:
Lenant 2016 年 3 月 25 日 下午 7:55
The REAL ping test for servers
http://www.cloudping.info/
(Virginia)

The other topic is using a wrong link

EDIT: some ppl asking why ping amazon servers, cus the game is hosted in the amazon server East Coast

or if u are having problems with this u also can:
Type cmd in windows search box, open cmd.exe

type "ping 54.88.25.242 -n 30" without the ""
最后由 Lenant 编辑于; 2016 年 3 月 26 日 下午 8:23
< >
正在显示第 31 - 44 条,共 44 条留言
Powerful Holy God 2016 年 3 月 26 日 上午 4:49 
30 ms ping, i literally live in VA lol
LIZARDMAN 2016 年 3 月 26 日 上午 5:35 
Well, this time is more reasonable.
251ms from Sydney
ShadowSkill 2016 年 3 月 26 日 上午 5:55 
This test is worthless, or amazon is using some soviet era tech
This is my stats from Op test

US-East (Virginia) 333 ms
US-West (California) 421 ms
US-West (Oregon) 357 ms
Europe (Ireland) 196 ms
Europe (Frankfurt) 198 ms
Asia Pacific (Singapore) 473 ms
Asia Pacific (Sydney) 483 ms
Asia Pacific (Japan) 959 ms
South America (Brazil) 428 ms
[/i]



My stats from reddit test are like: Ping min 141 max 157 avg 144ms
^ And this is true for most MMO i play with US based servers, for example in Secret World MMO (servers located on East Coast USA) i have 140-170 most of the time.

Reddit test
https://www.reddit.com/r/treeofsavior/comments/4b9ftf/for_accurate_latency_test_use_ping_548825242/


Type cmd in windows search box, open cmd.exe

type "ping 54.88.25.242 -n 30" without the ""
Rcrft 2016 年 3 月 26 日 上午 7:19 
237 ms Russia (Ural)
@xaker89 2016 年 3 月 26 日 上午 7:22 
142 from Russia
Michi 2016 年 3 月 26 日 上午 7:52 
185-190 From Argentina
Mordikan 2016 年 3 月 26 日 上午 8:17 
That server is just responding to HTTP-GET requests. That's not ICMP. I've had to do that at work before with some equipment. Find an open TCP port and send it a series of SYN packets then calculate the RTT which itself is not an accurate representation of latency. Wireshark doesn't lie.

Frame 76: 162 bytes on wire (1296 bits), 162 bytes captured (1296 bits) on interface 0
Interface id: 0 (\Device\NPF_{1BA4B2A8-4E39-43CA-B54D-8A7D42FDF84C})
Encapsulation type: Ethernet (1)
Arrival Time: Mar 26, 2016 10:03:04.715659000 Central Daylight Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1459004584.715659000 seconds
[Time delta from previous captured frame: 0.103962000 seconds]
[Time delta from previous displayed frame: 0.221469000 seconds]
[Time since reference or first frame: 4.424829000 seconds]
Frame Number: 76
Frame Length: 162 bytes (1296 bits)
Capture Length: 162 bytes (1296 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ethertype:ip:tcp:http:data]
[Coloring Rule Name: HTTP]
[Coloring Rule String: http || tcp.port == 80 || http2]
Ethernet II, Src: HonHaiPr_59:d4:c3 (00:1f:e2:59:d4:c3), Dst: Micro-St_5e:39:0a (d8:cb:8a:5e:39:0a)
Internet Protocol Version 4, Src: 54.240.193.70, Dst: 10.10.0.100
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes
Differentiated Services Field: 0x00 (DSCP: CS0, ECN: Not-ECT)
Total Length: 148
Identification: 0xd1d9 (53721)
Flags: 0x02 (Don't Fragment)
Fragment offset: 0
Time to live: 35
Protocol: TCP (6)
Header checksum: 0x82e6 [validation disabled]
Source: 54.240.193.70
Destination: 10.10.0.100
[Source GeoIP: Unknown]
[Destination GeoIP: Unknown]
Transmission Control Protocol, Src Port: 80 (80), Dst Port: 50430 (50430), Seq: 109, Ack: 741, Len: 108
Hypertext Transfer Protocol
HTTP/1.1 200 OK\r\n
Content-Length: 8\r\n
Date: Sat, 26 Mar 2016 15:02:57 GMT\r\n
Server: Amazon SimpleDB\r\n
\r\n
[HTTP response 2/2]
[Time since request: 0.221469000 seconds]
[Prev request in frame: 71]
[Prev response in frame: 73]
[Request in frame: 74]
Data (8 bytes)
..
Lenant 2016 年 3 月 26 日 下午 1:32 
引用自 cpluscoffee
That server is just responding to HTTP-GET requests. That's not ICMP. I've had to do that at work before with some equipment. Find an open TCP port and send it a series of SYN packets then calculate the RTT which itself is not an accurate representation of latency. Wireshark doesn't lie.

Frame 76: 162 bytes on wire (1296 bits), 162 bytes captured (1296 bits) on interface 0
Interface id: 0 (\Device\NPF_{1BA4B2A8-4E39-43CA-B54D-8A7D42FDF84C})
Encapsulation type: Ethernet (1)
Arrival Time: Mar 26, 2016 10:03:04.715659000 Central Daylight Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1459004584.715659000 seconds
[Time delta from previous captured frame: 0.103962000 seconds]
[Time delta from previous displayed frame: 0.221469000 seconds]
[Time since reference or first frame: 4.424829000 seconds]
Frame Number: 76
Frame Length: 162 bytes (1296 bits)
Capture Length: 162 bytes (1296 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ethertype:ip:tcp:http:data]
[Coloring Rule Name: HTTP]
[Coloring Rule String: http || tcp.port == 80 || http2]
Ethernet II, Src: HonHaiPr_59:d4:c3 (00:1f:e2:59:d4:c3), Dst: Micro-St_5e:39:0a (d8:cb:8a:5e:39:0a)
Internet Protocol Version 4, Src: 54.240.193.70, Dst: 10.10.0.100
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes
Differentiated Services Field: 0x00 (DSCP: CS0, ECN: Not-ECT)
Total Length: 148
Identification: 0xd1d9 (53721)
Flags: 0x02 (Don't Fragment)
Fragment offset: 0
Time to live: 35
Protocol: TCP (6)
Header checksum: 0x82e6 [validation disabled]
Source: 54.240.193.70
Destination: 10.10.0.100
[Source GeoIP: Unknown]
[Destination GeoIP: Unknown]
Transmission Control Protocol, Src Port: 80 (80), Dst Port: 50430 (50430), Seq: 109, Ack: 741, Len: 108
Hypertext Transfer Protocol
HTTP/1.1 200 OK\r\n
Content-Length: 8\r\n
Date: Sat, 26 Mar 2016 15:02:57 GMT\r\n
Server: Amazon SimpleDB\r\n
\r\n
[HTTP response 2/2]
[Time since request: 0.221469000 seconds]
[Prev request in frame: 71]
[Prev response in frame: 73]
[Request in frame: 74]
Data (8 bytes)
..
sry i dont understand any of this xD i just posted what i found in forums and was the most accurate with mine and other ppl's ping
mau 2016 年 3 月 26 日 下午 4:15 
140-150ms.
im ok if this is going to be my latency in-game.
Titan 2016 年 3 月 26 日 下午 6:52 
170 ms brazil
最后由 Titan 编辑于; 2016 年 3 月 26 日 下午 6:52
Reegatta 2016 年 3 月 26 日 下午 7:22 
Folks, use "ping" command in CMD prompt, seems to be more accurate. I got 146 - 150 ms with no loss packets.

IP from the server: 54.88.25.242.

Its lamia server from ITOS like someone says.
Zombies 2016 年 3 月 26 日 下午 7:30 
114ms ( scotland )
RayGobot 2016 年 3 月 26 日 下午 11:03 
44ms from South Western Ontario :p
julzRtw 2016 年 3 月 27 日 上午 2:34 
From your website :
US-East (Virginia) 121 ms
Europe (Frankfurt) 47 ms

From win cmd :
105ms

WTB eu servers :'(
最后由 julzRtw 编辑于; 2016 年 3 月 27 日 上午 2:37
< >
正在显示第 31 - 44 条,共 44 条留言
每页显示数: 1530 50

发帖日期: 2016 年 3 月 25 日 下午 7:55
回复数: 44