Files
Down-Detector/node_modules/ping/test/fixture/answer.json
2018-05-27 16:11:50 +01:00

68 lines
4.1 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"macos_en_sample1": {
"host": "google.com",
"numeric_host": "172.217.24.46",
"alive": true,
"output": "PING google.com (172.217.24.46): 56 data bytes\n64 bytes from 172.217.24.46: icmp_seq=0 ttl=54 time=5.371 ms\n64 bytes from 172.217.24.46: icmp_seq=1 ttl=54 time=4.269 ms\n64 bytes from 172.217.24.46: icmp_seq=2 ttl=54 time=4.970 ms\n64 bytes from 172.217.24.46: icmp_seq=3 ttl=54 time=5.228 ms\n\n--- google.com ping statistics ---\n4 packets transmitted, 4 packets received, 0.0% packet loss\nround-trip min/avg/max/stddev = 4.269/4.960/5.371/0.424 ms\n",
"time": 5.371,
"min": "4.269",
"max": "5.371",
"avg": "4.960",
"stddev": "0.424"
},
"linux_en_sample1": {
"host": "localhost",
"numeric_host": "127.0.0.1",
"alive": true,
"output": "PING localhost (127.0.0.1) 56(84) bytes of data.\n64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.022 ms\n64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.027 ms\n64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.029 ms\n64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.030 ms\n\n--- localhost ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 2999ms\nrtt min/avg/max/mdev = 0.022/0.027/0.030/0.003 ms\n",
"time": 0.022,
"min": "0.022",
"max": "0.030",
"avg": "0.027",
"stddev": "0.003"
},
"window_en_sample1": {
"host": "www.some-domain.com",
"numeric_host": "127.0.0.1",
"alive": true,
"output": "Pinging www.some-domain.com [127.0.0.1] with 32 bytes of\nReply from 127.0.0.1: bytes=32 time=564ms TTL=237\nReply from 127.0.0.1: bytes=32 time=555ms TTL=237\nReply from 127.0.0.1: bytes=32 time=554ms TTL=237\nReply from 127.0.0.1: bytes=32 time=548ms TTL=237\n\nPing statistics for 127.0.0.1:\n Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)\n Approximate round trip times in milli-seconds:\n Minimum = 548ms, Maximum = 564ms, Average = 555ms\n",
"time": 564,
"min": "548.000",
"max": "564.000",
"avg": "555.000",
"stddev": "5.723"
},
"window_zh_sample1": {
"host": "google.com",
"numeric_host": "216.58.203.14",
"alive": true,
"output": "Ping google.com [216.58.203.14] (使用 32 位元組的資料):\n回覆自 216.58.203.14: 位元組=32 時間=2ms TTL=54\n回覆自 216.58.203.14: 位元組=32 時間=2ms TTL=54\n回覆自 216.58.203.14: 位元組=32 時間=3ms TTL=54\n回覆自 216.58.203.14: 位元組=32 時間=3ms TTL=54\n\n216.58.203.14 的 Ping 統計資料:\n 封包: 已傳送 = 4已收到 = 4, 已遺失 = 0 (0% 遺失)\n 大約的來回時間 (毫秒):\n 最小值 = 2ms最大值 = 3ms平均 = 2ms\n",
"time": 2,
"min": "2.000",
"max": "3.000",
"avg": "2.000",
"stddev": "0.707"
},
"window_zh_sample2": {
"host": "google.com",
"numeric_host": "216.58.203.14",
"alive": true,
"output": "\nPing google.com [216.58.203.14] (使用 32 位元組的資料):\n回覆自 216.58.203.14: 位元組=32 時間=2ms TTL=54\n回覆自 216.58.203.14: 位元組=32 時間=2ms TTL=54\n回覆自 216.58.203.14: 位元組=32 時間=3ms TTL=54\n回覆自 216.58.203.14: 位元組=32 時間=3ms TTL=54\n\n216.58.203.14 的 Ping 統計資料:\n 封包: 已傳送 = 4已收到 = 4, 已遺失 = 0 (0% 遺失)\n 大約的來回時間 (毫秒):\n 最小值 = 2ms最大值 = 3ms平均 = 2ms\n",
"time": 2,
"min": "2.000",
"max": "3.000",
"avg": "2.000",
"stddev": "0.707"
},
"window_zh_sample3": {
"host": "127.0.0.1",
"numeric_host": "127.0.0.1",
"alive": true,
"output": "\nPing 127.0.0.1 (使用 32 位元組的資料):\n回覆自 127.0.0.1: 位元組=32 時間<1ms TTL=128\n回覆自 127.0.0.1: 位元組=32 時間<1ms TTL=128\n回覆自 127.0.0.1: 位元組=32 時間<1ms TTL=128\n回覆自 127.0.0.1: 位元組=32 時間<1ms TTL=128\n\n127.0.0.1 的 Ping 統計資料:\n 封包: 已傳送 = 4已收到 = 4, 已遺失 = 0 (0% 遺失)\n 大約的來回時間 (毫秒):\n 最小值 = 0ms最大值 = 0ms平均 = 0ms\n",
"time": 1,
"min": "0.000",
"max": "0.000",
"avg": "0.000",
"stddev": "1.000"
}
}