【問題】請問一下我的PING值正常嗎





WFR30126
2009-01-24, 11:48 PM
Microsoft Windows XP [版本 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ping 168.95.1.1 -t

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=21ms TTL=248
Reply from 168.95.1.1: bytes=32 time=15ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248
Reply from 168.95.1.1: bytes=32 time=31ms TTL=248

我是用hinet 10m/2m的




小沛
2009-01-25, 01:28 PM
有點小偏高,妳是只有Ping沒有同時瀏覽網頁跟上傳嗎?

不過還算正常範圍。我附上我的給妳參考。

2009/01/25 下午 1:26 分 測試的結果。

C:\>ping 168.95.1.1 -t

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248

Ping statistics for 168.95.1.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

boy711
2009-01-26, 02:08 AM
為什麼 我ping 不出來 time out:cry:

WFR30126
2009-01-26, 10:15 PM
有點小偏高,妳是只有Ping沒有同時瀏覽網頁跟上傳嗎?

不過還算正常範圍。我附上我的給妳參考。

2009/01/25 下午 1:26 分 測試的結果。

C:\>ping 168.95.1.1 -t

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248

Ping statistics for 168.95.1.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

沒有瀏覽網頁跟上傳

其實我前陣子也差不多是1x ms

不知道為什麼就突然變成31ms

大部分時間幾乎都保持在這個反應時間

不知道申告有用嗎?

p055877632
2009-01-27, 01:15 AM
有點小偏高,妳是只有Ping沒有同時瀏覽網頁跟上傳嗎?

不過還算正常範圍。我附上我的給妳參考。

2009/01/25 下午 1:26 分 測試的結果。

C:\>ping 168.95.1.1 -t

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=14ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248
Reply from 168.95.1.1: bytes=32 time=13ms TTL=248

Ping statistics for 168.95.1.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

xec@xec-desktop:~$ ping 168.95.1.1
PING 168.95.1.1 (168.95.1.1) 56(84) bytes of data.
64 bytes from 168.95.1.1: icmp_seq=1 ttl=239 time=39.4 ms
64 bytes from 168.95.1.1: icmp_seq=2 ttl=240 time=38.4 ms
64 bytes from 168.95.1.1: icmp_seq=3 ttl=239 time=39.6 ms
64 bytes from 168.95.1.1: icmp_seq=4 ttl=239 time=39.7 ms
64 bytes from 168.95.1.1: icmp_seq=5 ttl=239 time=39.3 ms
64 bytes from 168.95.1.1: icmp_seq=6 ttl=239 time=39.8 ms
64 bytes from 168.95.1.1: icmp_seq=7 ttl=239 time=39.0 ms
64 bytes from 168.95.1.1: icmp_seq=8 ttl=239 time=44.0 ms
64 bytes from 168.95.1.1: icmp_seq=9 ttl=240 time=68.7 ms
64 bytes from 168.95.1.1: icmp_seq=10 ttl=239 time=77.7 ms
64 bytes from 168.95.1.1: icmp_seq=11 ttl=239 time=100 ms
64 bytes from 168.95.1.1: icmp_seq=12 ttl=239 time=107 ms
64 bytes from 168.95.1.1: icmp_seq=13 ttl=239 time=132 ms
64 bytes from 168.95.1.1: icmp_seq=14 ttl=239 time=83.3 ms
64 bytes from 168.95.1.1: icmp_seq=15 ttl=240 time=90.0 ms
64 bytes from 168.95.1.1: icmp_seq=16 ttl=239 time=38.9 ms
64 bytes from 168.95.1.1: icmp_seq=17 ttl=239 time=39.6 ms
64 bytes from 168.95.1.1: icmp_seq=18 ttl=239 time=39.0 ms
64 bytes from 168.95.1.1: icmp_seq=19 ttl=240 time=39.5 ms
64 bytes from 168.95.1.1: icmp_seq=20 ttl=239 time=39.8 ms
64 bytes from 168.95.1.1: icmp_seq=21 ttl=239 time=39.2 ms
64 bytes from 168.95.1.1: icmp_seq=22 ttl=239 time=42.5 ms
64 bytes from 168.95.1.1: icmp_seq=23 ttl=240 time=88.6 ms
64 bytes from 168.95.1.1: icmp_seq=24 ttl=240 time=92.0 ms
64 bytes from 168.95.1.1: icmp_seq=25 ttl=240 time=71.7 ms
64 bytes from 168.95.1.1: icmp_seq=26 ttl=239 time=86.4 ms
64 bytes from 168.95.1.1: icmp_seq=27 ttl=239 time=38.7 ms
64 bytes from 168.95.1.1: icmp_seq=28 ttl=239 time=39.2 ms
64 bytes from 168.95.1.1: icmp_seq=29 ttl=239 time=39.4 ms
64 bytes from 168.95.1.1: icmp_seq=30 ttl=239 time=40.3 ms
64 bytes from 168.95.1.1: icmp_seq=31 ttl=239 time=38.9 ms
64 bytes from 168.95.1.1: icmp_seq=32 ttl=239 time=39.6 ms
64 bytes from 168.95.1.1: icmp_seq=33 ttl=239 time=39.1 ms
64 bytes from 168.95.1.1: icmp_seq=34 ttl=239 time=39.7 ms
64 bytes from 168.95.1.1: icmp_seq=35 ttl=240 time=39.8 ms
64 bytes from 168.95.1.1: icmp_seq=36 ttl=239 time=39.3 ms
64 bytes from 168.95.1.1: icmp_seq=37 ttl=239 time=39.9 ms
64 bytes from 168.95.1.1: icmp_seq=38 ttl=239 time=39.3 ms
64 bytes from 168.95.1.1: icmp_seq=39 ttl=239 time=39.2 ms
^C
--- 168.95.1.1 ping statistics ---
39 packets transmitted, 39 received, 0% packet loss, time 38173ms
rtt min/avg/max/mdev = 38.456/54.137/132.970/24.778 ms

preattyall
2009-02-01, 10:50 AM
沒有瀏覽網頁跟上傳

其實我前陣子也差不多是1x ms

不知道為什麼就突然變成31ms

大部分時間幾乎都保持在這個反應時間

不知道申告有用嗎?


我也是3xms,應該還算正常吧
不過工程師維修時很少以這個數據來判斷是否故障
光憑3Xms這點申告應該沒用