This is strictly a violation of the TCP specification

A network issue was debugged where connections going through CloudFlare would time out with a 522 HTTP error. The root cause of the problem was traced back to loopback congestion, which is not possible under normal circumstances due to the absence of buffering over loopback. Further investigation revealed that hundreds of CLOSE_WAIT sockets were present, indicating leaking sockets in the listening application. This issue caused some incoming connections to time out. The problem was resolved by addressing the socket leakage and ensuring proper handling of TCP states.