Corax
AboutGet 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 CategoriesServer (9315)Database (5486)Infrastructure (2435)queue (2320)cache (1740)Network (81)Cloud (78)Security (36)VoIP (7)Cascade (4)
All StatusPassedFailed

Bun 1.1 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 22.04 LTS

PASS

Bun 1.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Deno 1.42 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

Deno 1.42 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Deno 1.42 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9

PASS

Deno 1.42 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Deno 1.42 Failed Graceful Shutdown — Killed with SIGKILL on Amazon Linux 2023

PASS

Deno 1.42 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Deno 1.42 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9

PASS

Deno 1.42 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Deno 1.42 Failed Graceful Shutdown — Killed with SIGKILL on Oracle Linux 9

PASS

Deno 1.42 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Deno 1.42 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

Deno 1.42 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Deno 1.42 Failed Graceful Shutdown — Killed with SIGKILL on Debian 12 Bookworm

PASS

Deno 1.42 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Bun 1.1 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9

PASS

Bun 1.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Bun 1.1 Failed Graceful Shutdown — Killed with SIGKILL on CentOS 9 Stream

PASS

Bun 1.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on Windows Server 2022

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on Windows Server 2019

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on Oracle Linux 9

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on SUSE Enterprise 15 SP5

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on AlmaLinux 9

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on RHEL 9

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on Amazon Linux 2023

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Tomcat 10.1 Failed Graceful Shutdown — Killed with SIGKILL on Arch Linux

PASS

Tomcat 10.1 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Elixir (Phoenix) Failed Graceful Shutdown — Killed with SIGKILL on Arch Linux

PASS

Elixir (Phoenix) did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

ServerPattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal
PreviousPage 16 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.