2026-09-02 23:44:05 | CRITICAL | 192.168.1.105 | IP CONFLICT | AA:BB:CC:11:22:33 → 11:22:33:44:55:66
2026-09-02 23:44:05 | CRITICAL | 192.168.1.105 | IP CONFLICT | AA:BB:CC:11:22:33 → 11:22:33:44:55:66
2026-09-02 23:44:05 | ERROR | 192.168.1.44 | OFFLINE | 14:32:17
2026-09-02 23:44:06 | INFO | 192.168.1.44 | ONLINE | duración caída: 14 s
2026-09-02 23:44:06 | WARNING | 192.168.1.48 | PACKET LOSS | 20%
2026-09-02 23:44:06 | CRITICAL | 192.168.1.46 | IP CONFLICT | AA:BB:CC:00:00:01 → AA:BB:CC:00:00:99
2026-09-02 23:44:06 | ERROR | 192.168.1.41 | OFFLINE | +0s
2026-09-02 23:44:06 | ERROR | 192.168.1.42 | OFFLINE | +2s
2026-09-02 23:44:06 | ERROR | 192.168.1.43 | OFFLINE | +4s
2026-09-02 23:44:06 | ERROR | 192.168.1.44 | OFFLINE | +6s
2026-09-02 23:44:06 | ERROR | 192.168.1.45 | OFFLINE | +8s
2026-09-02 23:44:06 | CRITICAL | - | CORRELACION | Se detecta patrón de múltiples dispositivos afectados (5 OFFLINE en ~60 s). Probable problema común de Wi-Fi/AP/router.