Consistently receiving connection timed out for a website which has been configured for monitoring

[venky1544]

Hi,

I'm getting a lot of connection timed out for a website which has been configured for monitoring. the connection timed out has a blank response code. I'm a bit confused does the connection timed out needs to be alerted is it more of a network issue or is it an internal client-side error because server issue will give you response code > 500 . as there is no response code in this event.
How should it be interpreted?
My client is trying to understand what exactly is the response code for connection timed out if we highlight this could it be a false positive alert

Any insights/suggestions would be a great help.

[LukeMurphey]

A connection time out means that an HTTP connection could not be established. This is why there is no response code (you need a successful connection to get a response code).

[venky1544]

Hi Luke

yes i understand that http connection was not established but should this be considered as a network latency issue or some kind of client connectivity issue because I'm trying to understand should i raise a a alert for these kind of connection time out or not

[LukeMurphey]

I doubt it is a client issue. I get reports of possible bugs in Website Monitoring due to timeouts occasionally but they have always turned out to be legitimate network issues (firewall blocking the connection, Internet connection that is struggling, etc.).