Skip to content

HTTP status codesUpdated 2 Nov 2026

408 Error Code: When a Request Times Out

Quick answer A 408 means the server waited for your request to finish arriving and then closed the connection. A slow network is the usual cause, so retry on a better one.

HTTP status408
Impact
Low impact
Typical fix time
Minutes
Who fixes it
You

The 408 error code means Request Timeout. The server was ready, your browser started to send a request, and then the rest of it did not arrive in time, so the server closed the connection. Unlike a 504, where a server is slow to answer, here the server is waiting for you.

That is why the fix is often on your side: a weak signal, a busy Wi-Fi, a big upload on a slow line or a browser that stalled. The server may also add a Connection: close line to its reply, which tells your browser to open a fresh connection next time. Reloading on a steadier network clears most cases within minutes.

Common causes

  • 1Slow or unstable internet connection

    How to tellPages load slowly everywhere and videos buffer

    What fixes itStand near the router or find better mobile coverage

  • 2Large upload on a slow line

    How to tellError appears while sending a photo, video or big form

    What fixes itUpload on faster Wi-Fi or send a smaller file

  • 3Network switching during the request

    How to tellHappens when walking between Wi-Fi and mobile data

    What fixes itStay on one network until the page finishes

  • 4Browser or app stalled

    How to tellThe page hangs, other tabs are slow, the device feels hot or busy

    What fixes itClose extra tabs and apps, then reload

  • 5Server timeout set too short

    How to tellMany users see 408 on the same action

    What fixes itOwner raises the request timeout for that action

  • 6Firewall or proxy delaying the traffic

    How to tellOnly appears on office, school or hotspot networks

    What fixes itTest on mobile data; network admin reviews the filter

How to fix it, step by step

  1. Reload the page once

    Most 408 errors are one-off. Use the reload button or F5 just once and let it load. A new attempt opens a new connection, which often goes through.

  2. Test your speed with another page

    Open a few different sites. If they are all slow, the problem is your connection and not this one website. In that case see internet not working.

  3. Try a different connection

    Compare your home Wi-Fi with your phone's data plan, pick the steadier one at your spot and stay on it until the page completes.

  4. Restart the router

    Switch the router off for thirty seconds and on again. If you share the line with many devices, pause big downloads or video calls while you retry.

  5. Close extra tabs and apps

    A browser with many open tabs or a phone with little free memory can stall mid request. Close what you do not need, then try again.

  6. Make the upload smaller

    If the error appears when sending a file, reduce its size, or send fewer files at a time. Smaller requests finish before the server loses patience.

  7. Try again at a quieter time

    If the site is being slow for everyone, a later try may be smoother. If the 408 keeps showing for one action on one site, report it to the owner.

Understanding the 408 error code

Every connection to a server has a patience limit. The server expects a full request within a set number of seconds after it opens the connection. If your side is too slow or silent, it stops waiting and sends a 408, then closes the connection. The official text allows the browser to repeat the same request later on a new connection.

You are on a train, sending photos for a form. The progress bar stops, and the page says 408 Request Timeout. The upload could not complete in the time allowed because the signal dropped. Try once more at a station with stronger signal.

408 compared with 504, 499 and 524

Timeout codes: who waited and who was slow
CodeWho was slowWho waited
408The client sending the requestThe server
499The server replyingThe client, who left
504The server behind a gatewayThe gateway
524The origin server on a CDN siteThe CDN

Have a look at 504 Gateway Timeout, 499 Client Closed Request and the general timeout error guide. All codes are listed on HTTP status codes.

What site owners can do about a 408

  • Check the timeout setting for reading a request. Too short a limit punishes mobile visitors.
  • Look at which actions fail, such as uploads, and consider chunked uploads for large files.
  • Check for proxy or firewall delays that hold requests before the server sees them.
  • Avoid very long keepalive periods that tie up connections with idle visitors.

Do not make timeouts unlimited. Slow clients that never finish can use up the server's connections and block other visitors.

Frequently asked questions

What is the 408 error code?

Request Timeout is what the number 408 stands for in HTTP. The server did not receive your full request in time and closed the connection.

What is a request timeout error code, and who fixes it?

It is the 408. Most of the time you fix it by using a faster or steadier connection. A site owner steps in only if many users see it on the same action.

Does error code 408 mean the website is down?

No. The server is up and waiting. The delay came while your request travelled to it.

How is the HTTP 408 error code different from 504?

In a 408 the server waited for you. In a 504 a gateway waited for another server. The slow party is different.

Will clearing the cache fix a 408?

It rarely matters. A better connection, a smaller upload and a fresh reload are far more likely to help.