← Problem Library
Network L4 NETWORK-018 · 20 min

A proxy keepalive setting difference makes latency spike for only certain APIs

A situation where, on the same server, only some paths are unusually slow because of a difference in upstream connection reuse policy.

NetworkPlatform ReliabilityLevel 4Pro20 min
Scenario

A scenario that narrows down the root cause, centered on checking the correlation between connection-reuse policy and latency variance, in the situation of a proxy keepalive setting difference making latency spike for only certain APIs.

What to check first
  • Identify the primary failure signal in the Connection Reuse scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.