1

This question already has an answer here:

I've been facing this error since a lot of months now though it has been occurring annoyingly very often during last few days.

408 Request Time-out
Your browser didn't send a complete request in time.

I'm using Google Chrome on a Windows Server 2008 machine and have a fairly stable internet connection. Never seen this error on any other website.

What actually causes this error and is something wrong on my end?

marked as duplicate by Arjan, Martijn Pieters discussion May 25 '14 at 16:14

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

migrated from superuser.com May 25 '14 at 13:56

This question came from our site for computer enthusiasts and power users.

  • 1
    I'm getting the same error on github.com, but only with Internet Explorer 11 from time to time. Never had it on SO - not with any browser. Also I don't know your case, but in my case the whole thing appears within milliseconds, so it's not like a long timeout. – Mario May 25 '14 at 9:09
  • Mario stackoverflow replies average ~300ms if I ping, and displays that quickly when it does. Actually it shows timeout error also within milliseconds. – Abdullah Leghari May 25 '14 at 9:15
  • 1
    Related - 408 Request Timeout, is it just me? – Sathyajith Bhat May 25 '14 at 13:57
  • I've run into this issue on Github and SO when there's a proxy server between me and the sites. – Steven V May 25 '14 at 15:20

Browse other questions tagged .