Data Connectivity Issues - IMSI1
Telnyx Wireless SIMs on IMSI1 may not establish new data sessions or may lose data service intermittently. The IMSI1 partner had an outage across their platform. Telnyx reported the issue resolved at 18:40 UTC on November 3, 2026, and now monitors the service.
State
Identified
Started
Ongoing for
1 h 37 min
Worst impact
Partial outage
Timeline
3 updatesIdentified
1 h 31 min 94%
Monitoring
6 min 6%
Updates
Times in UTCAs posted by Telnyx
Telnyx Wireless SIMs on IMSI1 may be unable to establish new data sessions or may experience intermittent loss of data service, beginning around 15:45 UTC on November 3, 2026. This is caused by our IMSI1 partner experiencing an outage across their platform. The platform has now been stabilised and signalling traffic is gradually being re-introduced to it to restore service.
Issue was resolved at 18:40 UTC. We're now monitoring.
Telnyx Wireless SIMs on IMSI1 may be unable to establish new data sessions or may experience intermittent loss of data service, beginning around 15:45 UTC on November 3, 2026. This is caused by our IMSI1 partner experiencing an outage across their platform. The platform has now been stabilised and signalling traffic is gradually being re-introduced to it to restore service.
Telnyx in the last 90 days
Full historyIncidents in 90 days
30
Days with an incident
20
Median duration
2 h 34 min
This incident
37% shorter than the median
Other Telnyx incidents
All incidents
Telnyx·10DLC Traffic Towards Tier 1 Carriers Delayed
10DLC traffic to Tier 1 carriers AT&T, T-Mobile, and Verizon is delayed. Telnyx identified the problem. Messages still process, but more delays can occur as traffic increases.
Telnyx·Data Connectivity Issues IMSI1
Telnyx reports a data connectivity problem for some Telnyx Wireless SIMs. Affected devices cannot start a new data session or lose data service at times. Telnyx investigates the issue with an upstream network partner.
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.
Telnyx·Telnyx’s Support AI Assistant (TAIA) — Service interruption
Customers interacting with Telnyx’s Support AI Assistant through the chat or email widget may have observed error responses between 14:15 and 15:00 UTC on November 3, 2026. This issue has been resolved.
Telnyx·Outage of some public API endpoints on Nov 2
Telnyx public API endpoints had an outage on Nov 2. User authentication was mainly affected. No calls or messages were affected. Telnyx reports that the incident is resolved. The cause was identified and a fix is in place.
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