Find out why a pod is in CrashLoopBackOff
A crashing pod tells its story across status, exit codes, previous-container logs and events. Kubius pulls all of it into one live view so you can see the real cause - an OOM kill, a bad command, a failing probe - in seconds.
Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later
Everything a crash leaves behind, in one place
Restarts and reason at a glance
See the restart count climb live, the container's current and last state, the termination reason and exit code - CrashLoopBackOff, Error, OOMKilled - without digging.
Previous-container logs
Read the logs from the container instance that actually crashed, not just the one that's restarting. That's usually where the stack trace is.
OOM kills, called out
Exit 137 and out-of-memory kills are surfaced explicitly, with the memory limit and usage in context, so you know when it's a limits problem.
Events, in order
FailedScheduling, BackOff, probe failures and image-pull errors are listed newest-first against the pod, so the trigger is easy to spot.
Probes and limits, visible
Readiness/liveness/startup probes and resource requests/limits are rendered clearly - a mis-set probe or a tight limit is often the whole story.
Straight to the owner
Jump from a crashing pod to its Deployment, ReplicaSet or Job and back, so you can fix the template, not just the symptom.
Why Kubius for crash loops
From "why is it crashing?" to root cause in seconds
Live status, the right logs, and the events that explain it - together.
- Live restart count, last-state reason and exit code
- Logs from the previous (crashed) container instance
- OOMKilled / exit 137 surfaced with memory limit vs usage
- Pod events newest-first (BackOff, probe fails, image pull)
- One click to the owning workload to fix the template
- 14-day free trial, no card required
Simple, one-time pricing
Pay once. No subscription.
One-time licence from €49 - no subscription. 14-day free trial, no card required.
Free 14-day trial · macOS Sonoma (14) or later · No agents, nothing to install in-cluster
Questions, answered
How does Kubius help me debug CrashLoopBackOff?
It gathers everything a crash leaves behind - the container's last-state reason and exit code, the previous instance's logs, resource limits, probe config and the pod's events - into one live view, so you can identify the cause instead of stitching together kubectl commands.
Can I see the logs from before the container restarted?
Yes. Kubius reads the previous-container logs, which is where the crash's stack trace usually lives - the restarting instance often shows nothing useful.
Does it detect OOM kills?
Yes. Out-of-memory kills (exit 137 / OOMKilled) are called out explicitly alongside the container's memory limit and usage, so you can tell a memory problem from a crash.
Do I need Prometheus or any agents?
No. Kubius reads status, logs and events straight from the Kubernetes API and metrics from metrics-server if present - nothing to deploy into the cluster.