mediumNewJPMorgan ChaseInfosysPhonePe

Connections through our load balancer reset after exactly 350 seconds of silence. Where do you look and what do you tune?

A reset at a suspiciously round number is a fingerprint, not a bug. Matching client keepalives to the lowest timer in the path is the fix; here is the full ladder of knobs.

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.

A reset at a suspiciously round number is a fingerprint, not a bug. Matching client keepalives to the lowest timer in the path is the fix; here is the full ladder of knobs.

20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25

UP NEXT ON YOUR JOURNEY

Next in this trackEvery connect() and every dropped SYN on a busy host, no agents installed. What can eBPF see that tcpdump cannot?Next in this trackWalk me through nginx internals: what do the master and workers each do, and how does one worker hold thousands of connections?Next in this trackA 25Gbps NIC tops out near 4Gbps while one core sits pinned in softirq. What is happening and how do you fix it?

DISCUSSION · 0

Nothing here yet. Say how you would answer it.