Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
OpenResty 1.25 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS
PASSOpenResty 1.25 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Arch Linux
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Fedora 40 Server
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Oracle Linux 9
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on AlmaLinux 9
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
LiteSpeed 6.2 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS
PASSLiteSpeed 6.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Envoy 1.30 Container OOM Killed — Memory Limit Hit on Arch Linux
PASSEnvoy 1.30 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Envoy 1.30 Container OOM Killed — Memory Limit Hit on Fedora 40 Server
PASSEnvoy 1.30 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
.NET 8 (Kestrel) Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASS.NET 8 (Kestrel) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Envoy 1.30 Container OOM Killed — Memory Limit Hit on Oracle Linux 9
PASSEnvoy 1.30 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Envoy 1.30 Container OOM Killed — Memory Limit Hit on AlmaLinux 9
PASSEnvoy 1.30 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Envoy 1.30 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSEnvoy 1.30 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Envoy 1.30 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSEnvoy 1.30 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Envoy 1.30 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSEnvoy 1.30 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.