What Does HTTP Status 408 Mean? (Request Timeout)
What HTTP 408 (Request Timeout) Means In Plain English
A 408 status (Request Timeout) means the server timed out waiting for the client request to complete.
If you want the broader context across all status code families, use the full HTTP Status Codes Guide (2xx, 3xx, 4xx, 5xx).
Quick Navigation
- What HTTP 408 (Request Timeout) Means In Plain English
- How to Read HTTP 408 in WebsiteDown Results
- Most Common Root Causes
- What to Do Next
- What to Avoid During Triage
- Real-World Examples
- HTTP 408 FAQ
How to Read HTTP 408 in WebsiteDown Results
In website checks, 408 appears less often than gateway timeouts. When it appears, investigate client-network behavior, load balancer timeout settings, and request size/pacing.
If you see this code only in one region, compare with official provider status and retest from another network. Mixed regional results often indicate routing, policy, or edge differences rather than full global outages.
For deeper triage, compare this with the HTTP 504 guide, HTTP 502 guide, and the intermittent outage investigation guide.
Most Common Root Causes
- Slow client uploads or interrupted network paths.
- Aggressive server timeout configuration under load.
- Proxy/load balancer closing idle connections early.
- Large payloads sent over unstable networks.
What to Do Next
- Check timeout thresholds across edge, load balancer, and app tiers.
- Measure request body sizes and upload durations.
- Correlate 408 spikes with network jitter and packet loss reports.
- Differentiate 408 (client->server timeout) from 504 (upstream timeout).
What to Avoid During Triage
- Do not mix 408 and 504 in one bucket during triage.
- Do not increase all timeouts blindly without load impact review.
Real-World Examples
- Example: large form upload on unstable mobile network triggers 408.
- Example: load balancer idle timeout too short for upstream handshake.