Cause: Couldn't connect to server

A “Could not connect to server” alert usually indicates that the monitoring system is unable to establish a connection to the site. In most cases, this happens when a site has been moved to a new server or provider and DNS changes are still propagating.

• Site was recently moved to a new host

• DNS records were updated and are still propagating

• Nameserver changes are in progress

• Monitoring system is still resolving the previous DNS record

• Monitoring alert showing “Could not connect to server”

• Site loads in some locations but not others

• DNS resolves to different IPs depending on location

• Intermittent access to the site

• Check that the domain’s A-record points to the correct IP in the platform.

• Confirm the correct nameservers are set

• Allow time for DNS propagation (up to 24–48 hours depending on TTL)

• Load the site from different networks or devices

• Use DNS lookup tools to confirm consistent resolution

• If DNS changes were recently made, no action is required

• Monitoring alerts should clear once propagation finishes

Contact support if:

• DNS propagation has completed but the alert persists

• The site does not load from any location

• You need help verifying DNS records or nameserver settings

Provide the domain name and details of the recent move or DNS changes to help speed up troubleshooting.