Version 1.1.7

[Improvement] Enhanced the payload for webhook notifications (Documentation: https://kb.status.io/notifications/webhook/)

[Bug] Fixed bug causing the URL to exclude the maintenance_id in notification messages during maintenance create

 

Version 1.1.6

[Improvement] Improved SSL certificate validation process for dedicated certificates

[Bug] Fixed bug causing the URL to exclude the incident_id in notification messages

[Bug] Fixed SMS truncate issue for incident notifications

 

Status.io and GDPR

We’re just a few months away from mandatory compliance with GDPR. The European General Data Protection Regulation (GDPR) replaces the EU National Data Protection legislation and is due to take effect in May 2018. The GDPR is a new regulation to protect personal data of EU citizens. It affects all organizations (even outside of the EU) that process data of EU citizens.

In our previous article “Preparing for the GDPR”, we shared some resources for learning more about the GDPR. In this article, we’ll share what we’re doing to comply with the GDPR.

 

 

Is Status.io GDPR compliant?

Yes. Status.io is GDPR compliant.

We are a “processor” and we are required to have a data processing agreement (DPA) in place for each client. If you don’t already have a DPA, it’s easy to create one with us by contacting support.

 

 

GDPR-Specific Data Compliance

Personal data is stored in various locations including: United States, Canada, Ireland, Australia.

Personal data we collect: email address, SMS address, IP address.

Personal data is processed through Amazon Web Services (AWS) and Twilio for email and SMS message delivery. DPA’s are in place with each processor.

To comply with the Conditions for Consent (GDPR Article 7), subscribers must opt-in to sign up to receive status notifications.

A subscriber can self-remove themselves and delete all data associated with their subscription. This is a requirement for the Right to Rectification and Erasure (GDPR Article 16).

In accordance with the Right to Restriction of Processing (GDPR Article 18), any person can request to never be processed through our system.

 

 

Additional Data Protection and Privacy Documents

 

Privacy Policy

Terms of Service

Security Information

 

At Status.io, we always treat personal data with care and respect. And we’re always looking for ways to improve our security and protections for data.

 

Preparing for the GDPR

 

 

At Status.io, we always treat personal data with care and respect. We’re embracing the spirit of the GDPR and have been looking at how we can improve the security and protections of personal data.

Below we’re sharing some resources to help you better understand the GDPR and how it can affect your organization.

 

 

What is the GDPR?

The European General Data Protection Regulation (GDPR) replaces the EU National Data Protection legislation and is due to take effect in May 2018. The GDPR is a new regulation to protect personal data of EU citizens. It affects all organizations (even outside of the EU) that process data of EU citizens.

There is plenty of information available from the EU Commissioner’s Office to understand the GDPR. We recommend starting with the the Guide to the GDPR and “Preparing for the GDPR – 12 steps to take now”.

View the GDPR Key changes. This includes an overview of the main changes under GDPR and how they differ from the previous directive.

 

 

The following checklists help to assess compliance with the GDPR:

GDPR checklist for data controllers

GDPR checklist for data processors

 

 

Compliance Tools at Status.io

If you use Status.io for subscriber notifications, you may want to explore our Enhance Compliance functionality. Use the compliance tools to add disclaimers to your subscription signup form and additionally log the details of each subscriber’s opt-in. Learn more about our compliance features.

 

 

Disclaimer: This information is not legal advice.

Version 1.1.4

[Feature] Added new partner integration: OpsGenie

[Feature] Added new partner integration: Pingometer

[Improvement] Optimized the location selector for containers

[Improvement] Added Developer API methods to retrieve a single incident or maintenance

[Improvement] Added Developer API methods to retrieve a list of IDs for incidents or maintenances

[Improvement] Updated the Developer API documentation for /component/status/update to specifically handle a single component+container combination, instead of handling multiple components/containers per call

[Bug] Fixed an issue that allowed notification subscribers to signup more than once

[Bug] Updated coordinates for AWS location eu-central-1

 

 

 

Version 1.1.3

[Feature] Added new metrics integration for Librato

[Improvement] Inbound email alerts have been enhanced to handle multiple cases (DOWN, Down, down)

 

Enhancements for Incidents and Maintenances

Each day, dozens (sometimes hundreds) of incidents and maintenances are created on the Status.io platform. We’ve analyzed and studied thousands of these events to help us learn how to improve the tools based on our users’ needs.

Today we’re announcing a couple of updates that enhance and streamline the incident and maintenance processes. Let’s dive in!

 

Modifying affected infrastructure

You can now add or remove affected infrastructure in existing incidents and maintenances.

This is great for situations where a component was accidentally included or excluded from an incident or maintenance. It’s only a couple of clicks to update the affected infrastructure. Learn more in our knowledge base.

 

 

Updating incidents with different status levels

You can set different status levels for each component and container during an incident.

In the below example, the Atlanta API has been fixed while the Montreal API is still experiencing an outage.

Learn more about working with incidents in our knowledge base.

 

 

API updates

Our Developer API has been updated to reflect these improvements. Check out the latest API documentation at developers.status.io.

Don’t worry, existing integrations using our API will continue to work as they have before. You may choose to upgrade anytime when you’re ready to take advantage of the enhanced functionality.

 

SaveSave

Version 1.1.2

[Improvement] Added functionality to modify the affected infrastructure for existing incidents and maintenances (View more details in the blog post)

[Improvement] Improved the infrastructure affected linking for incidents in the dashboard and API (Review the updated API documentation at developers.status.io)

[Improvement] Updated server providers for container locations

[Bug] Fixed a bug that affected sorting when adding new components, containers and metrics

 

 

Version 1.1.1

[Improvement] Added ability to disable automation mode for an active maintenance

[Improvement] Notifications can now be configured to send automatically during an automated maintenance

[Improvement] Added functionality to remove components or containers from a maintenance

[Improvement] Improved the infrastructure affected linking for maintenances in the dashboard and API (Review the updated API documentation at developers.status.io)

[Bug] Fixed a date time display bug for incidents in the dashboard