Get started Dashboard

Troubleshooting. Step-by-step fixes for common production errors on AWS, Kubernetes, Cloudflare, Vercel, Postgres and the rest of a modern stack.

Troubleshooting guides start from a symptom you can see: an error code in the browser, a 504 from a serverless function, a database connection that keeps failing. Each one explains what the error means, the usual causes in order of how often they happen and the fix for each.

They are written for the engineer looking at the problem right now. Every guide shows the commands and code to find the cause, from tailing logs to tracing a slow request, then the change that fixes it and how to confirm the fix held. They cover Cloudflare Workers, Hyperdrive, Vercel functions, Kubernetes, Postgres and the other platforms teams deploy to most, and they say plainly when a problem is a platform limit and not your code. A guide that starts from one exact error message shows that message first, so you can check it matches yours.

How Polylane works on these platforms: Cloudflare, Vercel, Kubernetes, Supabase and Railway.

More guides

Kubernetes CrashLoopBackOff: causes and fixes

What CrashLoopBackOff means in Kubernetes, how to read the exit code and events behind it, and the fix for each common cause, from bad config to failing probes.

Boris Tane

How to debug Vercel function timeouts

Debug Vercel FUNCTION_INVOCATION_TIMEOUT 504s: find the slow call with vercel logs and httpstat, fix hangs, set maxDuration and verify on a preview.

Boris Tane

Nobody should be on-call. Polylane watches your infra, finds what broke, and writes the fix.

Get started for free