Yearly Archives: 2014

Chat rooms were widely used in the early days of the internet, instant messengers replaced them afterwards and they are getting popular again with a much focused use: team communication.

It is really handy to have all the members of a team talk to each other at the same place and have all that info saved (for searching later on).

HipChat and Slack

HipChat and Slack are 2 of the most popular apps in that area and Uptime Robot now integrates into both.

By simply adding an alert contact (My Settings>Add Alert Contact>Alert Contact Type>HipChat or Slack), it is now possible to get a message to the room/channel of your preference once a monitor gets down or up.

Such a usage not only makes sure that everyone in the team knows how the related project’s uptime is performing but also removes any confusions about the connectivity to the related project’s URL(s).

P.S. HipChat’s self-hosted HipChat Server is supported as well


Many Uptime Robot users were asking for an integration with the “push notifications service” Pushover and here it is.

Pushover is a paid app which has support for notifications through Android, iOS, Chrome, Firefox, Safari & Mac OS X Desktop. It has very nice features like defining “quiet hours, delivery groups” and more.


The addition is very simple just like any other alert contact:

  • go to My Settings page
  • click the “Add Alert Contact>Pushover button”
  • enter the Pushover User Key (that can be found in Pushover’s website or apps once logged in)
  • attach this new alert contact to the monitors of your choice through the “Edit Monitor” dialogs.
  • That’s all.

P.S. Pushover’s supported clients and their download links can be found here.

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, Uptime Robot will send a notification like Website&alertType=*0&alertDetails=Connection Timeout&monitorAlertContacts=457;2;[email protected].

Or, a custom Web Hook can be created like*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.