[Feature] Released public API v1
[Feature] Added external service health monitoring
[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!
[Feature] Added .com cname for optional bypassing of the .io TLD
[Feature] Components are now sortable via drag and drop
[Improvement] Live chat support is now accessible from anywhere inside the Dashboard
[Improvement] Redesigned the status.io website
[Bug] Fixed notification message subjects
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.
To get started, sign up for a normal account. Then send us an email and let us know which open source project the status page is for.