Uptime Robot has been a very stable service for a long time. Yet, for the last few weeks, we know that some users have received false-positives.

Why did that happen?

In short, the servers we used couldn’t handle the load :).

In detail, we always look for ways to heavily optimize the system and the engine to minimize the need for new CPU, RAM or diskspace. The optimizations vary from perfecting the queries used or compressing not-frequently-used-data to choosing the right platforms for the right job. But, we experienced that, how much you optimize, every system has a limit and you shall grow that system before getting close to that limit.

What are the actions taken?

We have added more servers and strengthened the current ones.

And, besides the servers added, from now on, we’ll be adding new ones before the load gets heavier so that the system will always stay healthy.

Additionally, various new controls are added to the engine to minimize false-positives and Uptime Robot will “very” soon start verifying downtimes from multiple locations at once (rather than the current setup which is 1 remote location).

What are the new IPs (if you need to whitelist them)?

There is now an additional engine and 4 more remote nodes to verify downtimes. The up-to-date list of IPs can be found at Locations & IPs page.

To sum up, just wanted to inform you that our hands are on it.

Customizing monitors one-by-one is not a problem when there are few of them but things get complicated when there are many.

The older Uptime Robot interface had the ability to start/pause/delete monitors in bulk and the new look was missing this feature.

We have just added this feature with more options. Now, it is possible to apply these actions to all monitors at once:

  • pause all monitors
  • start all monitors
  • delete all monitors
  • change intervals of all monitors
  • change alert contacts of all monitors

The feature can be reached from the “Bulk Actions” link just under the “Add Monitor” button at the left side menu.

Bulk Actions

Hope it helps using the interface much faster.

Uptime Robot keeps the event logs (back to 2 months) for the monitors and this information can be viewed through the web interface.

However, users may prefer to download them to work on this data (comparing with HTTP logs, sharing with colleagues, etc.).

Simply, it is now possible to export logs in CSV format through the “export icon” besides the “overall logs table” and “monitor-based logs tables”.

This is just a tiny-yet-useful feature addition and many more to come.

PushbulletToday, we are very happy to announce the integration of Pushbullet as a new “alert contact type”.

Pushbullet is an impressive and free service/app that enables users to receive notifications (and also share files) in:

With this integration, it is now possible to get the alerts on all these platforms in real-time. And totally free.

How to use Pushbullet with Uptime Robot?

  1. Create a free account at Pushbullet
  2. Install Pushbullet to device and/or browser you prefer
  3. Copy the Pushbullet API Key from Pushbullet website’s “Account Settings” page
  4. Login to Uptime Robot and go to “My Settings” page
  5. Click “Add Alert Contact” and choose Pushbullet
  6. Enter a “Friendly Name” and the “Pushbullet API Key” and create the alert contact.
  7. Attach this new alert contact to the monitors you prefer from the “edit monitor” dialog of each monitor.

That easy.

Uptime Robot is already integrated with the free and easy-to-use Boxcar app for sending iOS push messages.

Lately, the app has a new version, Boxcar 2, and the old version will be inactive in the next weeks.

Uptime Robot now supports Boxcar 2 and “any alert contacts for the older version will be deactivated on 11 April 2014 (7 days later)“.

In order to keep getting iOS push messages, please make sure that you:

  • install the Boxcar 2 app (note that the user-pass in the old Boxcar app is no longer valid, a new account shall be created in Boxcar 2)
  • define its “Access Token” as an alert contact
  • attach this alert contact to the monitors preferred.

Friendly Names For Alert Contacts

With this update, we have added the ability to define friendly names for alert contacts so that it’ll become much easier to distinguish them from each other.

That’s all for now :).

For the last month, we were working hard to improve the monitoring engine and pretty excited with how stable it became.

Also, few visible updates exist and here they are:


Many users were asking for a specific login page so that their “password managers” would automate the login process. Right now, the login has its own page.

And, the login page + dashboard are now served SSL-only.

New Server

