Get Updates About New Features And Annoucements

One of our customers, Mathias Meyer from Travis CI, wrote an awesome blog post today on 'Operating Your Site with Hubot'. Mathias has open-sourced his Hubot script, allowing you to automatically update your status page with just one line in your chat client. A few other customers have asked about this integration so we thought we'd go ahead and share parts of the post below. Thanks, Mathias!

(all content below reposted with permission from their blog)

Operating Your Site with Hubot - Travis CI

While we're still a pretty small team, we heavily rely on Campfire for our daily work and for communicating. Adding Hubot to the mix was only natural.

While Hubot is great for the pug bombs alone, we drew some more inspiration from GitHub's daily workflow, in particular for the operational part of Travis CI.

For one, I wanted to have a seamless integration of pushing incident updates to our status page.

Let's have a look at how this works out.

Status Updates

We're using the fine services from for our status page. I heckled them early on to throw an API our way so we can integrate it with Hubot. They were kind enough to ship one very shortly after, and we were off!

The integration allows for a few very simple commands. It allows you to update the status of specific components. For instance, to set the status of our component "Build Processing" to a degraded state, all that's required is the command /status Build Processing degraded.

Whenever a component is in a non-operational state, a status message should go along with it to explain what's going on.

Here's an example from a recent outage where our build processing was having issues because of problems with the infrastructure handling our private cloud setup. We noticed an increasing amount of errors and updated our status page right away.

The incident immediately pops up on our status page and on the Twitter feed for our system status.

During an outage we send updates to the page with the '/status update' command. Same for resolving an issue when the site has recovered from the incident.

Insert from StatusPage: Here's what the incident now looks like on Travis CI's page after the update.

You may wonder why we're going through the trouble of building the scripts and integrating them rather than go through the beautiful web app that's powering

Switching contexts is expensive, even more so during an outage. We're a small team, and the more we can focus on communication and handling the incident, the less context-switching is required.

Moustached Hubot

In the spirit of Travis CI, we open sourced our Hubot integrations for and OpsGenie. It's a continuous effort, and we're working on adding more of our essential services to the mix.

When we first launched StatusPage 5 months ago, we weren't really sure what features to differentiate the plans on and what pricing made sense. Free and $50/month sounded like a good place to start, so we just went with it knowing we'd pick up some good lessons along the way.

A couple themes have emerged in the meantime, and we've used them to make some changes to our packages. The first theme is that many small startups wanted a couple features of the $50/month plan (including page customization and CNAME support), but $50/month was too much. The second is that our Premium customers wanted more functionality, including the ability to display performance metrics on the page. Finally, we had requests for advanced functionality such as managing multiple pages, using custom stylesheets, design consulting, and further privacy options.

Today, we're introducing 3 new packages at $19, $79, and $249 per month to address each of these separate tiers.

For Current Premium Subscribers

You will retain your current plan and current pricing unless you choose to move to one of the new plans. No action is required on your part.

For Current Free Users

To help us focus our attention moving forward, we will be sunsetting all free accounts on August 9th. Free accounts that do not upgrade to at least a Hobby plan ($19/mo) by August 9th will still be available for you to design your page and manage your account, but anybody visiting your individual status page will be redirected to the homepage. The Hobby plan supports email notifications, and comes with all of the branding capabilities of the upper tier plans. It also allows for up to 2 users to manage the page.

For New Accounts

New accounts require a credit card up front, and will be given a free 30 day trial of the plan of their choosing. You can cancel at any time, and can even change your plan during the trial if you want to check out some of the more advanced features.

We know these are some pretty big changes, so as always, we're here to help if you have any questions.

UPDATE (7/7/13 @ 6:35 PM): Current premium subscribers will not be forced to move plans by August 9th, and instead will remain on their current plan and pricing level. The language in the post has been updated above to reflect this.

Since starting YC we've been hard at work building new features for all you awesome StatusPagers. While we're really excited to be launching something big two weeks from now, in the mean time we've released Webhook Notifications and Third Party Components. What are they you say?

Webhook Notifications

Similar to email and sms notifications, webhooks are another way for your customers to be notified about any incident or component updates. An end user can sign up for webhooks through your status page or through your own application using our API. Check out our documentation and screenshots for a walkthrough. When you update an incident or component, your end user will receive the hook with relevant information such as the old and new status of a specific component. The end user will also need to code around the incoming request in order to handle the notification appropriately.

Who should use webhook notifications?

If you're a company with external developers relying on your API, you would be a great fit for webhooks. For instance, we integrate with New Relic, Pingdom, and a few other monitoring providers. If New Relic's status page has webhook notifications enabled and they change the status of any components, we could gracefully degrade Alert Parsing in our own application or show a note to our end users letting them know of the New Relic issue. Before webhooks, we would only be notified outside of our application (email/sms) and then manually login to let users know of an issue.

If you are 'mission critical' to your external developer base, signing up for webhook notifications should be added to your on-boarding process. We're here to help with any API questions.

How do I enable webhooks?

First, navigate to Notifications and make sure notifications are enabled. Second, go ahead and enable webhook subscriptions within Notifications > Settings. Third, take a look at your page and make sure you see webhook notifications as an option within 'Subscribe to Updates'

Third Party Components

Part of what we're trying to do at StatusPage is to make things as easy as possible for you to communicate backend incidents to your end users. Lots of you rely on Amazon, Rackspace, Heroku, GitHub and other services to make your applications work. So, we're beginning to take the pain out of checking the status of these services and updating your page whenever they go up or down. Third Party Components is a new feature that lets you link a public component to your page, and automatically update the public component's status based on its official reported status. We're starting with GitHub and Heroku, and will be adding more as time goes on.

By default, your activated third party component name will be the name of the provider itself (i.e., activating GitHub will be displayed as 'GitHub' on your page). To change the name, click 'Edit' on the component once activated. To override a third party component's status, navigate to your Dashboard and select a status for the component out of the dropdown list. helps companies better communicate with customers and internal teams around downtime.