Probe Status
ONLINE
Home Princeton, Texas
120
MTM McKinney, Texas
16
Missing
23
External Targets
7
RAM Used
237 MB
670 MB available
Temperature
57.5°C
Free Storage
46.3 GB
HOME — 192.168.0.0/21
192.168.0.1 → 192.168.7.254
| Device | Status | IP Address | Hostname | MAC Address | Vendor | Latency | Last Seen | Finding |
|---|---|---|---|---|---|---|---|---|
| 🔎 | MISSING | 192.168.0.154 | — | dc:1e:d5:3c:f3:6c | (Unknown) | — | 2026-10-29 12:43:11 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.0.218 | — | 6e:fa:9b:bf:e4:15 | (Unknown: locally administered) | — | 2026-10-30 05:32:45 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.0.220 | — | 6e:fa:9b:bf:e4:15 | (Unknown: locally administered) | 4.9 ms | 2026-10-31 07:45:45 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.0.23 | — | 16:b3:7d:41:9a:b1 | (Unknown: locally administered) | 14.8 ms | 2026-10-31 07:45:45 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.1.252 | — | 40:89:c6:8b:cf:46 | (Unknown) | 29.6 ms | 2026-10-29 02:22:40 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.2.3 | — | 22:15:52:8d:8a:47 | (Unknown: locally administered) | 2.4 ms | 2026-10-30 08:02:55 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.2.5 | — | 22:15:52:8d:8a:47 | (Unknown: locally administered) | 3.4 ms | 2026-10-31 08:01:36 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.3.221 | — | 26:65:02:f0:bd:9f | (Unknown: locally administered) | 107.0 ms | 2026-10-28 06:23:48 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.3.242 | — | 32:c9:b0:09:9f:3d | (Unknown: locally administered) | — | 2026-10-25 08:43:04 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.3.79 | — | 1a:2c:25:d3:e6:c1 | (Unknown: locally administered) | 53.8 ms | 2026-10-29 04:41:34 | No discovery, ping or TCP response for 60+ minutes |
| 🌐 | MISSING | 192.168.4.1 | — | f4:cf:a2:51:96:5b | Espressif Inc. | — | 2026-10-25 22:10:43 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.4.146 | — | c0:99:c5:ea:9f:38 | (Unknown) | — | 2026-10-27 20:30:25 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.4.234 | — | 84:47:09:54:78:e5 | Shenzhen IP3 Century Intelligent Technology CO.,Ltd | 0.4 ms | 2026-10-25 09:44:34 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.5.41 | — | e8:8f:6f:00:93:8b | TCT mobile ltd | 245.0 ms | 2026-10-30 05:28:10 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.5.43 | — | e8:8f:6f:00:93:8b | TCT mobile ltd | 96.4 ms | 2026-10-31 07:46:18 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.5.81 | — | 2a:0a:cc:6e:5c:77 | (Unknown: locally administered) | 2.8 ms | 2026-10-29 04:41:38 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.6.104 | — | ae:06:3a:60:32:c1 | (Unknown: locally administered) | — | 2026-10-26 16:08:14 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.6.148 | — | d4:63:fe:c8:42:19 | Arcadyan Corporation | 1.8 ms | 2026-10-31 02:52:52 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.6.219 | — | 84:47:09:80:c0:d3 | Shenzhen IP3 Century Intelligent Technology CO.,Ltd | 0.8 ms | 2026-10-30 14:19:42 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.7.79 | — | 4a:78:1d:02:3d:47 | (Unknown: locally administered) | — | 2026-10-30 05:28:20 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | MISSING | 192.168.7.81 | — | 4a:78:1d:02:3d:47 | (Unknown: locally administered) | — | 2026-10-31 07:05:27 | No discovery, ping or TCP response for 60+ minutes |
| 🌐 | UP | 192.168.0.1 | — | cc:28:aa:5d:ad:68 | (Unknown) | 0.7 ms | 2026-10-31 11:53:02 | |
| 🖥️ | UP | 192.168.0.10 | — | c8:ff:bf:0c:1b:4f | (Unknown) | 0.8 ms | 2026-10-31 11:53:02 | |
| 🖥️ | UP | 192.168.0.100 | — | c4:65:16:9b:9f:b2 | Hewlett Packard | 0.4 ms | 2026-10-31 11:53:03 | |
| 📷 | UP | 192.168.0.12 | — | 10:7c:61:49:bd:b3 | (Unknown) | 0.4 ms | 2026-10-31 11:53:03 | |
| 🔎 | UP | 192.168.0.158 | — | 38:54:f5:73:41:2d | (Unknown) | — | 2026-10-31 11:42:44 | |
| ☎️ | UP | 192.168.0.200 | — | 00:15:65:f4:8b:27 | XIAMEN YEALINK NETWORK TECHNOLOGY CO.,LTD | 0.6 ms | 2026-10-31 11:53:04 | |
| 🖥️ | UP | 192.168.0.22 | — | 84:47:09:84:01:78 | Shenzhen IP3 Century Intelligent Technology CO.,Ltd | 0.9 ms | 2026-10-31 11:53:04 | |
| 💡 | UP | 192.168.0.3 | — | 14:91:38:64:10:c1 | Amazon Technologies Inc. | — | 2026-10-31 11:53:04 | |
| 💡 | UP | 192.168.0.57 | — | 30:ae:a4:9f:67:e4 | Espressif Inc. | 2.4 ms | 2026-10-31 11:53:06 | |
| 💡 | UP | 192.168.0.59 | — | d4:36:39:8c:fe:b5 | Texas Instruments | 804.0 ms | 2026-10-31 11:47:58 | High latency: 804.0 ms |
| 🌐 | UP | 192.168.1.1 | — | 2c:cf:67:c1:39:4c | (Unknown) | 0.4 ms | 2026-10-31 11:53:06 | |
| 💡 | UP | 192.168.1.10 | — | 08:84:9d:d8:ec:1e | Amazon Technologies Inc. | — | 2026-10-31 11:53:07 | |
| 📺 | UP | 192.168.1.110 | — | f8:77:b8:d5:06:38 | Samsung Electronics Co.,Ltd | 0.5 ms | 2026-10-31 11:53:08 | |
| 🖥️ | UP | 192.168.1.12 | — | c8:ff:bf:0f:bf:49 | (Unknown) | 0.4 ms | 2026-10-31 11:53:09 | |
| 💡 | UP | 192.168.1.131 | — | b0:f7:c4:09:77:02 | Amazon Technologies Inc. | 2.0 ms | 2026-10-31 11:53:09 | |
| 💡 | UP | 192.168.1.154 | — | 60:38:e0:44:d3:c5 | Belkin International Inc. | 1.8 ms | 2026-10-31 11:53:10 | |
| 🔎 | UP | 192.168.1.155 | — | 98:22:ef:0e:94:7b | Liteon Technology Corporation | 2.9 ms | 2026-10-31 11:53:10 | |
| 🔀 | UP | 192.168.1.167 | — | 50:eb:f6:11:72:70 | ASUSTek COMPUTER INC. | 0.7 ms | 2026-10-31 11:53:10 | |
| 💡 | UP | 192.168.1.170 | — | cc:6a:10:f0:73:08 | The Chamberlain Group, Inc | — | 2026-10-31 11:48:04 | |
| 🔀 | UP | 192.168.1.183 | — | 1c:61:b4:f8:43:b2 | TP-Link Corporation Limited | 1.8 ms | 2026-10-31 11:53:11 | |
| 📷 | UP | 192.168.1.188 | — | 00:12:31:ac:4c:f6 | Motion Control Systems, Inc. | 0.7 ms | 2026-10-31 11:53:11 | |
| 📷 | UP | 192.168.1.189 | — | 00:12:31:ac:52:4c | Motion Control Systems, Inc. | 0.7 ms | 2026-10-31 11:53:12 | |
| ☎️ | UP | 192.168.1.197 | — | ec:74:d7:ec:1b:f1 | Grandstream Networks Inc | — | 2026-10-31 11:53:12 | |
| 🖥️ | UP | 192.168.1.2 | — | 2c:cf:67:00:08:34 | (Unknown) | 0.4 ms | 2026-10-31 11:53:14 | |
| 🔎 | UP | 192.168.1.200 | — | 0e:7c:de:5f:a0:17 | (Unknown: locally administered) | 3.5 ms | 2026-10-31 11:22:14 | |
| 🔎 | UP | 192.168.1.254 | — | 40:89:c6:8b:cf:46 | (Unknown) | 2.3 ms | 2026-10-31 11:53:14 | |
| 🖥️ | UP | 192.168.1.3 | — | e4:e7:49:3a:73:1c | Hewlett Packard | 1.1 ms | 2026-10-31 11:53:14 | |
| 🖥️ | UP | 192.168.1.4 | — | 98:fe:54:35:5d:4e | (Unknown) | 0.5 ms | 2026-10-31 11:53:15 | |
| 🔎 | UP | 192.168.1.42 | — | 6c:c8:40:dd:23:b0 | (Unknown) | — | 2026-10-31 11:53:15 | |
| 👁️ | UP | 192.168.1.5 | — | — | — | 0.1 ms | 2026-10-31 11:53:17 | |
| 📷 | UP | 192.168.1.52 | — | 00:12:31:ac:53:13 | Motion Control Systems, Inc. | 0.6 ms | 2026-10-31 11:53:17 | |
| 💡 | UP | 192.168.1.54 | — | a4:cf:12:e4:10:bb | Espressif Inc. | 18.3 ms | 2026-10-31 11:53:18 | |
| 📷 | UP | 192.168.1.9 | — | f0:00:06:00:db:17 | (Unknown) | 0.5 ms | 2026-10-31 11:53:18 | |
| 💡 | UP | 192.168.2.105 | — | 08:84:9d:49:0b:6a | Amazon Technologies Inc. | — | 2026-10-31 11:53:19 | |
| 💻 | UP | 192.168.2.12 | — | 84:47:09:56:42:94 | Shenzhen IP3 Century Intelligent Technology CO.,Ltd | 0.4 ms | 2026-10-31 11:53:20 | |
| 🔎 | UP | 192.168.2.134 | — | dc:1e:d5:3d:6b:18 | (Unknown) | — | 2026-10-31 11:53:20 | |
| 🔎 | UP | 192.168.2.140 | — | 18:de:50:4a:be:c1 | (Unknown) | 54.0 ms | 2026-10-31 11:53:22 | |
| 💡 | UP | 192.168.2.173 | — | 0c:95:05:4c:57:e9 | The Chamberlain Group, Inc | 1.2 ms | 2026-10-31 11:53:22 | |
| 💡 | UP | 192.168.2.18 | — | 50:02:91:ba:dd:dc | Espressif Inc. | 3.4 ms | 2026-10-31 11:53:23 | |
| 💡 | UP | 192.168.2.244 | — | 10:5a:17:89:be:c8 | Tuya Smart Inc. | 41.4 ms | 2026-10-31 11:53:23 | |
| 💡 | UP | 192.168.2.55 | — | 14:91:38:41:47:5c | Amazon Technologies Inc. | — | 2026-10-31 11:53:24 | |
| 🖨️ | UP | 192.168.3.12 | — | c8:ff:bf:0e:8e:9f | (Unknown) | 0.4 ms | 2026-10-31 11:53:25 | |
| 💡 | UP | 192.168.3.165 | — | d8:bf:c0:d2:49:be | Espressif Inc. | 4.5 ms | 2026-10-31 11:53:26 | |
| 🔎 | UP | 192.168.3.169 | — | 18:de:50:9b:48:be | (Unknown) | 21.3 ms | 2026-10-31 11:53:26 | |
| 💡 | UP | 192.168.3.188 | — | 80:c5:f2:a0:70:0e | AzureWave Technology Inc. | 3.8 ms | 2026-10-31 11:53:26 | |
| 📷 | UP | 192.168.3.192 | — | f0:00:05:26:b4:c7 | (Unknown) | 0.5 ms | 2026-10-31 11:37:58 | |
| 💡 | UP | 192.168.3.229 | — | 60:01:94:98:ba:bd | Espressif Inc. | 1.3 ms | 2026-10-31 11:53:27 | |
| 📷 | UP | 192.168.3.240 | — | f0:00:05:26:b4:f7 | (Unknown) | 2.9 ms | 2026-10-31 11:53:27 | |
| 💡 | UP | 192.168.3.244 | — | 68:db:f5:86:f4:7d | Amazon Technologies Inc. | — | 2026-10-31 11:53:28 | |
| 🖥️ | UP | 192.168.3.33 | — | c8:ff:bf:0c:1f:e0 | (Unknown) | 0.7 ms | 2026-10-31 11:53:29 | |
| 🔎 | UP | 192.168.3.34 | — | 44:a9:2c:50:53:23 | Shenzhen Lianfaxun Electronic Technology Co.,Ltd | 0.6 ms | 2026-10-31 11:53:30 | |
| 🔎 | UP | 192.168.3.56 | — | 18:de:50:a8:06:5b | (Unknown) | 43.6 ms | 2026-10-31 11:53:30 | |
| 💡 | UP | 192.168.3.78 | — | 10:bb:f3:c8:a3:ec | HUNAN FN-LINK TECHNOLOGY LIMITED | 2.4 ms | 2026-10-31 11:53:30 | |
| 🖥️ | UP | 192.168.4.12 | — | 84:47:09:54:76:58 | Shenzhen IP3 Century Intelligent Technology CO.,Ltd | 0.3 ms | 2026-10-31 11:53:31 | |
| ⚙️ | UP | 192.168.4.24 | — | 5c:15:c5:0f:1a:1b | (Unknown) | 4.6 ms | 2026-10-31 11:53:31 | |
| 🔎 | UP | 192.168.4.254 | — | f0:2f:9e:c1:17:33 | (Unknown) | — | 2026-10-31 11:53:32 | |
| 🔎 | UP | 192.168.4.27 | — | e0:b9:4d:52:f0:db | SHENZHEN BILIAN ELECTRONIC CO.，LTD | 1.8 ms | 2026-10-31 11:53:33 | |
| 🖥️ | UP | 192.168.5.12 | — | c8:ff:bf:0c:1b:b6 | (Unknown) | 0.4 ms | 2026-10-31 11:53:34 | |
| 🔎 | UP | 192.168.5.144 | — | 18:de:50:9a:0a:0f | (Unknown) | 23.9 ms | 2026-10-31 11:53:34 | |
| 🔎 | UP | 192.168.5.148 | — | 6c:c8:40:dd:04:64 | (Unknown) | 39.0 ms | 2026-10-31 11:53:34 | |
| 🔎 | UP | 192.168.5.212 | — | 18:de:50:9a:17:3d | (Unknown) | 18.9 ms | 2026-10-31 11:53:35 | |
| 💡 | UP | 192.168.5.222 | — | 74:d6:37:6b:5e:f9 | Amazon Technologies Inc. | — | 2026-10-31 11:53:35 | |
| 💡 | UP | 192.168.5.223 | — | 84:f3:eb:57:69:36 | Espressif Inc. | 2.9 ms | 2026-10-31 11:53:37 | |
| 💡 | UP | 192.168.5.232 | — | 60:6d:3c:04:1b:2b | Luxshare Precision Industry Company Limited | 1.3 ms | 2026-10-31 11:53:37 | |
| ☎️ | UP | 192.168.5.236 | — | 6c:60:eb:ef:fb:a8 | ZHI YUAN ELECTRONICS CO., LIMITED | 1.4 ms | 2026-10-31 11:53:38 | |
| 🔎 | UP | 192.168.5.251 | — | 18:de:50:99:fd:2d | (Unknown) | 24.4 ms | 2026-10-31 11:53:38 | |
| 🔎 | UP | 192.168.5.52 | — | e0:b9:4d:52:e6:2d | SHENZHEN BILIAN ELECTRONIC CO.，LTD | 2.2 ms | 2026-10-31 11:53:39 | |
| 📷 | UP | 192.168.5.55 | — | 00:70:08:ad:61:ee | (Unknown) | 0.6 ms | 2026-10-31 11:48:32 | |
| 🔎 | UP | 192.168.5.66 | — | dc:1e:d5:3e:f2:04 | (Unknown) | — | 2026-10-31 11:53:39 | |
| 🔎 | UP | 192.168.5.97 | — | 6c:c8:40:dd:2a:8c | (Unknown) | 18.5 ms | 2026-10-31 11:33:00 | |
| 🖥️ | UP | 192.168.6.12 | — | 84:47:09:4a:75:b4 | Shenzhen IP3 Century Intelligent Technology CO.,Ltd | 0.5 ms | 2026-10-31 11:53:40 | |
| 📷 | UP | 192.168.6.158 | — | f0:00:05:26:5f:85 | (Unknown) | 0.5 ms | 2026-10-31 11:48:34 | |
| 🔀 | UP | 192.168.6.176 | — | 0c:9d:92:2c:81:38 | ASUSTek COMPUTER INC. | 0.6 ms | 2026-10-31 11:53:41 | |
| 🔎 | UP | 192.168.6.2 | — | 6c:c8:40:dc:1d:1c | (Unknown) | 4.9 ms | 2026-10-31 11:53:41 | |
| 🔎 | UP | 192.168.6.205 | — | 6c:c8:40:dd:ed:b0 | (Unknown) | 5.3 ms | 2026-10-31 11:53:42 | |
| 💡 | UP | 192.168.6.221 | — | 60:38:e0:44:ba:e5 | Belkin International Inc. | 1.7 ms | 2026-10-31 11:53:42 | |
| 💡 | UP | 192.168.6.254 | — | 44:bb:3b:5c:4d:8b | Google, Inc. | — | 2026-10-31 11:48:36 | |
| ☎️ | UP | 192.168.6.47 | — | c4:fc:22:3d:78:d3 | YEALINK(XIAMEN) NETWORK TECHNOLOGY CO.,LTD. | 2.7 ms | 2026-10-31 11:53:43 | |
| ⚙️ | UP | 192.168.6.6 | — | 5c:15:c5:05:3f:53 | (Unknown) | 4.7 ms | 2026-10-31 11:48:38 | |
| 💡 | UP | 192.168.6.65 | — | 38:1f:8d:18:db:2f | Tuya Smart Inc. | 1.7 ms | 2026-10-31 11:53:43 | |
| 📷 | UP | 192.168.6.66 | — | 00:67:46:26:50:59 | (Unknown) | 0.6 ms | 2026-10-31 11:53:44 | |
| 🖨️ | UP | 192.168.6.90 | — | 58:05:d9:2d:38:93 | (Unknown) | 0.8 ms | 2026-10-31 11:53:44 | |
| ☎️ | UP | 192.168.7.10 | — | c4:65:16:ae:49:1f | Hewlett Packard | 0.8 ms | 2026-10-31 11:53:44 | |
| 🔎 | UP | 192.168.7.105 | — | a0:28:d0:70:0d:01 | (Unknown) | — | 2026-10-31 11:53:45 | |
| 🔎 | UP | 192.168.7.133 | — | 18:de:50:9a:1a:11 | (Unknown) | 78.9 ms | 2026-10-31 11:53:46 | |
| 🖥️ | UP | 192.168.7.148 | — | fc:3f:db:0b:59:b0 | Hewlett Packard | 0.7 ms | 2026-10-31 11:53:47 | |
| ☎️ | UP | 192.168.7.15 | — | 80:5e:c0:71:2d:21 | YEALINK(XIAMEN) NETWORK TECHNOLOGY CO.,LTD. | 0.6 ms | 2026-10-31 11:53:47 | |
| 🔎 | UP | 192.168.7.167 | — | 18:de:50:4b:61:de | (Unknown) | 23.7 ms | 2026-10-31 11:53:48 | |
| ☎️ | UP | 192.168.7.17 | — | 80:5e:c0:3e:fc:20 | YEALINK(XIAMEN) NETWORK TECHNOLOGY CO.,LTD. | 0.5 ms | 2026-10-31 11:53:48 | |
| ☎️ | UP | 192.168.7.18 | — | 00:15:65:b4:84:6a | XIAMEN YEALINK NETWORK TECHNOLOGY CO.,LTD | 0.7 ms | 2026-10-31 11:53:49 | |
| 🔎 | UP | 192.168.7.198 | — | 60:56:ee:15:0f:3c | (Unknown) | — | 2026-10-31 11:48:42 | |
| 🖥️ | UP | 192.168.7.20 | — | b0:5c:da:2b:53:38 | HP Inc. | 1.2 ms | 2026-10-31 11:53:49 | |
| 🔎 | UP | 192.168.7.33 | — | 8c:2a:85:c6:92:56 | (Unknown) | 9.3 ms | 2026-10-31 11:53:49 | |
| ⚙️ | UP | 192.168.7.50 | — | c0:99:27:75:2d:3a | (Unknown) | 0.7 ms | 2026-10-31 11:38:21 | |
| 📷 | UP | 192.168.7.51 | — | c0:99:df:4b:0b:72 | (Unknown) | 0.6 ms | 2026-10-31 11:53:50 | |
| 📷 | UP | 192.168.7.52 | — | c0:99:37:04:14:b2 | (Unknown) | 0.5 ms | 2026-10-31 11:43:31 | |
| 📷 | UP | 192.168.7.53 | — | c0:99:87:cb:7c:c9 | (Unknown) | 0.5 ms | 2026-10-31 11:43:31 | |
| 📷 | UP | 192.168.7.54 | — | c0:99:5e:3b:10:69 | (Unknown) | 0.6 ms | 2026-10-31 11:43:32 | |
| 🔎 | UP | 192.168.7.77 | — | e0:51:d8:14:9e:36 | China Dragon Technology Limited | 0.6 ms | 2026-10-31 11:53:50 |
WIFE-SITE — 192.168.50.0/24
VPN-routed network
| Device | Status | IP Address | Hostname | Latency | Last Seen | Finding |
|---|---|---|---|---|---|---|
| ⚙️ | UP | 192.168.50.107 | — | 34.3 ms | 2026-10-31 11:56:56 | |
| 🔎 | UP | 192.168.50.114 | — | — | 2026-10-31 11:56:56 | |
| 📷 | UP | 192.168.50.117 | — | 28.4 ms | 2026-10-31 11:56:58 | |
| 📷 | UP | 192.168.50.144 | — | 26.3 ms | 2026-10-31 11:56:58 | |
| ☎️ | UP | 192.168.50.171 | — | 26.5 ms | 2026-10-31 11:56:59 | |
| 🔎 | UP | 192.168.50.172 | — | — | 2026-10-31 11:50:04 | |
| 🔎 | MISSING | 192.168.50.174 | — | 36.3 ms | 2026-10-29 18:33:09 | No discovery, ping or TCP response for 60+ minutes |
| 🔎 | UP | 192.168.50.186 | — | — | 2026-10-31 11:44:41 | |
| 🔎 | UP | 192.168.50.226 | — | 29.7 ms | 2026-10-31 11:56:59 | |
| 🔎 | UP | 192.168.50.229 | — | 33.1 ms | 2026-10-31 11:57:00 | |
| 🔎 | MISSING | 192.168.50.24 | — | 141.0 ms | 2026-10-24 18:13:34 | No discovery, ping or TCP response for 60+ minutes |
| 🖨️ | UP | 192.168.50.244 | — | 26.5 ms | 2026-10-31 11:57:00 | |
| 🔎 | UP | 192.168.50.42 | — | 87.2 ms | 2026-10-31 11:57:01 | |
| 🔎 | UP | 192.168.50.6 | — | 75.2 ms | 2026-10-31 11:39:23 | |
| 🔎 | UP | 192.168.50.62 | — | 32.7 ms | 2026-10-31 11:57:02 | |
| 🔎 | UP | 192.168.50.72 | — | — | 2026-10-31 11:50:08 |
External / Website / API Monitoring
/etc/peakaboo-probe/external-targets.txt
| Status | Target | Resolved IP | HTTP | Latency | Last Check | Message |
|---|---|---|---|---|---|---|
| UP | 1.1.1.1 | 1.1.1.1 | — | 13.7 ms | 2026-10-31 11:57:11 | Reachable |
| UP | 8.8.8.8 | 8.8.8.8 | — | 6.8 ms | 2026-10-31 11:57:10 | Reachable |
| UP | https://aliensoft.us | 76.209.14.37 | 200 | 454.6 ms | 2026-10-31 11:57:12 | HTTP 200 |
| UP | https://majesticthaimassage.us | 76.209.14.36 | 200 | 970.1 ms | 2026-10-31 11:57:13 | HTTP 200 |
| UP | https://peakaboo.us | 76.209.14.36 | 200 | 483.8 ms | 2026-10-31 11:57:11 | HTTP 200 |
| UP | https://skworm.us | 76.209.14.37 | 200 | 457.8 ms | 2026-10-31 11:57:12 | HTTP 200 |
| UP | https://tools.aliensoft.us | 76.209.14.37 | 200 | 482.0 ms | 2026-10-31 11:57:13 | HTTP 200 |
Recent Findings
| Time | Severity | Type | Target | Message |
|---|---|---|---|---|
| 2026-10-31 11:07:56 | WARNING | DEVICE_MISSING | 192.168.50.172 | 192.168.50.172 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 10:11:34 | WARNING | DEVICE_MISSING | 192.168.1.200 | 192.168.1.200 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 09:04:57 | WARNING | DEVICE_MISSING | 192.168.2.5 | 192.168.2.5 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 08:49:17 | WARNING | DEVICE_MISSING | 192.168.5.43 | 192.168.5.43 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 08:49:17 | WARNING | DEVICE_MISSING | 192.168.0.220 | 192.168.0.220 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 08:49:17 | WARNING | DEVICE_MISSING | 192.168.0.23 | 192.168.0.23 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 08:08:34 | WARNING | DEVICE_MISSING | 192.168.7.81 | 192.168.7.81 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 07:03:52 | WARNING | DEVICE_MISSING | 192.168.7.81 | 192.168.7.81 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 06:56:38 | WARNING | DEVICE_MISSING | 192.168.50.186 | 192.168.50.186 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 06:56:38 | WARNING | DEVICE_MISSING | 192.168.50.114 | 192.168.50.114 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 06:12:19 | WARNING | DEVICE_MISSING | 192.168.0.220 | 192.168.0.220 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 05:44:32 | WARNING | DEVICE_MISSING | 192.168.1.200 | 192.168.1.200 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 05:18:54 | WARNING | DEVICE_MISSING | 192.168.50.114 | 192.168.50.114 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 05:15:53 | WARNING | DEVICE_MISSING | 192.168.2.5 | 192.168.2.5 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 04:17:35 | WARNING | DEVICE_MISSING | 192.168.50.186 | 192.168.50.186 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 03:56:17 | WARNING | DEVICE_MISSING | 192.168.2.5 | 192.168.2.5 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 03:56:16 | WARNING | DEVICE_MISSING | 192.168.6.148 | 192.168.6.148 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 03:04:24 | WARNING | DEVICE_MISSING | 192.168.1.170 | 192.168.1.170 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 02:54:11 | WARNING | DEVICE_MISSING | 192.168.1.200 | 192.168.1.200 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 02:38:13 | WARNING | DEVICE_MISSING | 192.168.50.114 | 192.168.50.114 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 02:07:34 | WARNING | DEVICE_MISSING | 192.168.7.81 | 192.168.7.81 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-31 01:50:32 | INFO | NEW_DEVICE | 192.168.1.254 | New device discovered on HOME: 192.168.1.254 |
| 2026-10-31 00:56:18 | WARNING | DEVICE_MISSING | 192.168.2.5 | 192.168.2.5 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 23:53:13 | WARNING | DEVICE_MISSING | 192.168.6.148 | 192.168.6.148 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 23:06:50 | WARNING | DEVICE_MISSING | 192.168.1.170 | 192.168.1.170 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 22:56:23 | WARNING | DEVICE_MISSING | 192.168.7.198 | 192.168.7.198 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 22:51:07 | WARNING | DEVICE_MISSING | 192.168.50.186 | 192.168.50.186 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 22:10:01 | WARNING | DEVICE_MISSING | 192.168.50.6 | 192.168.50.6 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 22:10:01 | WARNING | DEVICE_MISSING | 192.168.50.172 | 192.168.50.172 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 22:10:01 | WARNING | DEVICE_MISSING | 192.168.50.42 | 192.168.50.42 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 21:53:40 | INFO | NEW_DEVICE | 192.168.2.5 | New device discovered on HOME: 192.168.2.5 |
| 2026-10-30 21:48:57 | INFO | NEW_DEVICE | 192.168.7.81 | New device discovered on HOME: 192.168.7.81 |
| 2026-10-30 21:48:43 | INFO | NEW_DEVICE | 192.168.5.43 | New device discovered on HOME: 192.168.5.43 |
| 2026-10-30 21:48:07 | INFO | NEW_DEVICE | 192.168.0.220 | New device discovered on HOME: 192.168.0.220 |
| 2026-10-30 21:19:15 | WARNING | DEVICE_MISSING | 192.168.50.186 | 192.168.50.186 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 20:01:24 | WARNING | DEVICE_MISSING | 192.168.1.170 | 192.168.1.170 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 19:56:16 | WARNING | DEVICE_MISSING | 192.168.7.198 | 192.168.7.198 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 18:48:56 | WARNING | DEVICE_MISSING | 192.168.50.172 | 192.168.50.172 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 18:28:14 | WARNING | DEVICE_MISSING | 192.168.50.186 | 192.168.50.186 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 16:50:42 | WARNING | DEVICE_MISSING | 192.168.7.105 | 192.168.7.105 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 16:23:32 | WARNING | MAC_CHANGE | 192.168.3.34 | 192.168.3.34 changed MAC from 84:47:09:80:c0:d3 to 44:a9:2c:50:53:23 |
| 2026-10-30 15:23:16 | WARNING | DEVICE_MISSING | 192.168.6.219 | 192.168.6.219 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 15:17:34 | WARNING | DEVICE_MISSING | 192.168.50.172 | 192.168.50.172 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 15:02:18 | WARNING | DEVICE_MISSING | 192.168.7.105 | 192.168.7.105 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 14:51:19 | WARNING | DEVICE_MISSING | 192.168.5.97 | 192.168.5.97 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 14:36:07 | WARNING | DEVICE_MISSING | 192.168.0.12 | 192.168.0.12 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 14:24:39 | INFO | NEW_DEVICE | 192.168.3.34 | New device discovered on HOME: 192.168.3.34 |
| 2026-10-30 14:20:36 | WARNING | DEVICE_MISSING | 192.168.50.114 | 192.168.50.114 has not responded to discovery or verification for more than 60 minutes |
| 2026-10-30 13:48:50 | INFO | NEW_DEVICE | 192.168.6.219 | New device discovered on HOME: 192.168.6.219 |
| 2026-10-30 13:44:41 | WARNING | DEVICE_MISSING | 192.168.5.97 | 192.168.5.97 has not responded to discovery or verification for more than 60 minutes |