Pinging sz.tencent.com [61.144.238.145] with 32 bytes of data: Reply from 61.144.238.145: bytes=32 time=140ms TTL=243 Reply from 61.144.238.145: bytes=32 time=123ms TTL=243 Reply from 61.144.238.145: bytes=32 time=123ms TTL=243 Reply from 61.144.238.145: bytes=32 time=121ms TTL=243 Ping statistics for 61.144.238.145: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 121ms, Maximum = 140ms, Average = 126ms Pinging sz2.tencent.com [61.144.238.146] with 32 bytes of data: Reply from 61.144.238.146: bytes=32 time=129ms TTL=242 Reply from 61.144.238.146: bytes=32 time=122ms TTL=242 Reply from 61.144.238.146: bytes=32 time=126ms TTL=242 Reply from 61.144.238.146: bytes=32 time=137ms TTL=242 Ping statistics for 61.144.238.146: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 122ms, Maximum = 137ms, Average = 128ms Pinging sz3.tencent.com [202.104.129.251] with 32 bytes of data: Reply from 202.104.129.251: bytes=32 time=143ms TTL=242 Reply from 202.104.129.251: bytes=32 time=130ms TTL=242 Reply from 202.104.129.251: bytes=32 time=231ms TTL=242 Reply from 202.104.129.251: bytes=32 time=210ms TTL=242 Ping statistics for 202.104.129.251: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 130ms, Maximum = 231ms, Average = 178ms |