New Alert log feature, Bulk Update improvements, UI changes and API limit changes.

We’ve got a few things to bring you up to speed with today, and you can find all the information below!

New Alert log feature

Our new Alert Log feature gives you a high level of visibility on alerts that have been sent out by our system, you can see the timing, and status of any alert we send no matter the alerting  method.


This new feature is available for all plans, so you can take advantage of the data whether you are on our free or Enterprise package! You’ll be given the reasons for any alert failures, some examples including running out of SMS credits and incorrect contact details. As well as a full log of all alerts sent out, with this tool you can also see logs of reports generated by features like Virus Scan.

You can access this new feature by going to the Contact Groups section of your account, and from here you can see the alert logs for each Contact Group on your account.

Bulk Update improvements

We’ve implemented a summary of which tests will be updated upon filtering for all Bulk Updates. This means that each time you run an update in bulk you’ll be able to see which tests were affected to the right side of the page.


UI Improvements

First off we’ve made some improvements to the screen which displays all of your tests, primarily the changes are contained within the “Box View” layout, we’ve changed the buttons on the test boxes to be smaller and more accessible, and we’ve ensured that all of the options for each test can be easily accessed without needing to drill down into the test’s details.

We’ve also somewhat standardized the entry system for the email addresses in the Contact Groups to closely match the phone number entry section.

This means now that it will not be possible to miss alerts due to formatting errors, all previous phone numbers have of course been ported over to the new system already!

API Limit Changes

Following user requests we’ve increased the burst limit for our API to 20 per second, up from 10. To accommodate this change and also to prevent abuse in future we have elected to have a daily limit of 100,000 API calls per account – this is a level at which we can see that very few users will be affected, and we feel that it’s a fair limit in terms of using our API on any paid plan. There are no changes to this on the free level plan, and the same limit of 250 calls per day will apply.


New API Key Management function, and team access to data through the API and App

In this post we’ll take you through the available options for managing sub-accounts, from managing permissions in app, to our new functionality which allows you to assign individual API keys to your users. First lets take a look at our new API Key Management feature with support for multiple API Keys.

API Key Management


It’s now possible to add multiple API keys to an account, this means that for teams the same key will no longer need to be shared, and each member of staff/department can be assigned their own access token.

As well as being an improvement security wise, you can monitor the usage for each key in the API Key’s section of the user menu, to do this – and to add new keys for your team simply click here.

Sub-User Management

On our Business level plan it’s possible to add Sub-Users who have access to the in-app data, this allows them to view the information in a much more visual fashion when compared to the API. Sub-Users will be able to view the full settings and details of the tests on the “Main Account” depending on the permissions that they are assigned.

You can assign a few different parameters to your Sub-Users, first off you should decide whether they will have “view-only” or “full-edit” rights which will affect how they can interact with the test data from the main account.

Another handy option that can be set is tag based access, this means that you can assign a Sub-User to one or more test tags, and when they log in it’s only the tests under these tags that they will be able to see and interact with.

Building up our API

Some Exciting Changes to our API

Over the past few weeks we’ve been making incremental updates to our API to bring it up to date with our in-app features, a few of these updates have already been released, so now is a great time to recap and go through the new capabilities that are offered:

Page Speed

You can now fully manage your Page Speed tests through our API. You can create new tests, update existing ones as well as deleting them, and there are calls for listing current tests and grabbing the historical data too!

The same limits for data retention apply here as when managing these through app, so everything will match up to what you see there. The full documentation for the new Page Speed functions can be found here. 


SSL tests are another much requested addition to our API, and after our recent update to SSL monitoring it made sense to prioritise this one!

For SSL tests you can create, delete, list and update – with full control over the expiry alerts, as well as the settings for SSL validity. You can now also configure how many days before expiry you get the related alerts – which can be very handy for self signed, and other shorter term certificates.

In order to get going with this and take a look at our documentation on the new SSL API methods just click here.

Maintenance Windows

We have new functionality for our Maintenance Windows too, this has been something we wanted to add for a while as it’s a feature that really benefits from the added automation that our API can provide.

With the new API functions for Maintenance Windows you’ll be able to set up a new window, delete an existing window, list all current windows and update a pre-set window.

To check out the new functions for the windows and see how they can benefit your operations just click here.

There’s still more to come…

There are many further changes and additions to come, so keep an eye on our API documentation and update channels for the latest news as it comes in!

Feature Update: Enhanced SSL Monitoring

Today we’ve released a huge update, completely changing how our SSL monitoring works and enabling you to keep a much closer eye on all aspects of your certificates. We’ve introduced a new set of features for SSL, that enable much more powerful monitoring, these are summarized below:

Expiration Monitoring – We’ve fully revamped our expiration monitoring increasing the options in terms of how often the details are checked (anywhere from 5 minutes to 7 days dependent on plan level), also allowing customization of when the alerts for expiry come through – meaning that self-signed certs are now much less troublesome to keep an eye on.


Certificate Validity – As well as expiry we now watch out for validity issues, we will run a complete check of the certificate chain, verify that the certificate is on the correct domain, and we’ll also ensure that the certificate has not been revoked by the relevant authority. You can get alerted by our system right away if any of these factors are not as they should be.

Certificate Score – We now take a range of factors into account to provide you with a certificate score. Firstly we look at the “Cipher Strength”. Cipher strength has a proprietary scoring algorithm that takes the following variables into consideration:


* Key Exchange

* Bulk Cipher & Strength

* Used Keyed-hash message authentication (HMAC)

From the Cipher Strength and other factors, we give your certificate a final score, the full weightings for this score are shown below:

* Cipher Strength (50%)

* Perfect Forward Secrecy (25%)

* Certificate Errors (10%)

* Certificate Validity (5%)

* Certificate Presence (5%)

* Extended Validation presence (5%)

We will mark your certificate with a score out of 100%, you can see all scores within the SSL section in the left menu. All of the info can also be viewed on the details page, where we provide further data and comparison graphs.


The new functionality is available across all paid plans, and all functions are now managed within the SSL section, meaning that there’s increased separation from the uptime tests and the ability to manage these separately.

New Root Cause Details available

We’ve today made it a lot easier for you to identify of timeout related downtimes with the addition of two new functionalities to our “Root Downtime Causes” section.

Now you can see both a Traceroute and a DNS check details in the event of a timeout on any test within your account, if you are looking for the Enhanced root downtime causes then these can be found below the “Status Periods” section, in the portion of the page marked “Root Downtime Causes”

In order to view the new info in the event of a timeout on one of your tests, simply click the “Details” button next to a Root Cause entry. You’ll then see a full summary of the DNS test and Traceroute. These new stats are only available on our paid plans, so you’ll need a subscription to take advantage of the heightened detail!