Configure slow-response monitoring

Slow-response monitoring alerts you when a website remains reachable but takes longer than expected to respond. It is off by default and does not replace availability monitoring.

Configure a new monitor

1. Open New Monitor.
2. In Helpful alerts, turn on Slow response alerts.
3. Under Alert when slower than, choose 1, 2, 3, 5, or 10 seconds.
4. Under Confirm after, choose 2, 3, 4, or 5 consecutive slow checks.
5. Complete the rest of the monitor settings and select Create Monitor.

The default configuration is 3 seconds for 3 consecutive checks.

Configure an existing monitor

1. Open Monitors and select the monitor.
2. Open Slow Response Alerts in Monitor Tools.
3. Enable or disable the feature.
4. Choose the threshold and consecutive-check count.
5. Select Save changes.

Disabling the feature stops new slow-response detection. It does not delete earlier performance incidents.

Choose a threshold

Start with a threshold that is meaningfully slower than the website's normal response time. The available thresholds are 1, 2, 3, 5, and 10 seconds.

Also compare the threshold with the monitor's availability timeout. The timeout should be higher than the slow threshold when possible. If a request reaches the timeout first, the result is an availability failure rather than a successful slow response.

Choose a confirmation count

The confirmation count controls how many slow checks must occur consecutively before a performance incident opens:

• 2 checks detects sustained slowness sooner but is more sensitive to brief spikes.
• 3 checks is the balanced default.
• 4 or 5 checks waits longer and can reduce notifications for variable websites.

The real confirmation time depends on the monitor interval. Three slow checks take about 3 minutes on a 1-minute monitor and about 15 minutes on a 5-minute monitor.

What happens after confirmation

After the configured number of consecutive successful-but-slow checks:

• Uptime Basics opens a performance incident.
• The monitor can remain Up because availability and performance are separate.
• Eligible email and SMS destinations can receive a Slow Response notification.

After the configured number of later checks no longer meet the slow condition, the performance incident resolves and eligible destinations can receive a recovery notification.

Alert delivery requirements

Slow-response notifications use the monitor's Alert Channels settings. Email or SMS must be enabled at both the account and monitor levels, and the monitor must select a verified destination.

Changing the slow-response threshold does not change the monitor timeout, check interval, accepted HTTP codes, or availability confirmation policy.

Verify the setting

After saving:

1. Confirm the Slow Response Alerts summary shows the selected threshold and count.
2. Review the Response Time chart over a representative period.
3. Use Detailed Logs to compare individual response times with the threshold.
4. Review incident and alert history after sustained slowness occurs.

Related articles

• Slow website versus unavailable website
• Configure alerts for one monitor
• What creates an incident?
• Use Detailed Check Logs