Blog.

Uptime Robot is generating and keeping 1000s of logs each day in order to display reports and help you reach the past data. There are already millions of records and, as expected, working with huge datasets normally end up in a slower experience. We were working hard to improve the speed of the Uptime Robot […]

If you every want to find out the date-time of a specific downtime or how long it had taken, the only option was to check the date-times of the notifications sent (from e-mails- tweets, text messages or RSS). Here is a new feature which is asked most by Uptime Robot users: “ability to view past […]

Tip: While using Uptime Robot until now, if you didn't need to do anything with the IPs of the service, then feel free to skip this post. Actually 99.9% of the users don't need this info. Around a month ago, we had shared that a new IP was added to our engine to strengthen the […]

In order to make Uptime Robot faster and more stable, a new server is being added to the tiny : ) cluster (3 machines now). If you're using a firewall and had needed to unblock the IPs of the service, than you may want to unblock this new IP as well: 74.86.179.131. Also, it can […]

Today, Uptime Robot adds a new monitor type besides the http(s) and keyword checking: Ping. It is actually the most basic command to find out if a network is up or down. How does it differ from http(s)? Http(s) monitoring sends a request to the web server and, in return, gets a status code from […]

Since the beginning, Uptime Robot was supporting URLs with SSL certificates (https). However, self-signed certificates (the ones with unknown CAs) were not supported as they were generating errors like "unknown certificate", etc. and Uptime Robot was considering these websites to be down. Today, URLs with self-signed certificates are now supported just like any other URL […]