All HTTP status codes

HTTP 408 Request Timeout

Client Error

The server gave up waiting for the client to finish sending the request. Servers often close the connection afterwards.

Defined in RFC 9110

Common causes

  • Slow or stalled client connections (poor networks, paused uploads)
  • Keep-alive connections idled past the server's request timeout

How to fix it

  1. Retry the request (it's safe to retry by definition)

  2. Increase client-side upload performance or chunk large bodies

  3. Tune server header/body timeout settings if legitimate clients are cut off

Related status codes

504 Gateway Timeout

A gateway/proxy didn't get a response from the upstream in time. The upstream may still be processing — the proxy just gave up waiting.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.