BYOC Edge 502 Bad Gateway during high-concurrency API polling

Trying to understand why our BYOC edge deployment is returning 502 Bad Gateway errors when hitting the /v2/analytics/interactions endpoint with >50 concurrent requests.

The edge logs show successful upstream connections, but the response never reaches the client. Is there a known limit on concurrent outbound connections from the BYOC container that overrides the standard API rate limits?

You might want to check at the connection pooling settings in your load generator. The BYOC edge isn’t blocking the traffic, but the client-side socket exhaustion is causing the reset before the response arrives.

{
 "connection_pool_size": 5,
 "keep_alive_timeout_ms": 5000,
 "max_connections_per_route": 10
}