UptimeRobot Mod

UptimeRobot helps users monitor website and server performance at all times, providing recommendations for website improvements to boost speed and traffic, meeting the needs of diverse users. It also automatically alerts users when website issues arise, helping them promptly fix vulnerabilities and errors, ensuring website security at all times. The software will continue to be updated with more practical tools to further enhance website security. Users who need it can download it from this site.

Features:

Website monitoring: Be the first to know that your website is down! Reliable monitoring warns you before any significant trouble and saves you money.

Response time monitoring: Monitor response times and spot slowdowns immediately with customizable alerts.

DNS monitoring: Get alerted when your DNS records change. Monitor DNS entries and detect unexpected changes before they impact your service.

SSL monitoring: Don't lose visitors because of an expired SSL certificate. Get notified 30, 14 and 7 days before expiration.

Domain expiration monitoring: Keep your online presence secure and avoid any potential damage by monitoring your domain's expiration date.

Cron job monitoring: Also known as heartbeat monitoring. Monitor recurring background jobs or intranet devices connected to the internet.

Port monitoring: Is the email service still UP? How about the critical database server? Let's check! Monitor any specific service running on any port.

Useful Tips:

Customize Monitors: Take advantage of the options to create, modify, pause, and remove monitors based on your specific needs.

Utilize Integrations: Connect with third-party tools like Slack and PagerDuty for improved workflow and collaboration.

Access History: Keep track of up and down events, allowing you to analyze trends and make informed decisions about your services.

Set Alerts: Configure alerts for specific monitoring parameters to ensure you are promptly notified of any issues.

User Reviews:

The view all monitor just show 4 monitors from Home Screen, rest of monitor are not shown. Now hope the shifting of Germany nodes to USA further improve things and app becomes more reliable life it was few years ago. Please add more nodes from india or Asia. App issues remains unresolved.

I've relied on UptimeRobot for years to keep an eye on my network status. It has never let me down and always proves to be user-friendly. The new app design really stands out. Everything feels smoother and cleaner, plus it offers exciting new features. Adding push notifications directly from the app brings a great convenience. The web-based interface lets you explore system monitors in-depth, which is a huge benefit. UptimeRobot remains essential for my network. This updated interface makes it even easier to suggest to others.

A user with the OnePlus 6 on Android 10 noticed some issues. Notifications just won’t cooperate. When trying to enable them, a popup appears. Clicking enable takes the user to app settings where notifications show as on. However, going back to the app reveals that the toggle for monitors is still off. Frustrating situation for sure!

FAQs:

What is a heartbeat monitor?

It works in an opposite way compared to other monitoring types. Heartbeat Monitor is the best solution to monitor endpoints inside an intranet (but connected to the internet). It’s also suitable for regular/cron jobs your website/app may be performing.We will provide a unique URL for each heartbeat monitor to which your device/server/computer will be sending requests. Once it doesn’t arrive, you will receive a downtime alert.

How can I debug a down monitor?

Firstly, please, make sure all our IPs are allow-listed on your end and by your provider. They can be all found here.If there are still any issues, you can try removing the monitor and creating it again. This will change the IP address of your monitor.If there’s a “Connection Timeout”, take a look at the Response Times graph and see if there are some longer responses. The monitor will be marked as down after 45 seconds of not being able to reach your URL.My glitch.me/com, Heroku, or similar monitor is not working Glitch.me, for example, is preventing ping services from reaching their servers and keeping their apps awake.

What are the differences between monitor types?

Here are short details about monitor types:

http(s): it's perfect for website monitoring. The service regularly sends requests (which are the same as if a visitor is browsing your website) to the URL and decides if it is up or down depending on the HTTP statuses returned from the website (200-success, 404-not found, etc.)

ping: this is good for monitoring a server. Ping (ICMP) requests are sent and up/down status is decided according to the "if responses are received or not". Ping is not a good fit for monitoring websites as a website (its IP) can respond to ping requests while it is down (which means that the site is down but the server hosting the site is up)

port: good for monitoring services like SMTP, DNS, POP as all these services run from a specific port and UptimeRobot decides their statuses if they respond to the requests or not

keyword: checks if a keyword exists or not exists in a web page

cron-job (heartbeat): good for servers/computers/devices that are inside an intranet (but connected to the Internet) and need to be monitored. The feature works in the opposite way compared to other monitoring types. UptimeRobot provides a unique URL for each heartbeat monitor created and expects the monitored item to send regular requests to this URL. Once a regular request doesn’t arrive on time, the monitor is marked as down.

How do you detect downtime?

UptimeRobot sends HTTP requests every x minutes from its main engine (US-Dallas)

If no response is received, another request is sent from the same location (in case the previous one was just a hiccup)

If no response is received again, it sends 2 other requests in parallel from 2 random and remote locations (the list of locations can be found here)

If these 2 remote requests fail to get a response too, then the monitor is marked as down and notifications are triggered

Or, if the monitor returns an erroneous HTTP status, it is instantly marked as down without verification (as the status is returned from the monitor itself)

And, once a monitor is down, UptimeRobot keeps sending requests every 1 min (no matter the default monitor interval) for faster uptime recovery, only from the main location

So, in case of a 30 min downtime (except HTTP-status-based downtimes), the monitor needs to:

fail to respond twice from the main engine

fail to respond from 2 remote locations

and must have failed to respond at least 20-25 times in a row from the main location (as the requests are sent only from the main location once the monitor is down)

There are some rare/edge scenarios like:

our requests/IPs may have been temporarily blocked by a firewall

there may have been a problematic hop between UptimeRobot's servers and monitor's server. And, if all the requests UptimeRobot has sent passed from that problematic hop at some point, the requests may have failed and UptimeRobot would think that the site didn't respond. This is the main reason we send "verification requests" from multiple locations to minimize this risk and it is very very low

both of these scenarios have a very low possibility, yet, still wanted to share.. just in case

For the Pro Plan, it is possible to:

get a “DOWN” notification only if the monitor is down for x minutes

and, optionally, keep getting the “DOWN” notifications every y minutes

Simply, you may configure your settings like “if down for x minutes alert once” or “if down for x minutes, alert every y minutes“. 

Conclusion:

UptimeRobot: Monitor anything is the official mobile app for UptimeRobot, the world's leading uptime monitoring service. With this app, you can easily monitor the status of your websites, SSL certificates, ports, server responses, keywords on web pages, and scheduled jobs.The app provides an overall status screen to quickly check if any of your services are down. It also offers a history of up and down events, a monitor list with search and filter features, and detailed information about each monitor, including uptime, response time, and event history.