408 Request Timeout — Causes & Fix
HTTP 408 (Request Timeout) means the server timed out waiting for the client to finish sending the request.
- Applies to
- Any website or web server (HTTP standard)
- Time to fix
- 5–30 minutes
What it means
Causes include a slow or dropped connection, a stalled upload, or a client that opened a connection but sent data too slowly. HTTP status 408 is defined in RFC 9110 (HTTP Semantics). This is a client-side (4xx) error — the request itself had a problem, so the fix is usually on the requester's side or in how the server validates the request.
Symptoms
- "408 Request Timeout"
- Slow connection or a hung upload
How to fix it
- 1
Retry on a stable connection
1. As a user: check your internet connection and retry.
- 2
Tune timeouts (developers)
1. Review client/server request timeouts. 2. For large uploads, ensure the connection stays active.
Frequently asked questions
Is 408 my fault or the server's?
Usually a slow/interrupted connection on the client side, but very aggressive server timeouts can also trigger it. Retry on a stable connection first.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.