Infrastructure Scenario Tests

We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.

21,502
Total Tests
100.0%
Pass Rate
21,502
Passed
0
Failed

Bun 1.1 Packet Loss Due to NIC Errors on AlmaLinux 9

PASS

Bun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.

ServerPattern: NIC_ERRORSSeverity: MEDIUMConfidence: 64%Auto-Heal

Caddy 2.8 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

Caddy 2.8 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

Apache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Bun 1.1 Packet Loss Due to NIC Errors on Oracle Linux 9

PASS

Bun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.

ServerPattern: NIC_ERRORSSeverity: MEDIUMConfidence: 64%Auto-Heal

Bun 1.1 Packet Loss Due to NIC Errors on CentOS 9 Stream

PASS

Bun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.

ServerPattern: NIC_ERRORSSeverity: MEDIUMConfidence: 64%Auto-Heal

Bun 1.1 Packet Loss Due to NIC Errors on Fedora 40 Server

PASS

Bun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.

ServerPattern: NIC_ERRORSSeverity: MEDIUMConfidence: 64%Auto-Heal

Caddy 2.8 Failed Graceful Shutdown — Killed with SIGKILL on Arch Linux

PASS

Caddy 2.8 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 24.04 LTS

PASS

Apache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on CentOS 9 Stream

PASS

Apache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Windows Server 2019

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Windows Server 2022

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Arch Linux

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Windows 11 Enterprise

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Windows 10 Enterprise

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Oracle Linux 9

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 22.04 LTS

PASS

Apache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on Rocky Linux 9

PASS

Apache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Amazon Linux 2023

PASS

Nginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal
PreviousPage 28 of 466Next

Every scenario is tested against Corax's Neural Engine in a production environment with AI-powered root cause analysis.

Tests run continuously as new infrastructure patterns are added.