Inbound call failures to SIP connections
Inbound calls to SIP connections fail with SIP response code 478. Telnyx reports that a change improved DNS resolution on its voice infrastructure and that these calls now process normally. Telnyx is monitoring the service for stability.
State
Monitoring
Started
Ongoing for
9 h 7 min
Worst impact
Notice
Timeline
2 updatesInvestigating
1 h 11%
Monitoring
8 h 7 min 89%
Updates
Times in UTCAs posted by Telnyx
We’ve applied a change to improve DNS resolution reliability on our voice infrastructure, and inbound calls to SIP connections are being processed normally. We’re monitoring to ensure service remains stable.
We are investigating an issue with DNS resolution on our voice infrastructure causing inbound calls to SIP connections to fail with SIP response code 478.
Telnyx in the last 90 days
Full historyIncidents in 90 days
37
Days with an incident
31
Median duration
2 h 49 min
This incident
3.2× the median
Other Telnyx incidents
All incidents
Telnyx·Degraded Performance for AI Assistants Using ElevenLabs
Telnyx AI Assistants that use ElevenLabs as the voice provider had degraded performance in the US region. The incident is resolved. It lasted 3 hours and 45 minutes.

Telnyx·EU Messages expiration issues
Telnyx reported that messages in the EU region did not expire correctly, so they stayed in the sent status and did not finalize. Telnyx resolved the issue and message finalization in EMEA is normal again. The outage lasted about 2 hours and 41 minutes.

Telnyx·GLM-5.3-Flash (Default tier) Inference is Degraded
Telnyx reports that GLM-5.3-Flash inference on the Default tier is degraded. Priority tier and voice agents using GLM-5.3-Flash are not affected. Telnyx resolved the incident after 2 hours and 59 minutes.

Telnyx·MS Teams outbound call drops due to IceConnectivityChecksFailed
MS Teams outbound calls to Telnyx dropped 15 to 21 seconds after answer with IceConnectivityChecksFailed. Telnyx reports the incident resolved. Telnyx pushed a fix on November 13 and flagged no further issues after monitoring.

Telnyx·Data Connectivity Issues - IMSI1
IMSI1 data connectivity did not work. Telnyx reports that the incident is resolved. It lasted 1 hour and 32 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