Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Windows Server 2022
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Arch Linux
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Fedora 40 Server
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Oracle Linux 9
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on AlmaLinux 9
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Caddy 2.8 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS
PASSCaddy 2.8 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Apache httpd 2.4 Container OOM Killed — Memory Limit Hit on Arch Linux
PASSApache httpd 2.4 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Apache httpd 2.4 Container OOM Killed — Memory Limit Hit on Fedora 40 Server
PASSApache httpd 2.4 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Apache httpd 2.4 Container OOM Killed — Memory Limit Hit on Oracle Linux 9
PASSApache httpd 2.4 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Apache httpd 2.4 Container OOM Killed — Memory Limit Hit on AlmaLinux 9
PASSApache httpd 2.4 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Apache httpd 2.4 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSApache httpd 2.4 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Apache httpd 2.4 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSApache httpd 2.4 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Apache httpd 2.4 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSApache httpd 2.4 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
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.