In addition to the IPs being currently used, we’ll be starting to use (effective by 2015-10-12) a set of new IPs parallel to the new machines to be joined to the system. Here they are:

  • IP Block:
  • Or, the IPs that will be used:
    • –
    • -
    • -
    • -
    • -
    • -
    • -
    • -
    • – for future use
    • - for future use
    • - for future use
    • - for future use
    • - for future use

If your monitors are behind a firewall and had needed to whitelist Uptime Robot’s current IPs, please make sure that you whitelist these IPs as well for the monitoring to function as expected.


For any user willing to customize the notifications or integrate them into their own apps (or 3rd party apps), web-hook alert contacts is one of the best options.

Yet, it was only supporting GET requests and POST support was frequently requested. And, here it comes.

It is now possible to receive the web-hook requests as POST and it supports both:

  • standard POST (application/x-www-form-urlencoded)
  • or JSON (application/json)

For both options, the parameters to be posted need to be defined in JSON and the custom variables provided (like *monitorURL*, *monitorFriendlyName*, etc.) can all be used as POST values.


We have added few new features to the API which may look tiny, yet, can be handy for anyone integrating with the API. Here they are


This (search) is a new parameter for the getMonitors method for filtering the responses with a given keyword (that will be searched in the monitorURL and monitorFriendlyName).

Getting Account Details

If you need a short summary of the account details, the getAccountDetails can return the number of up, down or paused monitors, the monitor limit and the min. interval that can be used on the account.

Threshold and recurrence

It is possible in Pro Plans to get notified “if down for x minutes, alert once (or every y minutes)”. These parameters allow setting these values via the API.

They can be used with the addMonitor or editMonitor methods and, also, getMonitors will return the threshold + recurrence values of each monitor’s alert contact.

Older Response Time Data

As the Pro Plans are keeping the response time values back to 12 months, here is a way to reach them via the API (besides the web interface).

The responseTimesStartDate and responseTimesEndDate parameters in the getMonitors method are the way to go for that.

That is all for now :).

We are planning to add “public status pages” as a built-in feature to Uptime Robot. Yet, there are services which are specialized in this area, offering advanced features and already work with Uptime Robot.

We’re happy to announce the completion of our integration with one of them: StatusCast. This will allow Uptime Robot customers to create their own end user-facing application status pages which update automatically from application performance monitors in Uptime Robot’s system.


This will help with managing customer expectations without increasing your team’s workload, as our integration with StatusCast makes it easier to communicate fulfillment of your SLA and put the rare service disruption into the larger context of consistently excellent performance.

StatusCast’s hosted status pages update in real-time and allow for rules-based or manual edits to ensure the wording and the timing of your updates are appropriate for your end user audience.

The goal is to extend the value Uptime Robot provides by taking the information your team is already receiving and applying it to solve another common demand placed upon IT/DevOps teams.

Why do end users care?

It’s frustrating when your software application is inaccessible or experiences performance issues.

While you know that happens rarely rather than never, and that the real metrics should be the speed and thoroughness with which an issue is resolved rather than the fact that the rare issue occurred at all, customers may not know this until it is visible.

Why should you care?

Whether the customer is right or not in their presumption about the disruption in your application, their negative feelings are going to hurt your reputation and your customer retention.

Your challenge then is to fix the problem as quickly as possible, while communicating to end users and internal staff (e.g. Customer Support, Executive team, etc.) about the scope of the issue, how much progress you’re making, and when full functionality can be restored. This level of transparency, attention, and professionalism helps to mitigate your customers’ frustration.

Uptime Robot already helps you with the first part of that challenge, by enabling you to quickly identify the nature of the disruption. Our new integration with StatusCast lightens the communications portion of that burden as well, by translating the application monitoring data you’re already getting from Uptime Robot into information that makes sense to your end users and non-technical colleagues. This leaves your team free to focus on what they do best: fixing the problem!

How does it work?

