How can I increase request timeouts in my checks?

By default, most monitoring checks have a 40-second timeout. If the endpoint takes longer to respond, the check will return a timeout error.

You may see an error like CRITICAL - Socket timeout after 40 seconds on HTTPS or other types of checks. This error means that our probe servers were unable to establish a connection to your website or endpoint within the set timeout limit. It does not necessarily indicate a complete outage but suggests that the response took too long.

Timeout errors can occur in HTTPS and other types of checks for a variety of reasons, including temporary network congestion, high server load, or web application firewall (WAF) and other security issues preventing the connection.

If you believe the default timeout is causing issues, you can adjust this setting under the Advanced tab when creating or editing a check:

If you receive timeout errors unexpectedly, we recommend checking network logs for traffic spikes or unusual patterns and ensuring that Uptime’s Probe Servers are whitelisted by the website or resource.