Connection timed out

What it usually means

The connection was attempted, but nothing came back before the timeout. Often an overloaded server, or a firewall silently dropping traffic instead of refusing it.

What to check first

• Server load: a saturated CPU, a full worker pool or a slow database makes a healthy server look absent.
• A firewall that silently drops packets instead of refusing them (dropping produces a timeout, refusing produces "connection refused").
• The response-time limit on the monitor, if the site is merely slow rather than dead.

How ErrorDetector reports it

This is a reachability failure. The check is repeated immediately to rule out a blip; once confirmed, an incident opens with this cause on it, every channel on the monitor is alerted, and the outage counts against uptime until the next successful check closes the incident.

Caught by: httpkeywordapipingport monitors. Read about the incident management feature.