Live

Inbound call failures to SIP connections

0

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 updates
19:1521:3223:4802:0504:21
NoticeUpdate postedTimes in UTC

Investigating

1 h 11%

Monitoring

8 h 7 min 89%

Updates

Times in UTC

As posted by Telnyx

Monitoring

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.

Investigating

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 history
90 days agoToday

Incidents in 90 days

37

Days with an incident

31

Median duration

2 h 49 min

This incident

3.2× the median

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

7 days
median 2 h 49 min
90 days agoToday

Other Telnyx incidents

All incidents

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