460 HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

AWS ALB 460 Client Closed Connection

The client closed the connection before the Application Load Balancer sent its response.

Exact message you may see ALB 460 client closed connection460 Client closed the connection with the load balancer before the idle timeout period elapsed
Seen on: AWS HTTP

Meaning

ALB returns 460 when the client disconnects, often because its timeout is shorter than the idle timeout or the backend is slow. Increase the client timeout, speed up the backend, or raise the ALB idle timeout (default 60 s).

Common causes

  • Client timeout shorter than ALB idle timeout
  • Slow backend response
  • Mobile client dropping connections
  • User closed the page
  • Long request without keepalive

⚡ Quick fix

  1. Raise the client timeout above the ALB idle timeout
  2. Speed up the slow endpoint
  3. Check HTTPCode_ELB_4XX_Count and access logs

Detailed fix by platform

AWS CLI

  1. aws elbv2 modify-load-balancer-attributes --load-balancer-arn ARN --attributes Key=idle_timeout.timeout_seconds,Value=120

How to diagnose

  1. Client timeout — Shorter?
  2. Backend latency — High?
  3. ALB idle timeout — Default 60 s?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

463 — AWS ALB 463 X-Forwarded-For header has too many IP addresses (HTTP)463494 — nginx 494 Request Header Or Cookie Too Large (HTTP)494496 — nginx 496 SSL Certificate Required (HTTP)496499 — HTTP 499 Client Closed Request (Nginx) (HTTP)499502 — Intermittent 502 caused by keep-alive timeout mismatch (HTTP)502504 — 504 Gateway Timeout from load balancer idle timeout (long request) (HTTP)504561 — AWS ALB 561 Unauthorized (identity provider error) (HTTP)561ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM region460

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.