Upcoming TLS Certificate renewals for SIP Trunking Signaling - US and EU regions
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 pro
The latest update from Telnyx.
State
Scheduled
Started
5 d ago
2026-10-27 16:11 UTC
Ongoing for
5 days
Worst impact
Maintenance
Timeline
1 updateScheduled
5 days 100%
Updates
Times in UTCAs posted by Telnyx
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 pro
Telnyx in the last 90 days
Full historyIncidents in 90 days
23
Days with an incident
18
Median duration
2 h 34 min
This incident
Not comparable
Other Telnyx incidents
All incidents
Telnyx·Messaging Webhook Delays
We believe the issue is now resolved
Telnyx·Delays with Messaging Webhooks, Mission Control Number and Porting ordering/configurations
Our team found the root cause of this issue to be due to a network blip leading to various service issues. It was confirmed to be brief and all services are now caught up as of 15:15UTC.
Telnyx·Telephony tokens 503s error
A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.
Telnyx·Unexpected wireless voice usage and charges
Resolved
Telnyx·Wireless session drops in DC2
NAT errors resulted in user-plane issues for some users.
Follow Telnyx
Your coding agent knows when Telnyx is down, and tells you when a failure is theirs, not yours. You can also get Telnyx incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "telnyx" and tell me if Telnyx has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=telnyx/feed subscribe https://outages.cc/feed.xml?providers=telnyxFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane