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
1 h 8 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
7 min 10%
In progress
1 h 1 min 90%
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
30
Days with an incident
21
Median duration
2 h 39 min
This incident
Not comparable
Other Telnyx incidents
All incidents
Telnyx·Data Connectivity Issues - IMSI1
Telnyx Wireless SIMs on IMSI1 could not establish new data sessions or lost data service intermittently. The problem started around 15:45 UTC on November 3, 2026. Telnyx reports that the issue is resolved. Data connectivity is restored. If a device is still impacted, toggle airplane mode or reboot the device to help it reattach to the network.
Telnyx·10DLC Traffic Towards Tier 1 Carriers Delayed
Telnyx 10DLC traffic to Tier 1 carriers AT&T, T-Mobile, and Verizon had delays. Telnyx reports that the issue is resolved. The incident lasted about 11 hours and 36 minutes.
Telnyx·Data Connectivity Issues IMSI1
Telnyx Wireless SIMs with IMSI1 cannot start new data sessions in some regions. Some devices also lose data service during active sessions. Telnyx reports that the incident is resolved. It lasted about 5 hours.
Telnyx·Messaging Latency
Telnyx reported latency that affected messaging webhooks, the messaging API, and delivery times for a subset of messaging. Telnyx implemented a fix and monitored the results. Telnyx reports that the incident is resolved and that the incident lasted 163 minutes.
Telnyx·Telnyx’s Support AI Assistant (TAIA) — Service interruption
Telnyx's Support AI Assistant does not work through the chat or email widget. Customers saw error responses between 14:15 and 15:00 UTC on November 3, 2026. Telnyx reports that the problem is resolved.
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