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

PostgreSQL 16 Backup Job Failed — Retention at Risk on Ubuntu 24.04 LTS

PASS

PostgreSQL 16 backup job has been failing for 42 consecutive runs. No recent restore point available. Data protection gap growing.

DatabasePattern: BACKUP_FAILURESeverity: HIGHConfidence: 68%Auto-Heal

MySQL 8.4 Backup Job Failed — Retention at Risk on Amazon Linux 2023

PASS

MySQL 8.4 backup job has been failing for 9 consecutive runs. No recent restore point available. Data protection gap growing.

DatabasePattern: BACKUP_FAILURESeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Backup Job Failed — Retention at Risk on Windows 11 Enterprise

PASS

PostgreSQL 16 backup job has been failing for 24 consecutive runs. No recent restore point available. Data protection gap growing.

DatabasePattern: BACKUP_FAILURESeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Backup Job Failed — Retention at Risk on Windows Server 2019

PASS

PostgreSQL 16 backup job has been failing for 50 consecutive runs. No recent restore point available. Data protection gap growing.

DatabasePattern: BACKUP_FAILURESeverity: HIGHConfidence: 68%Auto-Heal

TimescaleDB 2.14 Container OOM Killed — Memory Limit Hit on Arch Linux

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Rocky Linux 9

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

TimescaleDB 2.14 Container OOM Killed — Memory Limit Hit on Fedora 40 Server

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on RHEL 9

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Rocky Linux 9

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on RHEL 9

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5

PASS

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

DatabasePattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal
PreviousPage 54 of 275Next

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.