Troubleshoot isolated monitor failures

The monitor that failed may have a different network path to your site than other synthetic monitoring locations or from locations you are testing. If there is a problem at the location, or on the network between the location and your site, a single location may fail to return a result. This indicates that some users on similar network paths may have experienced issues.

If you see Connect timed out or Read timed out, this typically indicates that the site was unavailable or so slow to respond such that the monitor could not retrieve any data. This usually indicates an issue along the network path.

There may be requests that timed out or requests that are missing. You may see timeout messages such as

TimeoutError: URL {YOUR_DOMAIN} was unable to finish all network requests before reaching the maximum time limit

or

TimeoutError: Page load timed-out (unable to finish all network requests on time)

These requests could not complete before the page load timeout or the end of the script.

To solve the problem, try drilling into the resource to see when and where it responds poorly. Some resources may intermittently return slowly.

If the page frequently is unable to fully load within 60 seconds and you are using a simple browser monitor, try a scripted browser monitor and set a configurable page load timeout.