Yearly Archives: 2010

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 be necessary if you have excluded the IPs in your statistics application.

The new IP will be active by 03 December 2010.

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 the server (like 200, 404, etc.). So, the server that the website hosted on can be up, other websites on it can be working but it may only be your website.

Ping looks for if the IP of your website is reachable or not. It is a better fit to monitor uptimes of servers/networks.

Should I use both http(s) and Ping for a website?

There is no need for that. If the aim is to monitor a website uptime, then http(s) monitoring should be enough as it'll notify you when the server can not be pinged as well.

However, if you have a dedicated server or a VPS, using Ping for the server IP besides the websites on that server is a good idea.

 

This is also an important step for Uptime Robot as how monitor types are handled both on the frontend and backend are now changed to let us adding new monitor types easier :).

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 (as you already know the certificate is self-signed and no need to throw alerts).

On the other hand, for any type of https URLs, if the certificate is an invalid one (like the common name and URL not matching) or the date is expired, Uptime Robot will keep sending a down alert.

Lately, we have added “custom timezones” to Uptime Robot where users can select their timezone to view any report in their own date and time.

You may be willing to add something similar to your own application as well and it takes some time to find the values for timezones or cities and countries they cover.

As we already have it, want to share the data (something simple but can save time):

Download the timezones database in .SQL format.

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 various web applications before but wanted/needed to experience how an application that runs -too- many tasks and has many users:

  • can scale better
  • serve stable
  • offer a good support system
  • and more..

to improve ourselves.

And, yes, we're learning too much from it, thanks to suggestions, comments which also help us a lot.

Will It Stay Free?

Well, that's the main plan. Simply, we want to support it with sponsors.

When the service was launched in January 2010, we had mentioned that it would stay for free at least until June 2010. And, lately, we updated this to December 2010 (in our about page).

Since the launch, we've contacted too many "possible advertisers" and, to be honest, it didn't go very well yet : ). However, we're still in contact with many others which means "it can always happen".

Uptime Robot currently runs on 2 cool servers and a remote account (for multi-location monitoring which we'll increase the number very soon) + it is improved regularly. Yes, it has a cost but we're not complaining. We learn a lot and that's something.

To sum up, we want to keep it free and will see how it goes.

P.S. Many users asked to donate, thanks so and so much. "You-paying" is the last option.

Any suggestions, thoughts? Please share, they mean a lot.

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 in the “My Monitors” page like below:

The report displays the events (up/down/paused) within a timeline and it is interactive. You can hover any event to find out the details about it.

In order to view the dates and times in your own timezone, we have added a “timezone” field inside the “My Settings” page which you can select your own and the report (+ all feature reports) will be displayed with that timezone.

P.S. The report tooltips are a little buggy in IE (working on a fix) but they work nice in all other browsers.

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 send DMs)
  • Go to "My Settings" page
  • Under "Add Alert Contacts", click Twitter
  • Enter your Twitter user (without @)
  • Activate this alert contact by pressing the "play button" inside the table listing your alert contacts

That's it. You'll now be receiving up and down alerts via Twitter.

Excited to share a nice move that will make Uptime Robot much more stable and eliminate any false-positives.

We’ll be starting to monitor websites from multiple locations (from US, Europe, Asia, etc.) to make 100% sure that they are “down” before sending any notifications.

It is all set now and we’ll be doing test monitoring starting today and the system will be activated fully by next week.

The remote checks will be done from URLs like r1.uptimerobot.com, r2.uptimerobot.com, etc. So, if you whitelist our IPs in your firewalls, analytics applications, etc, please whitelist *.uptimerobot.com to make sure it will cover all remote locations.

New IP:

Tip: If you need to whitelist IPs for a reason, you’ll find the rest useful. Else, why don’t you start monitoring more websites?

Today, we have also added a new server which is much powerful and won’t require any upgrades for a long time (hopefully short).

The old IP (174.36.18.26) will still be used until the end of April 2010 and the new IP is 67.228.76.131 (it is already used).

Well, this is actually more a bug fix than a new feature but this sounds much better :).

Because of how Uptime Robot was handling/filtering URLs, monitors with querystrings couldn’t be added. And, it is fixed now.

So, it is possible to monitor a URL like http://ww.mydomain.com/index.php?item=1&price=15.

Also, in some cases, multiple notifications were being sent for the same alert, which is also fixed now. Simply, one notification per one alert contact.

Hopefully, more features to come this week. Keep an eye on!

This is the first post of the Uptime Robot Blog and hi to everyone :).

Since the launch of the project (20 Jan 2010), we worked hard to make the system better and there has been several updates to it:

New Features:

  • Keyword checking (ability to check if a keyword exists or not in a webpage)
  • RSS alerts (get the alerts via RSS)

Improvements:

This is the biggest part that we have worked on.

We weren't expecting such an interest on Uptime Robot as the system had few hundred users just in the first day.

Continue reading