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 hello@status.io

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 hello@status.io

Status maps are now powered by jVectorMap

With a little CSS and static image, we rolled our own mapping solution. It was half-baked and only meant to be a temporary solution.

The legacy maps are now long gone and we replaced them with the maginificant jVectorMap! Browser compatibility was a primary concern and these maps support everything all the way back to IE 6.0.

The shiny new maps:

Location information appears on hover. We will be adding more meaningful data here in the future.

The legacy CSS maps:


How to automate your status page with Pingdom

Already use Pingdom for network monitoring? You’re in luck! Simply link your Pingdom alerts to your Status.io components for automatic status updates.

How it works

Pingdom sends an email alert when one of your monitoring checks fails. Our backend parses this message and then toggles the component’s status based on the detected values.

  • ‘DOWN’ sets a component to ‘Full outage’
  • ‘UP’ sets a component to ‘Operational’

Configure your components for Pingdom automation

  1. Login to the Status.io control panel and navigate to integrations. Copy the email hook address from the component you’re linking right now.



2. Next login to your Pingdom account and add a new contact using the email address you copied in the previous step.



3. Edit the individual monitoring check at Pingdom and enable alerts to be sent to the new contact you just created.

Repeat these steps for each component that you want linked to a Pingdom check.

That’s it! Now your status page will stay updated automatically based on Pingdom events.