# Telnyx: Upcoming TLS Certificate renewals for SIP Trunking Signaling - CA and AU regions

> Telnyx maintenance “Upcoming TLS Certificate renewals for SIP Trunking Signaling - CA and AU regions” on 2026-09-04: impact maintenance (vendor’s label), 3 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/telnyx/incidents/01M0Z9S3D5N1NSK0BJQ35E932K
Last updated: 2026-09-04T11:56:34Z

- Impact (vendor’s label): maintenance (maintenance)
- Status: maintenance complete
- Started: 2026-09-04 09:00 UTC · Resolved: not resolved · Duration: ongoing
- Updates: 3 · Affected components: Canada, Australia
- [Vendor status page: https://status.telnyx.com/incidents/01M0Z9S3D5N1NSK0BJQ35E932K](https://status.telnyx.com/incidents/01M0Z9S3D5N1NSK0BJQ35E932K)
- [Company: Telnyx](https://rewindex.com/company/telnyx.md)

## Timeline of updates

- **maintenance scheduled** 2026-08-26 15:07 UTC: Our Telephony Engineers will perform maintenance on our inbound SIP proxy servers in the Canada (sip.telnyx.ca: http://sip.telnyx.ca) and Australia (sip.telnyx.com.au: http://sip.telnyx.com.au) regions. During this maintenance, our TLS certificate for each proxy server will be renewed. These important changes will happen. - We'll switch Certificate Authority from Sectigo to LetsEncrypt. - The "clientAuth" EKU is being deprecated, which may affect customers who use mTLS (mutual TLS) for SIP signaling. This change may be important for any customer who has our old (current) TLS certificate or root CA certificate (or chain) loaded into an SBC/appliance/phone. A notification was sent to customers recently (21st July, subject "Action may be required: TLS certificate changes for Telnyx SIP proxies"); more-detailed information can be found online here. - https://support.telnyx.com/en/articles/15948276-upcoming-tls-certificate-changes-for-telnyx-sip-proxies For any customer seeking to test TLS compatibility before the renewal, note that our Staging SIP proxy server at sipstaging.telnyx.com:5061 can be used to test both inbound and outbound calls (and registrations); it has a certificate from the same certificate authority. For any customer not using TLS, the change is expected to be completely seamless.
- **maintenance in progress** 2026-09-04 09:00 UTC: Maintenance has started
- **maintenance complete** 2026-09-04 11:56 UTC: We've completed the TLS certificate change at sip.telnyx.com.au: http://sip.telnyx.com.au servers. For sip.telnyx.ca: http://sip.telnyx.ca, we've completed the certificate change at only one of the two proxy servers (sip-anycast2.telnyx.ca: http://sip-anycast2.telnyx.ca, 64.16.250.13). The primary server (at sip-anycast1.telnyx.ca: http://sip-anycast1.telnyx.ca, 192.76.120.31) has not been changed; we're postponing this until Wednesday 9th September (next week) to give some customers a few more days to review and update TLS configurations. Please note that the existing TLS certificate for sip.telnyx.ca: http://sip.telnyx.ca is due to expire on 12th September, so we'll still complete the renewal before the expiry.

## Cite this

Maintenance posted by Telnyx, started 2026-09-04 09:00 UTC, not resolved, 3 update(s).

- Canonical URL: https://rewindex.com/company/telnyx/incidents/01M0Z9S3D5N1NSK0BJQ35E932K
- Citation: Telnyx, “Upcoming TLS Certificate renewals for SIP Trunking Signaling - CA and AU regions” (2026-09-04 09:00 UTC). Archived by Rewindex: https://rewindex.com/company/telnyx/incidents/01M0Z9S3D5N1NSK0BJQ35E932K (CC BY 4.0).
- Markdown link: `[Telnyx: Upcoming TLS Certificate renewals for SIP Trunking Signaling - CA and AU regions (2026-09-04)](https://rewindex.com/company/telnyx/incidents/01M0Z9S3D5N1NSK0BJQ35E932K)`


---
Canonical: https://rewindex.com/company/telnyx/incidents/01M0Z9S3D5N1NSK0BJQ35E932K · Markdown: https://rewindex.com/company/telnyx/incidents/01M0Z9S3D5N1NSK0BJQ35E932K.md · JSON: https://rewindex.com/api/v1/companies/telnyx/incidents/01M0Z9S3D5N1NSK0BJQ35E932K · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T17:48:45.560Z