# Telnyx: Upcoming TLS Certificate renewals for SIP Trunking Signaling - US and EU regions

> Telnyx edited its scheduled TLS certificate renewal notice for inbound SIP proxy servers in the US (sip.telnyx.com) and Europe (sip.telnyx.eu), adding that no disruption to calls or SIP signaling is expected. The edit clarifies expected customer impact; no maintenance start time or duration is shown

Canonical: https://rewindex.com/company/telnyx/incidents/01M5Z2369RSB8MXCRJ707SHJ3P
Last updated: 2026-10-31T15:17:09Z

- Impact (vendor’s label): maintenance (maintenance)
- Status: maintenance scheduled · edited after publishing
- Started: 2026-11-09 09:00 UTC · Resolved: not resolved · Duration: ongoing
- Updates: 1 · Affected components: Europe, US
- [Vendor status page: https://status.telnyx.com/incidents/01M5Z2369RSB8MXCRJ707SHJ3P](https://status.telnyx.com/incidents/01M5Z2369RSB8MXCRJ707SHJ3P)
- [Company: Telnyx](https://rewindex.com/company/telnyx.md)

## Summary

Telnyx edited its scheduled TLS certificate renewal notice for inbound SIP proxy servers in the US (sip.telnyx.com) and Europe (sip.telnyx.eu), adding that no disruption to calls or SIP signaling is expected. The edit clarifies expected customer impact; no maintenance start time or duration is shown. _(machine-written, sol)_
## Timeline of updates

- **maintenance scheduled** 2026-10-27 16:11 UTC _(edited after publishing)_: Our Telephony Engineers will perform maintenance on our inbound SIP proxy servers in the US (sip.telnyx.com: http://sip.telnyx.com) and Europe (sip.telnyx.eu: http://sip.telnyx.eu) regions. No disruption to calls or SIP signaling is expected during this maintenance. During this maintenance, our TLS certificate for each proxy server will be renewed; the four proxy servers will get the update on separate days. These important changes will happen. - We'll switch Certificate Authority from Digicert to LetsEncrypt (which means that the entire certificate chain will be changed). - 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 earlier this year (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 Important: the schedule for this maintenance is changed slightly from what was published on our website (which has been updated with this new schedule). - Mon 09 November (0900 to 1200 UTC) - 64.16.250.10 (sip.telnyx.com: http://sip.telnyx.com IP2) - Thu 12 November (0900 to 1200 UTC) - 192.76.120.10 (sip.telnyx.com: http://sip.telnyx.com IP1) - Mon 16 November (0900 to 1200 UTC) - 185.246.41.141 (sip.telnyx.eu: http://sip.telnyx.eu IP2) - Thu 19 November (0900 to 1200 UTC) - 185.246.41.140 (sip.telnyx.eu: http://sip.telnyx.eu IP1) 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.

## Rewindex changes for this incident

- 2026-10-28 09:13 UTC: [Incident silently edited: Upcoming TLS Certificate renewals for SIP Trunking Signaling - US and EU regions](https://rewindex.com/change/rbffbd51a37af1a.md)


---
Canonical: https://rewindex.com/company/telnyx/incidents/01M5Z2369RSB8MXCRJ707SHJ3P · Markdown: https://rewindex.com/company/telnyx/incidents/01M5Z2369RSB8MXCRJ707SHJ3P.md · JSON: https://rewindex.com/api/v1/companies/telnyx/incidents/01M5Z2369RSB8MXCRJ707SHJ3P · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-10-31T15:17:09.321Z