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