Show HN: Crashloop Analyzer – paste Kubernetes logs to diagnose CrashLoopBackOff (crashloop-analyzer.vercel.app)
I built a small tool to speed up debugging Kubernetes CrashLoopBackOff errors.
Normally when a pod keeps restarting you end up jumping between: - kubectl logs - kubectl describe - events - docs
Crashloop Analyzer lets you paste pod logs or kubectl describe output and it highlights likely causes like:
• OOMKilled • ImagePullBackOff / ErrImagePull • missing environment/config values • port binding failures
It also suggests useful kubectl commands to investigate further.
The detection is deterministic first (pattern matching common failure modes) with optional AI-assisted explanation layered on top.
Live demo: https://crashloop-analyzer.vercel.app/
6 comments
[ 95.7 ms ] story [ 502 ms ] threadI built this because I noticed that many Kubernetes CrashLoopBackOff issues are detectable with simple log patterns.
Examples I see often:
OOMKilled
listen tcp :8080: bind: address already in use
missing environment variables or config files
permission errors
failing startup or readiness probes
Most of the time the root cause is already visible in `kubectl logs --previous`, but during an incident you still end up scanning a lot of output.
The tool does three things:
1. Detect known crash patterns in the logs
2. Map them to a likely root cause
3. Suggest next debugging steps
There is an optional AI explanation layer, but the detection itself is rule based.
There are also example logs already in the UI if you want to try it without grabbing logs from a cluster.
I am curious what patterns people run into most often when debugging CrashLoopBackOff issues. I would like to expand the rule set.