Category Archives: Announcements

https-smallPublic Status Pages, a feature to easily share the statuses of the monitors with others, was introduced few months ago.

The standard status page URLs (like https://stats.uptimerobot.com/xyz) were HTTPs-enabled since day one.

However, the ones behind a custom domain (like http://status.mywebsite.com) were not as it was a little more tricky to get a SSL certificate for all the custom domains.

Good news, custom domains are now HTTPs enabled too (thanks to the free + automated CA: Let’s Encrypt).

And, all status pages are actually HTTPs-only from now on.

Important note for CloudFlare users:

As the status pages are now HTTPs-only, the “flexible SSL feature of CloudFlare” will end up in an infinite redirect. There are 2 options to make it work:

  • disabling the “cloud feature” for the CNAME
  • or, using Full or Strict SSL feature

Uptime Robot’s API is consumed pretty much (with over 5,000,000+ requests/day) for “automating monitor management”, pulling the data to generate custom reports and more.

As the usage grows every day, the APIv2 is built for a faster, more secure and stable experience with added features.

SSL and POST only

The APIv2 expects all parameters to be sent as a POST request and works SSL-only where both changes together help making it more secure.

Updated parameter names and speed

The parameter names and responses are very consistent now. They are all lower-case, separated with “_” (like api_key).

And, most methods are now ~ 2x to 5x faster.

Added features

It is now possible to pull more data with getMonitors method, including:

  • getting the uptime % of a range (or multiple ranges) with custom_uptime_ranges parameter
  • getting the all time duration of statuses with  all_time_uptime_durations parameter
  • getting the logs of a given period with logs_start_date and logs_end_date parameters
  • getting maintenance windows of a monitor

And, maintenance windows can also now be managed with the API too.

Code samples

The updated documentation page now has code samples for each monitor in multiple scripting and programming languages including PHP, Python, Nodejs, Go, Ruby, C# and Java.

When will APIv1 be retired?

APIv2 is the version that will be improved from now on and APIv1 is planned to be retired by 1 June 2017. So, please make sure that you switch to the new API before then.

Suggestions and bug reports

We are already using APIv2 in production, so, it is pretty stable. Yet, there is always a change of bugs and please let us know if you experience one.

Also, look forward to any suggestions and feature requests to make it better.

Great news! Uptime Robot now has an official mobile app.

The app allows performing the most critical actions (add/edit/delete monitors, view stats) and it supports push notifications.

Uptime Robot App

The app will be improved regularly and missing features/actions will be added in the next weeks (like “creating alert contacts”).

How does push notifications work?

Once logged in to the app, it simply:

  • asks for a “friendly name” for the mobile device
  • and creates a “mobile alert contact” with that name.

And, the rest works just the same as other alert contacts so that you can get alerted via push notifications only for the monitors you prefer.

Get the app

The app can be downloaded from:

Hope that you like it and it helps for a better uptime.

You’ll remember that SSL 3.0 is no longer secure since October 2014 with the discovery of Poodle attack. And, it is also disabled by default on all popular browsers.

On the other hand, there are still a small number of websites that support SSL 3.0 (which must definitely be disabled).

Starting tomorrow (6 April 2016), we’ll also be dropping support on sending SSL 3.0 compatible requests which will make the monitoring “not function” for those websites (a website’s SSL 3.0 support can be checked from SSL Labs).

Once Uptime Robot detects that a website requires SSL 3.0 for HTTPs communication, it’ll not mark the monitor as down but pause it and notify the user via e-mail with the information for taking action.

 P.S> Disable SSLv3 is a nice website that shares “web server specific information” regarding “how to disable SSL 3.0″

We all want our websites/servers to be “up” all the time and take multiple actions to increase uptime.

Yet, not all sites/servers are built for 100% uptime. Some have various tasks that cause downtime like:

  • backups
  • batch jobs
  • restarts
  • upgrades
  • etc.

Uptime Robot now has a new feature (for the Pro Plan) to handle such one-time or regular downtimes nicely:

Maintenance Windows

The feature is for easily defining once or recurring “do-not-monitor periods”.

As an example, we can now set a Maintenance Window that will start “Every Tuesday at 22:35 and run for 20 minutes”. Uptime Robot will stop the monitoring as 22:35 and resume it 20 minutes later so that you don’t get any “expected notifications”.

Maintennace Windows

It has support for:

  • once
  • daily
  • weekly
  • monthly

schedules. And, the way it works is very familiar (just like Alert Contacts).

They can simply be defined from the “My Settings” page and attached to the monitors of choice from the Add/Edit Monitor dialogs.

Simple and functional :).

 

If you are a business or freelancer with lots of monitors where getting the up/down notifications is not enough and want to keep an eye on the snapshot of the statuses of all monitors regularly, here is a new feature:

TV Mode

It is simply a focused view of the dashboard where only:

  • the number of the up-down monitors
  • and a list of “Latest Events”

are the most important.

The TV Mode refreshes each minute so that it always displays the up-to-date information.

It is a perfect fit to be displayed on a separate display where the teammates can also view it easily.

TV Mode

The feature can be reached from the “TV Mode link” at the right-top side of the dashboard (and, if pressed on a “monitor detail page”, it’ll keep the focus on that monitor).

P.S> Soon, we’ll be adding an option to reach the TV Mode with a unique link that doesn’t require user-pass (where login is sometimes an issue on display-only devices).

P.S2> The TV Mode is actually available since few weeks, yet, we hadn’t introduced it and hope that this blog post helps in case you had not seen it in the dashboard.

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: 69.162.124.224/28
  • Or, the IPs that will be used:
    • 69.162.124.226 – engine5.uptimerobot.com
    • 69.162.124.227 - engine6.uptimerobot.com
    • 69.162.124.228 - engine7.uptimerobot.com
    • 69.162.124.229 - engine8.uptimerobot.com
    • 69.162.124.230 - engine9.uptimerobot.com
    • 69.162.124.231 - engine10.uptimerobot.com
    • 69.162.124.232 - engine11.uptimerobot.com
    • 69.162.124.233 - engine12.uptimerobot.com
    • 69.162.124.234 – for future use
    • 69.162.124.235 - for future use
    • 69.162.124.236 - for future use
    • 69.162.124.237 - for future use
    • 69.162.124.238 - 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

Search

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.

StatusCast

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.