Version 0.4.1

[Improvement] Tour only shows during first Dashboard session

[Improvement] Removed about text from status page history view

[Improvement] Refactored top bar status level

[Improvement] Removed Uservoice to use Olark exclusively for support

[Improvement] Status pages now refresh automatically every 5 minutes

[Bug] Fixed tiemzone bug for status page history view

[Bug] Fixed minor RSS bug for status feeds

[Bug] Fixed auto-tweet bug

[Bug] Fixed URL in password recovery emails for contacting support

Version 0.4.0 – Refactoring our core

Today’s update brings a slew of enhancements that we have been developing. To continue growing towards our vision, we decided to refactor some of’s core functionality. You will notice that components can now be associated with multiple-containers and status updates are now separated by incidents and planned maintenance. These changes were a large hurdle that we had to overcome before continuing to add new features.

All existing status pages have been automatically upgraded to take advantage of these new enhancements.

Multitenancy improvements


Support for multitenancy architecture has been baked into since day one using what we call containers. Containers are used to represent a single geographic location and/or data center. There were limitations originally since each component could only be linked to a single container. To get around this, we created duplicate components. As of today you can consolidate for components and remove those duplicates.

Modify your existing components and select all of the appropriate containers.


Planned maintenance

Schedule maintenance activities in advance. Your users will be able to see all upcoming events. When you’re ready, start your maintenance and it will be displayed prominently on your status page.


Incident handling

Create a new incident to post the initial status update during an outage or other system failure. Further updates will be linked to the original incident. You can even create multiple incidents at the same time and your users will be able to see which updates belong to each incident.


More enhancements

  • Metrics thresholds – Control the min and max values for each metric graph on your status page.
  • Theme-able status bar – Change the default color of the status bar using our theme designer.
  • Fine tuned Pingdom automation – Pingdom alerts now trigger specific containers within each component.
  • And a few more surprises…

We launched our prototype at the end of July 2013 and have spent the past 6 months hacking on our product to deliver a solid platform for hosting your status page. Tons of great features are right around the corner, we deploy almost every day!

Create your status page now.

Happy New Year


We would like to wish you, your families and your systems a happy and healthy 2014 with 100% uptime.

2013 was great, but we are looking forward to really stepping it up in 2014.

Nothing is more important to us than building the finest status pages. For the past 8 weeks we have been refactoring and optimizing our platform and are gearing up to push version 0.4.0 to production.

Here are some of the major enhancements that you can expect to see in the next couple weeks:

  • Refactored incident handling to include the tracking of multiple status updates within a single issue
  • Ability to schedule planned maintenance events
  • Components support multiple containers
  • And much more…

What else?

A long awaited feature, status notifications. Soon your beloved users will be able to sign up to receive your status updates directly in their inbox. This has been our #1 most requested feature and we are psyched to deploy it! The enhanced notification system is scheduled for release towards the end of January.

We want you to love your status page. Looking for a unique feature? Wish a setting worked differently? Reply and tell us what we can do better to improve your status page.

Feature Requests and Preview v0.4.0

Our development timeline through version 0.4.2 is solid. We’re fullfilling our #1 feature request (can you guess what is is?) and refactoring the core of how component and containers work together.
We have supported multi-tenancy systems since the beginning, but components had a 1-to-1 relationship with containers. Soon you will have the ability to place a single component into multiple containers. This is a critical step that we must accomplish before continuing to increase functionality.


Beyond 0.4.2, we could use your help to decide on the priority of our development efforts. Send us your feedback. What features do you need? Which metrics providers do you want to see integrated? Have any ideas for the status page ux design? We’re super friendly. Your feedback would be sincerely appreciated. Drop us a line at

Version 0.3.0

When we launched in August there were browser compatibility issues, a limited feature set and no friendly wizard to help get your status page set up. But that has all changed! As of today, our platform has never been more stable. Instead of debugging errors, we are enhancing the existing features and adding new ones.

Check out some of our newest features in version 0.3.0:

Visibility Modes

Create private status pages for internal use.


Public Status API

Robots care about your status too! Every status page comes with a unique API call that provides your current system status.


Multi-user Teams

Enable your entire team to post status updates and manage your status page.


What’s next

Development is rapidly moving along and we are excited to share our upcoming releases in the near future. In the mean time if you have feedback, we would love to hear it. Drop us a line at