Support for TLS (Transport Layer Security) versions 1.0 and 1.1 was sunset on 1st June 2025.
As part of Ably's ongoing commitment to ensure the highest standards of security and performance, support for older TLS versions across the service has been deprecated. All connections to Ably must use TLS 1.2 or higher.
Impact
Since 1st June 2025, requests using TLS 1.0 or 1.1 are refused. This affects all connections to Ably's services, including:
- Realtime and WebSocket connections
- REST API calls
- Any other service that communicates with Ably
Error messages
When attempting to connect using TLS 1.0 or 1.1, you may receive a TLS protocol version error. The error message will reference protocol_version to indicate that the TLS version is not supported.
Recommended actions
- Verify compatibility: Ensure that your systems, applications, and integrations are configured to support TLS 1.2 or higher.
- Update legacy systems: If you are using older platforms, consult with your IT team or integration partners to update any components that still rely on TLS 1.0 or 1.1.
For customers who have a custom environment or active traffic management enabled, Ably can update your settings at any time.
Request failures
From 1st June 2025, attempts to connect to Ably using TLS 1.0 or 1.1 may start to fail. Failures will be phased, with only a fraction of traffic being rejected at first, until 100% of requests are rejected after several weeks.
Requests that are rejected will contain an error message and code referencing this deprecation notice and the associated deprecation policy.
Contact support if you have any questions.