HTTP 460 Client Closed Connection (AWS ELB) — What It Means & How to Fix It

Fix AWS Elastic Load Balancer HTTP 460 error when the client closes the connection before the load balancer can send the response. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: HTTP 460 is an AWS-specific status code logged by Application Load Balancers (ALB). It occurs when the client closes the connection before the ALB can deliver the complete response. This is logged in ALB access logs but the client never sees a 460 response directly. High rates of 460 errors may indicate performance issues or aggressive client timeouts. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Client timeout is shorter than the backend processing time. Mobile users on unstable connections dropping requests mid-flight. Browser navigating away or cancelling requests before completion. Health check probes with short timeouts closing connections prematurely. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Review ALB access logs to identify which endpoints generate the most 460 errors. Increase the idle timeout on the ALB if backend responses are slow (default 60s). Optimize slow backend endpoints to respond faster and reduce client timeout risk. Check if automated clients or monitoring tools are closing connections prematurely. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.