Delayed delivery of 10DLC SMS messages to AT&T destinations
Message processing has returned to normal, and all queued messages have been delivered. SMS messages sent over 10DLC long code numbers to AT&T subscribers continue being delivered without delay after monitoring period.
The latest update from Telnyx.
State
Resolved
Started
26 d ago
2026-10-06 17:38 UTC
Lasted
25 h 51 min
until 2026-10-07 19:30 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
19 h 25 min 75%
Monitoring
6 h 27 min 25%
Updates
Times in UTCAs posted by Telnyx
Message processing has returned to normal, and all queued messages have been delivered. SMS messages sent over 10DLC long code numbers to AT&T subscribers continue being delivered without delay after monitoring period.
Message processing has returned to normal, and all queued messages have been delivered. SMS messages sent over 10DLC long code numbers to AT&T subscribers are now being delivered without delay. We are continuing to monitor traffic closely while our downstream partner and AT&T complete their investigation into the root cause. We will post a final update once the incident is resolved.
We are investigating delays in the delivery of SMS messages sent over 10DLC long code numbers to AT&T subscribers, beginning October 6 at around 15:00 UTC. Messages are being accepted but may be delivered later than expected to AT&T handsets. Messages to other carriers are not affected. Our team is working with our downstream partner and AT&T to identify the cause and restore normal processing. We will provide further updates as more information becomes available.
Telnyx in the last 90 days
Full historyIncidents in 90 days
23
Days with an incident
18
Median duration
2 h 34 min
This incident
10× the median
Other Telnyx incidents
All incidentsTelnyx·Messaging Webhook Delays
We believe the issue is now resolved
Telnyx·Delays with Messaging Webhooks, Mission Control Number and Porting ordering/configurations
Our team found the root cause of this issue to be due to a network blip leading to various service issues. It was confirmed to be brief and all services are now caught up as of 15:15UTC.
Telnyx·Telephony tokens 503s error
A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.
Telnyx·Unexpected wireless voice usage and charges
Resolved
Telnyx·Wireless session drops in DC2
NAT errors resulted in user-plane issues for some users.
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