nginx_upstream_peers_active

When NGINX proxies to async application servers (FastAPI, Node.js) but those backends make blocking I/O calls, the event loop stalls, causing serial-like request processing despite async infrastructure. Symptoms include flat throughput curves and rising tail latency even when CPU is moderate.

When NGINX proxies to backends (PHP-FPM, FastCGI, uwsgi) without proper connection limits, a single site can exhaust the proxy connection pool, blocking other sites on shared infrastructure. Default mod_proxy behavior allows each child process to open max connections equal to ThreadsPerChild × ServerLimit.

When nginx_upstream_peers_response_time p95/p99 percentiles increase but nginx_upstream_peers_active stays low and backend resources (CPU, memory, database) appear healthy, the issue often lies in configuration inefficiencies: suboptimal keepalives, excessive DNS lookups, or poorly tuned caching.