Live

Data Connectivity Issues - IMSI1

Partial outageOfficial update
0

Telnyx reports data connectivity problems for Wireless SIMs on IMSI1. New data sessions may fail, and data service may drop intermittently. Telnyx identified the issue and states that its IMSI1 partner has an outage across their platform.

State

Identified

Started

Ongoing for

2 h 2 min

Worst impact

Partial outage

Timeline

1 update
14:5715:2815:5816:2916:59
Partial outageUpdate postedTimes in UTC

Identified

2 h 2 min 100%

Updates

Times in UTC

As posted by Telnyx

Identified

Telnyx Wireless SIMs on IMSI1 may be unable to establish new data sessions or may experience intermittent loss of data service, beginning around 14:00 UTC on November 5th, 2026. This is caused by our IMSI1 partner experiencing an outage across their platform.

Telnyx in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

31

Days with an incident

22

Median duration

2 h 39 min

This incident

23% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

31 h 37 min
median 2 h 39 min
90 days agoToday

Other Telnyx incidents

All incidents
Telnyx logo

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.

Resolved
Telnyx logo

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.

Resolved
Telnyx logo

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.

Resolved
Telnyx logo

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.

Resolved
Telnyx logo

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.

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=telnyx
Slack
/feed subscribe https://outages.live/feed.xml?providers=telnyx

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane