HTTP 408

HTTP 408 Request Timeout โ€” Meaning, Causes & How to Fix

The server timed out waiting for the request; the client did not produce one in time.

Code
408
Name
Request Timeout
Class
4xx Client Error
Specification
RFC 9110 ยง15.5.9
Cacheable by default
Only with explicit Cache-Control / Expires

What HTTP 408 means

408 Request Timeout means the client was too slow: the server gave up waiting for the complete request and is closing the connection. It is different from 504, where a gateway waited too long for an upstream server.

Common causes

How to fix it

For site owners

For visitors & developers

SEO impact

Occasional 408s are harmless. Frequent ones in crawl logs suggest the server or network is struggling, which can reduce how much Googlebot crawls.

Example 408 response

HTTP/1.1 408 Request Timeout
Connection: close
Content-Length: 0

Related status codes

504 ยท Gateway Timeout429 ยท Too Many Requests400 ยท Bad Request401 ยท Unauthorized402 ยท Payment Required403 ยท Forbidden404 ยท Not Found405 ยท Method Not Allowed

Check or look up another code

Search and filter every code in the HTTP Status Codes tool, browse the full list by class, or read HTTP status codes explained: the complete developer guide.

Open HTTP Status Codes tool โ†’All status codes

Frequently asked questions

What does HTTP 408 mean?

HTTP 408 Request Timeout is a 4xx Client Error status code. The server timed out waiting for the request; the client did not produce one in time.

What is the difference between 408 and 504?

408: the server waited too long for the client. 504: a proxy or gateway waited too long for the upstream server.

Which specification defines 408?

It is defined in RFC 9110 ยง15.5.9.

Is a 408 response cacheable?

Not by default. A 408 response is only stored by caches when it carries explicit freshness information such as Cache-Control: max-age or Expires.

More PAYATE tools