.NET services fail at peak in two quiet ways. Sync over async code blocks thread pool threads while CPU sits idle, and new HttpClient instances use up local ports. Start with Fix Thread Pool Starvation in .NET and ASP.NET Core.
- Fix HttpClient Socket Exhaustion in .NET
Reuse connections through IHttpClientFactory or one shared SocketsHttpHandler, so outbound calls stop running out of local ports at peak traffic.
- Fix Thread Pool Starvation in .NET and ASP.NET Core
Remove sync over async calls in ASP.NET Core and set a thread pool minimum, so requests stop queueing behind blocked threads while CPU sits idle.