Client error · 408

408 Request Timeout

A 408 Request Timeout means the server was waiting for the rest of the request from the client and closed the connection when that wait expired. The server is up. The request never finished arriving.

HTTP status codes explained · the longer reference on the blog.

What 408 means

The code is a client-side timeout from the server’s point of view. The client opened a connection, then stalled while sending the request line, headers, or body. Proxies also emit 408 when they sit between a slow client and an origin and their own idle timer fires.

You will not see 408 for a slow response. That case is a gateway timeout on the proxy (504 or Cloudflare 524) or a client that gives up first. The homepage checker waits 10 seconds and, if nothing comes back, reports a timeout message with no HTTP status. A monitor does the same with its own timeout, which you can set from 5 to 60 seconds and which defaults to 30. Neither check invents a 408. They only record 408 when the server actually sends it.

Common causes

  • A slow or stalled upload

    Mobile clients and large multipart forms hit the server’s body timer. The route is fine for small requests and returns 408 for slow ones.

  • An idle keep-alive connection was reused too late

    The browser reused a connection the server had already decided to close. The next request can fail once with 408, then succeed on retry. A single blip of this kind is not an outage.

  • A proxy timer is shorter than the client needs

    nginx client_header_timeout or client_body_timeout, or a load balancer’s idle timeout, answers 408 while the app is still waiting for the body.

  • The client aborted and a middlebox filled in 408

    Some proxies synthesize 408 when the caller disconnects. Your app log shows a closed socket, and the visitor sees a timeout page from the proxy.

How to fix it

  • Separate “slow to send” from “slow to answer”

    If the server is slow after it has the full request, look at 504 and application latency. Change client body timers only when logs show the body never finished arriving.

  • Read the proxy timeout that fired

    The error log names the timer. Raise it to match real uploads, and keep a sensible cap so idle sockets cannot pile up.

  • Retry a simple GET

    A homepage GET has no body. If GET returns 200 and only uploads return 408, the site is up and the upload path is what needs the longer timer.

  • Watch for a pattern, not a single refresh

    One 408 on a reused connection is normal HTTP. Repeated 408s on ordinary page views mean a timer or a network device is cutting requests off.

Is it your site, or just you?

Load a small public page, then repeat the action that failed. A 408 only on a large upload, and only on one network, is the path between that client and the server. A 408 on a tiny GET from several networks is a timer on your edge.

The homepage checker requests the URL from outside your browser. If it returns HTTP 408, the server is closing ordinary GETs. If it returns 200 or a timeout-without-a-status, your browser’s request is the one being cut off.

How to monitor for 408

A monitor that receives HTTP 408 fails when it expects 200, which is the right alert if public GETs are being closed. If the checker reports “timeout” with no status, the monitor never got a 408 — the wait expired on our side first. Lengthen the monitor timeout (up to 60 seconds) only after you know the origin is slow rather than down.

The checker on the ismysiteup homepage requests the URL from our servers and shows the HTTP status, response time, and SSL details. No account is required, and that checker allows 5 checks per hour from the same network. A free account watches 5 URLs, each checked every 10 minutes, and sends alerts on WhatsApp, Telegram, Slack, or email. A monitor expects HTTP 200 unless you set a different expected status (100–599). One failed check is confirmed with a second check before the first alert, and a later success sends a recovery alert. Pro (every 5 minutes) and Business (every minute) are listed on the pricing page; paid checkout is not open yet.

Compare Free, Pro, and Business

Related status codes

FAQ

How is 408 different from 504?

408 means the server got tired of waiting for the client to send the request. 504 means a gateway got tired of waiting for the origin to send the response.

Does the free checker report 408 when my site is slow?

It reports HTTP 408 only if your server sends that status. If your server stays silent for 10 seconds, the checker reports a timeout and no HTTP status.

Is one 408 worth paging someone?

Usually no. Idle keep-alive connections produce occasional 408s. ismysiteup waits for a second failed check before the first alert, which filters a single blip.