Data Connectivity Issues - IMSI1
Telnyx reported data connectivity problems on IMSI1. An IMSI1 partner stabilized the service and restored live traffic. Telnyx monitored the recovery of data sessions. Telnyx marked this incident resolved.
State
Resolved
Started
Lasted
1 h 32 min
Worst impact
Notice
Timeline
3 updatesIdentified
1 h 1 min 67%
Monitoring
30 min 33%
Updates
Times in UTCAs posted by Telnyx
This was a duplicate entry. Updates on the IMSI1 data connectivity issue continue on the main incident.
Our partner has resumed sending traffic. We are monitoring the recovery of data sessions
Our IMSI1 partner has confirmed that they have stabilized the service and are currently restoring live traffic. Service restoration is still in progress.
Telnyx in the last 90 days
Full historyIncidents in 90 days
32
Days with an incident
22
Median duration
2 h 39 min
This incident
42% shorter than the median
Other Telnyx incidents
All incidents
Telnyx·Data Connectivity Issues - IMSI1
Telnyx Wireless SIMs on IMSI1 had a partial data outage. Some SIMs could not start new data sessions, and some lost data service. Telnyx reports that the incident is resolved. The outage lasted about 7 hours.
Telnyx·Data Connectivity Issues - IMSI1
Telnyx Wireless SIMs on IMSI1 could not start new data sessions, or lost data service at times. The incident started around 15:45 UTC on November 3, 2026. Telnyx reports that the incident is resolved and that data connectivity is restored. If a device is still affected, toggling airplane mode or rebooting may 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 was delayed. Telnyx reports that the issue is resolved. The outage lasted about 11 hours and 37 minutes.
Telnyx·Data Connectivity Issues IMSI1
Telnyx Wireless SIMs with IMSI1 had data connectivity problems in some regions. Affected devices could not start a new data session and existing sessions could drop. Telnyx reports that the incident is resolved, and it lasted about four hours and fifty eight minutes.
Telnyx·Messaging Latency
Telnyx reported latency in messaging webhooks, and later also increased API latency and delivery times for a subset of messaging. Telnyx made a fix and monitored the results. The incident is resolved and lasted about 2 hours and 43 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.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