Email API messages rejected with gw_reject// injection_failed
We have confirmed reports that Email API deliverability has now improved. Email sending through the Telnyx Email API was unavailable during the following periods: - 9th October, approximately 21:10–22:05 UTC. - 10th October at approximately 22:15 UTC until 12th October at 09:25 UTC. A service restart by our engineers stabilised deliverability after 12th October at 09:25 UTC and resolved the issue.
The latest update from Telnyx.
State
Resolved
Started
20 d ago
2026-10-12 08:31 UTC
Lasted
5 h 27 min
until 2026-10-12 13:58 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
1 h 5 min 20%
Monitoring
4 h 22 min 80%
Updates
Times in UTCAs posted by Telnyx
We have confirmed reports that Email API deliverability has now improved. Email sending through the Telnyx Email API was unavailable during the following periods: - 9th October, approximately 21:10–22:05 UTC. - 10th October at approximately 22:15 UTC until 12th October at 09:25 UTC. A service restart by our engineers stabilised deliverability after 12th October at 09:25 UTC and resolved the issue.
Email sending through the Telnyx Email API was unavailable during the following periods: • 9th October, approximately 21:10–22:05 UTC. • 10th October at approximately 22:15 UTC until 12th October at 09:25 UTC. New send requests during these periods failed with **_gw_reject// injection_failed_**. Messages already queued before each interruption continued to be sent. Customers can retry messages that failed during the affected periods. Service has been restored following a mitigation. We are monitoring stability and working on a permanent fix.
We are currently investigating this issue.
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
2.1× 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