10DLC Traffic Towards Tier 1 Carriers Delayed
10DLC message traffic to Tier 1 carriers AT&T, T-Mobile, and Verizon is delayed. Telnyx reports that the cause is identified: high traffic volume and network constraints at the carriers. Messages still process, but more delays are possible.
State
Identified
Started
Ongoing for
1 h 30 min
Worst impact
Degraded
Timeline
1 updateIdentified
1 h 30 min 100%
Updates
Times in UTCAs posted by Telnyx
We are experiencing delays across Tier 1 carriers AT&T, T-Mobile, and Verizon due to heightened traffic volume. Carriers report network constraints. Messages are processing but may face further delays as traffic increases. We are monitoring closely.
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
41% shorter than the median
Other Telnyx incidents
All incidents
Telnyx·Data Connectivity Issues IMSI1
Telnyx reports a partial outage that affects data connectivity for some Telnyx Wireless SIMs. Impacted devices cannot start a new data session, or they lose data service intermittently. Telnyx is investigating the issue with an upstream network partner.
Telnyx·Messaging Latency
Telnyx reports messaging webhook latency. Messaging delivery was not affected, but a subset of messaging saw increased API latency and longer delivery times. Telnyx made a fix and now monitors the results. Webhook, API, and delivery latency are back at normal levels.
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.
Telnyx·Outage of some public API endpoints on Nov 2
Some Telnyx public API endpoints did not work on Nov 2. The problem was mainly around user authentication. No calls or messages were affected. Telnyx identified the cause and put a fix in place. The incident is resolved. It lasted about 16 minutes.
Telnyx·Messaging API Latency
Telnyx reported latency in webhook delivery for delivery receipts on the Messaging API. Message sending was not affected. Telnyx implemented a fix, monitored the results, and then resolved the incident. The incident lasted about 9 hours and 50 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