A new server is added to the system for a much more stable monitoring experience.

For users that need to whitelist IPs, its IP ( was already listed here, so, you probably don’t need to.

Addition to the API

For newMonitor and editMonitor methods, there is now an optional monitorInterval parameter for setting the checking interval. That simple.

What’s Next?

A few cool features are on the way, stay tuned :)

There is a new “alert contact type” in town: “Web Hooks“.

In its simplest form, “Uptime Robot sends a request to a URL that you mention” with all parameters of the monitor.

After that, you can handle this request and use the information in it for many possible things like sending custom notifications to your clients, restarting servers, integrating Uptime Robot with 3rd party products/services, etc.

Web Hook

It can be used in 2 ways:

  • standard: a standard querystring is added to the end of the Web Hook alert contact
  • custom: a totally custom querystring structure can be created with the variables provided

As an example:

If a web-hook alert contact is http://www.domain.com/?, Uptime Robot will send a notification like http://www.domain.com/?monitorID=95987545252&monitorURL=http://test.com&monitorFriendlyName=Test Website&alertType=*0&alertDetails=Connection Timeout&monitorAlertContacts=457;2;[email protected].

Or, a custom Web Hook can be created like http://www.domain.com/?id=*monitorID*&type=*alertType* by simply using the variables wrapped inside ** characters.

These variables can be found in the “Create New Alert Contact” dialog in “My Settings page”.

Hope that it can simplify any possible integrations.

It is already possible to monitor websites that require “HTTP basic auth” with Uptime Robot by providing login details.

However, it was not possible to monitor authentication-required websites without providing the auth credentials as Uptime Robot was considering any HTTP 401 response as “down”.

A logic update is applied today that will count HTTP 401 as:

  • “up” if no authentication info is provided
  • “down” if authentication info in provided

Simply, you can now monitor auth-required websites without providing these details.

With the new version of Uptime Robot’s front-end, response time data was also added as a new feature.

However, it was not available in the API until today as we were experimenting ways to keep this huge data. Things look pretty stable now and response times can now be reached via API.

As expected, the feature is a parameter for the getMonitors method. There are actually 2 parameters:

  • responseTimes: if set to 1 (responseTimes=1), the response time for all the checks in the last 24 hours is returned
  • responseTimesAverage (optional): the API can also return the values as averages for given minutes (for ex: the dashboard averages the values as 30 minutes). This parameter will be very handy once the data for longer periods will be available and we’ll be able to get averages for hours/days/weeks, etc.

Hope that this new addition will enable you to provide more useful data in your site and/or apps.

Uptime Robot’s website and dashboard have changed completely few months ago.

It is not announced until now as we didn’t think it was complete before it works on all devices. And, it is now optimized for all resolutions.

With the new dashboard, we wanted the things to be still simplistic but ease presenting other useful information.

Uptime Robot Dashboard

Uptime averages presented for different periods is a result of this. And so the response time data which is pretty important to analyze” if a monitor is healthy/fast even if it is not down”.

With the response time monitoring, the data being kept and processed has grown hugely. We have experimented various ways of keeping them for finding the most optimized solution (may be a technical post on that later), found it :) and ready to present more valuable information with them.

Another addition is “custom monitoring intervals” which helps us to define the intervals each monitor is checked.

Dedicated team

Uptime Robot had started as a side project 4 years ago. Since then, it always asked for more hours from us to get better and, for the last 12 months, we were working almost full-time on it.

And, since the start of 2014, we are officially working full-time on it.. no distractions.  So, expect things to evolve much faster as we have lots of exciting ideas to make Uptime Robot more functional.

That is it for now and please feel free to share your thoughts and suggestions that will make the service better.


Ohh, and one more thing:

Social love

Uptime Robot now has a Facebook page and, if you use the service and think that it is functional, we’d love to get your help on spreading the word about it so that any site owner uses it and minimizes downtime.

Here it is:

And, you can always follow us on Twitter too:

Have a great day everyone.