TLS 1.0 and 1.1 deprecation
As part of our commitment to maintain a trusted platform and promote the safety of your data we have begun the process of deprecating TLS 1.0 and 1.1.
The PCI Security Standards Council updated their guidance and will now require full deprecation of TLS 1.0 on June 30th, 2018.
As of this writing Airbrake customer traffic breakdown per protocol
- TLS 1.2 – 80.43%
- TLS 1.1 – 0.22%
- TLS 1.0 – 19.35%
Thus far we have
- deprecated support for SSLv3 in 2014
- transitioned webhook integrations to enforce TLS 1.2 on October 3, 2016
Our timeline for deprecating TLS 1.0 and 1.1:
- August 21, 2017 – customers may begin testing TLS 1.2 notifier compatibility
- June 30, 2018 – in accordance with the revised deadline published by the PCI SSC all support for TLS 1.0 and 1.1 will disabled. All Airbrake domains will transition to support TLS 1.2 only.
How will it affect me?
If you are running a legacy version of an Airbrake notifier your account may stop receiving errors. We recommend upgrading your notifier before June 30th, 2018.
If you wish to test your application’s compatibility, you can do so by attempting to send errors to https://tlsv12.airbrake.io (temporarily, instead of https://airbrake.io or https://api.airbrake.io). If the errors appear on your dashboard, your application is compatible with the upcoming changes. Refer to your notifier’s configuration instructions on how to change the destination domain, and be sure to change it back when you have finished testing.
Upgrading your notifier
Please consult our Install Airbrake page for more information on how to upgrade your notifier or force a TLS 1.2 connection.
Troubleshooting runtime issues
If you have upgraded your notifier and are still experiencing issues negotiating a connection using TLS 1.2 it is possible there are language or system dependencies which do not support TLS 1.2
We will continue to monitor TLS 1.0 and 1.1 vulnerabilities and adapt our timeline as required to mitigate issues if they arise.
If you have any questions please don’t hesitate to reach out at firstname.lastname@example.org.