Scheduled maintenance for Programmable Voice - Voice API/Programmable Voice - TeXML EU/US/APAC/UAE
Maintenance has started
The latest update from Telnyx.
State
In progress
Started
Ongoing for
41 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
21 min 52%
In progress
20 min 48%
Updates
Times in UTCAs posted by Telnyx
Maintenance has started
Our Telephony Engineers will perform maintenance on our Programmable Voice and TeXML services in the Europe/US/APAC/UAE region. This maintenance should not disrupt service.
Telnyx in the last 90 days
Full historyIncidents in 90 days
35
Days with an incident
28
Median duration
2 h 42 min
This incident
Not comparable
Other Telnyx incidents
All incidents
Telnyx·EU Messages expiration issues
Telnyx reported that messages in the EU region did not expire correctly, so they stayed in the sent status and did not finalize. Telnyx resolved the issue and message finalization in EMEA is normal again. The outage lasted about 2 hours and 41 minutes.

Telnyx·GLM-5.3-Flash (Default tier) Inference is Degraded
Telnyx reports that GLM-5.3-Flash inference on the Default tier is degraded. Priority tier and voice agents using GLM-5.3-Flash are not affected. Telnyx resolved the incident after 2 hours and 59 minutes.

Telnyx·MS Teams outbound call drops due to IceConnectivityChecksFailed
Microsoft Teams outbound calls to Telnyx drop 15 to 21 seconds after answer with IceConnectivityChecksFailed. Telnyx identified a root cause and pushed a fix to production at 14:10 UTC. Telnyx is monitoring the results.

Telnyx·Data Connectivity Issues - IMSI1
IMSI1 data connectivity did not work. Telnyx reports that the incident is resolved. It lasted 1 hour and 32 minutes.

Telnyx·Data Connectivity Issues - IMSI1
Telnyx Wireless SIMs on IMSI1 could not establish new data sessions, or lost data service intermittently. Telnyx reports that this incident is resolved. The incident lasted about 7 hours.
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.live/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.live/feed.xml?providers=telnyx/feed subscribe https://outages.live/feed.xml?providers=telnyxFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane