Skip to content
Pricing RU Sign In
RU
← All Status Codes
408
Client Error

408 Request Timeout

408 Request Timeout — server grew tired of waiting for the complete request and closed the connection. Slow or unstable client network.

Description

The 408 Request Timeout status code indicates that the server did not receive a complete request message within the time it was prepared to wait. The client may repeat the request without modifications.

Common Causes

Slow client connection (mobile, poor Wi-Fi) Large upload payload with nginx client_body_timeout exceeded Firewall / proxy-server timeout

How to Fix

Increase nginx client_body_timeout (default 60s → 120s) for endpoints with uploads. For large files, use chunked upload (S3 multipart, tus.io). Advise clients to retry the request.

Check your website's HTTP status code

Check now →

Related Status Codes

400
400 Bad Request
The server cannot process the request due to malformed syntax.
 401
401 Unauthorized
Authentication is required and has failed or not been provided.
 402
402 Payment Required
402 Payment Required — code reserved for future use, but currently used by some APIs to signal "payment needed".
 403
403 Forbidden
The server understood the request but refuses to authorize it.
 404
404 Not Found
404 Not Found — the requested URL does not exist on the server. The most common client-error; signals search engines to remove the page from index.
 405
405 Method Not Allowed
The HTTP method used is not allowed for this resource.

Related guides

Longer-form reading on this topic from the knowledge base.

Automate this check

Set up continuous monitoring and get an alert when something breaks. No manual runs to remember.

Start free

Start monitoring for free

Sign up and get access to API, monitoring and notifications

Create Account API Documentation