About Get Started

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

All Categories Server (9315)Database (5486)Infrastructure (2435)queue (2320)cache (1740)Network (81)Cloud (78)Security (36)VoIP (7)Cascade (4)

All Status Passed Failed

Tomcat 10.1 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm

Tomcat 10.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Tomcat 10.1 Container OOM Killed — Memory Limit Hit on Rocky Linux 9

Tomcat 10.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Tomcat 10.1 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream

Tomcat 10.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Tomcat 10.1 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

Tomcat 10.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Tomcat 10.1 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

Tomcat 10.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on Arch Linux

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on Fedora 40 Server

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on Oracle Linux 9

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on AlmaLinux 9

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on Amazon Linux 2023

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on RHEL 9

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on Rocky Linux 9

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on CentOS 9 Stream

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Elixir (Phoenix) Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

Elixir (Phoenix) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Rust (Actix-Web) Container OOM Killed — Memory Limit Hit on Arch Linux

Rust (Actix-Web) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Rust (Actix-Web) Container OOM Killed — Memory Limit Hit on Fedora 40 Server

Rust (Actix-Web) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Rust (Actix-Web) Container OOM Killed — Memory Limit Hit on Oracle Linux 9

Rust (Actix-Web) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Rust (Actix-Web) Container OOM Killed — Memory Limit Hit on AlmaLinux 9

Rust (Actix-Web) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

PreviousPage 72 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.