WhereGoes

408 Request Timeout

4xx client error

The server gave up waiting for the client to finish sending a request within its configured idle window, then usually closes the connection.

Common causes

  • Slow client uploads or a stalled body send.
  • Keep-alive idle limit shorter than the client's think time.
  • A lost network path between client and server.

How to fix it

  • Raise the keep-alive and body-read timeouts to realistic values.
  • Ask clients to retry, ideally on a fresh connection.
  • Check for middleboxes that hold connections open without data.

What it means for redirects and SEO

Timeouts burn crawl budget and can drop the URL if frequent. Slow origin responses are the usual reason. Reducing time to first byte usually clears these up.

Related codes