Scheduled maintenance for Programmable Wireless - US
The Wireless team will be upgrading the software on our subscriber database (HSS). Before the upgrade, signalling traffic will be moved to a standby node, and it will be moved back once the upgrade is complete. Devices attaching to the network, re-authenticating or receiving SMS may see a brief delay while traffic is moved, after which they will retry automatically. Established data sessions are not expected to be affected. This affects Programmable Wireless users in all regions.
The latest update from Telnyx.
State
Resolved
Started
Lasted
5 h 28 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
5 h 28 min 100%
Updates
Times in UTCAs posted by Telnyx
The Wireless team will be upgrading the software on our subscriber database (HSS). Before the upgrade, signalling traffic will be moved to a standby node, and it will be moved back once the upgrade is complete. Devices attaching to the network, re-authenticating or receiving SMS may see a brief delay while traffic is moved, after which they will retry automatically. Established data sessions are not expected to be affected. This affects Programmable Wireless users in all regions.
Telnyx in the last 90 days
Full historyIncidents in 90 days
33
Days with an incident
24
Median duration
2 h 39 min
This incident
Not comparable
Other Telnyx incidents
All incidents
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.
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.
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