A containerized service intermittently fails health checks under load, but logs show no errors and the application appears to be processing requests normally.

Consider whether the health check's own timeout is too aggressive relative to the application's response time under genuine load — if the healthcheck request itself gets queued behind real traffic and occasionally exceeds its timeout, that's a load-induced false-negative rather than an actual health problem; verify by checking healthcheck response times specifically during load spikes, and consider giving the healthcheck endpoint a separate, lighter-weight code path or thread pool so it isn't starved by application traffic.