Twilio Changelog | Nov. 11, 2026
Upcoming cipher suite list update for all Twilio REST API endpoints on February 18, 2027
Security standards are always evolving, and we want to ensure your Twilio applications are using the strongest protection available.
We're extending the deadline for these changes and customers now have until February 18, 2027, to update their setups with the ciphers listed below. We’ll continue accepting legacy cipher traffic during that window so customer applications keep running without interruption.
This extra time will help make the switch as smooth as possible.
If customers are using legacy network software or older operating systems, they may need to update their systems to support the following new ciphers:
TLSv1.3_2025 ciphers
TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384
RSA ciphers (TLSv1.2_2025)
ECDHE-RSA-AES128-GCM-SHA256
ECDHE-RSA-AES256-GCM-SHA384
How to prepare for the new ciphers
Test your system: Customers can check today whether their setup already supports the newer ciphers. From the application, send a request to https://tls-test.twilio.com using the same server, runtime and network path (including any proxy or firewall) that the application uses to call Twilio. If a 200 OK response is returned, no changes are needed. If the connection fails, customers need to upgrade their setups using the steps below.
- Upgrade (if the test failed)
- Direct API users: Verify the OS and TLS library support TLS 1.2 with the ciphers above. Check with the OS and TLS library providers for details.
- Helper Library users: Cipher negotiation is handled by the underlying runtime and OS, not the Helper Library. Customers should check with their runtime and OS providers for TLS 1.2 support. We also recommend upgrading to the latest Twilio Helper Library.
- Verify the connection: After upgrading, run the same test again from the application. Once customers see that 200 OK response, they're all set.
Need a hand?
Check out these resources for more information: