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.
State
Investigating
Started
Ongoing for
1 h 42 min
Worst impact
Partial outage
Timeline
1 updateInvestigating
1 h 42 min 100%
Updates
Times in UTCAs posted by Telnyx
We're currently investigating an issue affecting data connectivity for some Telnyx Wireless SIMs. Starting at approximately 15:15 UTC on November 3, 2026, impacted devices may be unable to establish a new data session or may experience intermittent loss of data service. Devices with an existing active session may also be affected. We've identified the issue with an upstream network partner and are actively working with them to restore full service. We'll provide an update within 30 minutes or sooner as more information becomes available. We apologize for any inconvenience this may cause.
Telnyx in the last 90 days
Full historyIncidents in 90 days
29
Days with an incident
20
Median duration
2 h 34 min
This incident
34% 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·Messaging Latency
Telnyx reports messaging webhook latency. Messaging delivery is not affected. Telnyx also sees higher API latency and longer delivery times for some messaging. Telnyx put a fix in place and monitors the results. The incident is under investigation. It started 123 minutes ago.
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.
Telnyx·Messaging API Latency
Telnyx reported delays in webhook delivery latency on the Messaging API, including webhook delivery receipts. Message sending was not affected. Telnyx implemented a fix and the issue is now resolved. The outage lasted about 10 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.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