[Improvement] Optimized the email notification workers to improve delivery speeds
[Improvement] Updated New Relic metric integration
[Improvement] Tuned TLS connection configuration
[Improvement] Fixed Status API response data format
[Bug] Fixed uptime calculation for Pingdom metrics
[Bug] Fixed DKIM validation display bug
Today we’re announcing our newest integration with Amazon Simple Email Service (Amazon SES).
All status notifications will now be delivered via SES instead of Mandrill. Due to a major change in terms at Mandrill, we decided to use this opportunity to switch to a more reliable provider.
Amazon SES is a rock solid email service built on the reliable and scalable infrastructure that Amazon developed to serve its own customer base.
Action Required:
Existing users will need to re-verify their custom email domain settings. Verification is quick and simple. Learn more in our knowledge base article.
While verification is pending, status notifications will be sent from [email protected].
[Feature] Ability to view email delivery report for status notifications
[Feature] Option to have the Last Updated time automatically updated
[Improvement] Migrated email delivery to Amazon SES
[Improvement] Automatic handling of bounced email messages
[Improvement] Version identifier links to the Changelog
[Improvement] Added New Relic metric type (Throughput RPM)
[Bug] Fixed a bug causing the custom HTML to break for certain status pages
[Improvement] Updated Terms of Service.
[Improvement] Updated Privacy Policy.
[Improvement] Updated the Status.io logo.
[Improvement] Enhanced the validation for SSL certificate requests.
[Improvement] Migrated to SendGrid for transactional email delivery.
[Feature] Search engine privacy
[Improvement] Migrated inbound email alerts to new service provider (SendGrid)
[Bug] Fixed a bug causing some New Relic metrics to not be updated
[Bug] Fixed a bug causing connections to private HipChat servers to fail
Until now each status page hosted on our platform was limited to using a single custom domain name such as status.example.com.
Today we’re excited to launch support for multiple custom domains, allowing companies to set up public status pages using custom domains like these:
This is great for products or services with multiple names, or anyone who wants to increase the redundancy of their status page. No longer will you be limited to serving your public status pages on a single domain. Customers on our Business plan can add up to 3 custom domain names per status page.
And of course we built in support for custom SSL certificates to be used with multi-domains. Simply upload your certificate for each domain name.
Pro tip: In addition to using custom domains, every account comes with a Status.io subdomain that you can set up and use like example.status.io.
[Feature] Added support for multiple custom domains
[Improvement] Enhanced history search functionality
[Bug] Fixed an issue causing some non-admin team members to receive 404 errors in the dashboard
[Feature] History page now supports full text search
[Feature] History page is filterable by component
We released a bunch of libraries to help you build integrations with our status platform using your favorite language. These libraries are officially maintained by us and will be updated as the API evolves.
Go – https://github.com/statusio/statusio-go
Node.js – https://github.com/statusio/statusio-node
PHP – https://github.com/statusio/statusio-php
Python – https://github.com/statusio/statusio-python
Ruby – https://github.com/statusio/statusio-ruby
Our Github account also lists some non-official libraries and plugins: https://github.com/statusio
[Improvement] Status API returns more detailed info
[Improvement] Added maintenance reminder schedule info
[Improvement] Improved the reliability of IRC notifications by implementing SASL
[Improvement] Support private HipChat servers
[Bug] Fixed 404 errors for successful payment method updates