Application performance information is pushed from Uptime Robot to your hosted status page. StatusCast allows you to set up rules-based automation and privacy settings so that the right information gets to the right people (as not all application performance data is relevant to or appropriate for all users).

End users are also able to subscribe to updates via email, social media (Twitter, etc.), SMS text message, etc., as that is often more convenient for them than checking a status page.

We want your feedback!

You can give the StatusCast integration a try (they have both free and paid plans) and let us know what you think. Again, our goal is to extend the value that can be received from Uptime Robot! Please let us know if you have any thoughts or suggestions.

Uptime Robot offers many ways to get notifications: e-mail, SMS, push messages, web-hooks, 3rd party integrations and more..

And, it delivers a “down message” once a monitor is down and an “up message” once it is back up.

The advanced notification options

For the Pro Plan, it is now possible to:

  • get a “down notification” only if the monitor is down for x minutes
  • and, optionally, keep getting the “down notifications” every y minutes

Simply, we can now tell “if down for x minutes alert once” or “if down for x minutes, alert every y minutes“.

And, this is a per monitor per alert setting which is great to have different settings for each monitor or alert contact.

What it is good for?

Using this feature, you can:

  • ignore small downtimes
  • escalate notifications (if down, send notifications to Alex, if down for 30 minutes, send notification to Brian, etc.)
  • make sure you don’t miss a down notification by getting them every x minutes

How to use it?

Advanced Notifications

In the “add/edit monitor dialogs”, you’ll see a “show advanced options” option. Once clicked, it’ll display a “settings icon besides each alert contact” and clicking them will be showing the options.

And, the interface will remember whether “the advanced options are shown or hidden for any future add/edit monitor actions” to ease the usage.

Additionally, the feature can be applied to all monitors in bulk using the “Bulk Actions” (that can be found just under the “Add Monitor” button).

Need the Pro Plan?

Besides this advanced notification options, the Pro Plan supports 1-minute monitoring for faster downtime detection and 1 year of stats (and, it is still offered with the introductory pricing).

The past stats and events related to a monitor is pretty important to analyze its performance within time.

Uptime Robot keeps events back to:

  • 2 months for Free Plan
  • 1 year for Pro Plan

and response times back to:

  • 24 hours for Free Plan
  • 1 year for Pro Plan

However, there can be times where a monitor may need a new start (it may have changed the hosting company, owner or had lots of issues that you do not prefer to track) and want to open a new page for it.

It is now possible to reset all the history of a monitor using the “Reset Stats” link that can be reached through the actions of a monitor (in the left sidebar>clicking settings icon besides a monitor).

Additionally, the feature is also available through the API with the resetMonitor method.

Uptime Robot, a project that have started out of curiosity 5+ years ago, has now grown so much.

Since the last year, we are a full-time team working on it, providing fast support and trying very hard to keep the service simple, solid and modern.

In order to guarantee its future and keep offering a great monitoring experience, it became clear that Pro Plan is the way to go.

The Free Plan is still here

The Free Plan of “50 monitors checked every 5 minutes” (which you are currently using) is still here and stays untouched.

The Pro Plan

The Pro Plan is a very budget-friendly premium monitoring plan which comes with 3 additional features:

- 1-minute checking intervals for faster downtime detection
- (Optional) more monitors
- 1 year of log retention
You can check the pricing and purchase by logging-in + clicking the “Upgrade” link that can be found in the header or inside the “My Settings” page.

Additionally, you’ll see that there is now a “Pro SMS” feature which supports almost any mobile provider and can be used by purchasing SMS credits from the “My Settings” page (one-time credits come with each Pro Plan to experience it).

20% discount for early adopters

The Pro Plan pricing is currently 20% discounted for early adopters. By purchasing now, you’ll be locking the discount rate for future renewals and upgrades.

The future

We are working on introducing exciting new features (for both plans) and making the monitoring experience more solid than ever.

Please let us know any questions or suggestions you may have and we’ll be very happy to help.

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.