Skip to main content

How to Debug a Monitor Showing as Down in UptimeRobot

Learn how to debug a monitor that shows down status in UptimeRobot to identify and fix false alerts or real downtime issues.

Updated over 2 weeks ago

If your monitor is showing as down, here are some steps to help you debug the issue:

1. Whitelist Our IPs:

Ensure that all our IPs are whitelisted both on your end and by your provider. You can find the list of IP addresses here: UptimeRobot Locations.

2. Check Incident Logs:

Each incident includes a log that provides specific details such as error codes and timestamps. Reviewing these logs can help identify the exact reason for the downtime.

3. Check Your Server’s Accessibility:

Verify that your server is accessible from multiple locations. You can use online tools like Down For Everyone Or Just Me to see if the issue is widespread. Consider scenarios where server responses differ for direct access versus automated monitoring, which can explain why monitors report downtime despite accessibility.

4. Review Server Logs:

Check your server logs for any errors or issues that might be blocking our monitors. This can provide insights into why the monitor is detecting downtime. Pay special attention to any HTTP 500 error codes, as these indicate server-side issues that monitoring nodes interpret as downtime.

5. Investigate Firewall and Security Settings:

Ensure that your firewall or security settings are not blocking our monitoring requests. Adjust them if necessary to allow uninterrupted access. Additionally, ensure ICMP traffic is allowed, especially if you are using Ping monitors, as server firewalls, cloud provider restrictions, or network equipment might block ICMP echo requests.

6. Test Your URL:

Manually test the URL or the service that the monitor is checking. Ensure that it is running correctly and returning the expected response.

7. Monitor Configuration:

Double-check the configuration of your monitor. Ensure that the URL, port, and other settings are correct and match what you are monitoring. For HTTP/HTTPS monitors, verify the request method in the monitor settings. Switching to 'GET' under Advanced Settings might resolve erroneous downtime reports.

8. Network Issues:

Check for any network issues that might be affecting connectivity between your server and our monitoring locations.

9. Pause and Restart the Monitor:

Try pausing the monitor and then starting it again. This can sometimes resolve temporary issues.

10. Contact Support:

If you have followed all these steps and your monitor is still down, please contact our support team for further assistance.

By following these steps and utilizing the incident logs, you can effectively debug and resolve issues with a down monitor.

Did this answer your question?