Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Oracle Linux 9
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on Debian 12 Bookworm
PASSApache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9
PASSApache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on Amazon Linux 2023
PASSApache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Caddy 2.8 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9
PASSCaddy 2.8 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Caddy 2.8 Failed Graceful Shutdown — Killed with SIGKILL on Oracle Linux 9
PASSCaddy 2.8 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Caddy 2.8 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server
PASSCaddy 2.8 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on CentOS 9 Stream
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Debian 12 Bookworm
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Rocky Linux 9
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Apache httpd 2.4 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5
PASSApache httpd 2.4 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Caddy 2.8 Failed Graceful Shutdown — Killed with SIGKILL on Arch Linux
PASSCaddy 2.8 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
Bun 1.1 Packet Loss Due to NIC Errors on Oracle Linux 9
PASSBun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.
Bun 1.1 Packet Loss Due to NIC Errors on Fedora 40 Server
PASSBun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.
Bun 1.1 Packet Loss Due to NIC Errors on Arch Linux
PASSBun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.
Bun 1.1 Packet Loss Due to NIC Errors on AlmaLinux 9
PASSBun 1.1 is experiencing intermittent connectivity issues caused by NIC errors on the host's network interface.
Nginx 1.26 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 22.04 LTS
PASSNginx 1.26 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.
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.