Blog.

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 […]

We get many questions regarding "if Uptime Robot will ever become paid or not" and thought it'll be the best to share it in detail. Why Is Uptime Robot Free? We have launched Uptime Robot in January 2010 hoping to offer a non-complicated uptime service (where every website owner actually needs). Also, we had created […]

Since the launch of Uptime Robot, we’re analyzing the cost of keeping logs in means of performance and size. With lots of tweaks to our engine and code, Uptime Robot now saves every action to present them as reports and charts. The first report activated is the “Last 24 Hours Status” which can be found […]

Few weeks ago, Twitter approved our request for getting whitelisted to use their API, so we wouldn’t be limited with the standard daily API usage limits. And, we just activated the Twitter integration for getting the up/down alerts via Twitter DMs (direct messages). The usage is very simple: Follow @uptimerobot Twitter user (so, it can […]