[Feature] Released public API v1
[Feature] Added external service health monitoring
v1 of the Status.io API is fully baked and ready for consumption.
Developer resources are located at developers.status.io
The API includes the most critical functions for managing your status page.
If you build a plugin, let us know!
And look out for the custom metrics API, coming very soon!
A new alternative TLD is now supported for custom domains: .com
When using a custom domain, such as status.example.com, you must create a CNAME record pointing to domain.status.io.
Now you may choose between the .io or .com TLD.
.io should use domain.status.io
.com should use domain.statusio.com
Why does it matter?
TLD’s are each controlled by different entities, different infrastructure, etc. We all saw the .io TLD experience issues early in 2013. While we can’t prevent a TLD issue, we decided to offer multi-TLD’s so our customers can choose which TLD they wish to utilize.
Status.io is powered by open source software and we have the utmost respect and love for the open source community.
As of today we are offering sponsored accounts at Status.io for selected open source projects.
We published a service for checking the current status of an API: http://whatsup.status.io
And the best part is you can check the health of an API with an API call 🙂
Each services has a unique id which can be used with a simple GET method
The health of 50+ services are being monitored, and we plan to add many more.
4 distributed nodes are monitoring the service availability of each API by inspecting the endpoint’s HTTP response and/or performing synthetic transactions, latter being the goal for all checks.
We’re using this to power the upcoming external components feature for our status pages. Yup, soon you will be able to add 3rd party service health on your status pages 🙂
Give it a try. It’s 100% free.
[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
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 Status.io’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.
Support for multitenancy architecture has been baked into Status.io 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.
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.
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.
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!
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:
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.