One saturated core on a proxy is rarely about raw traffic volume. It is a parallelism failure with three usual suspects, and the per-thread view names the culprit in minutes.
an account raises the per-topic limit · no card
← Incident Response & Production Debugging / 19
mediumNewCloudflareFlipkartSwiggy
Requests pile up at the nginx edge, one core is pegged at 100 percent, and the backends look bored. Walk me through it.
One saturated core on a proxy is rarely about raw traffic volume. It is a parallelism failure with three usual suspects, and the per-thread view names the culprit in minutes.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
UP NEXT ON YOUR JOURNEY
Next in this trackAfter last night's firewall cleanup, calls to one payment vendor hang instead of failing fast. Find the rule that did it.Next in this trackThe CI runner's Docker daemon crashed mid-build and refuses to start. Release is blocked. Get us shipping again.Next in this trackSame-node pod calls work, cross-node calls time out, and small probes pass while real requests hang. Find the break.
DISCUSSION · 0
Nothing here yet. Say how you would answer it.