outages.live
Live
TTelnyxMaintenance · 2026-10-18 08:12 UTC

Scheduled maintenance for Programmable Wireless - US

MaintenanceOfficial update

The Wireless team will move voice (IMS) session handling at our US core site to upgraded infrastructure to improve VoLTE call reliability. During the window, new voice registrations may briefly fail and retry while traffic is moved; existing sessions and data services are not expected to be affected, and any disruption is not expected to last more than 5 minutes. Affected users are in North, Central and South America and the Caribbean.

The latest update from Telnyx.

State

Scheduled

Started

14 d ago

2026-10-18 08:12 UTC

Ongoing for

14 days

Worst impact

Maintenance

Timeline

1 update
Oct 18Oct 21Oct 25Oct 29Nov 1
MaintenanceUpdate postedDates in UTC

Scheduled

14 days 100%

Updates

Times in UTC

As posted by Telnyx

Scheduled2026-11-01 17:18 UTC

The Wireless team will move voice (IMS) session handling at our US core site to upgraded infrastructure to improve VoLTE call reliability. During the window, new voice registrations may briefly fail and retry while traffic is moved; existing sessions and data services are not expected to be affected, and any disruption is not expected to last more than 5 minutes. Affected users are in North, Central and South America and the Caribbean.

Telnyx in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

23

Days with an incident

18

Median duration

2 h 34 min

This incident

Not comparable

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

31 h 37 min
median 2 h 34 min
90 days agoToday

Other Telnyx incidents

All incidents
T

Telnyx·Messaging Webhook Delays

We believe the issue is now resolved

Resolvedresolved 2 d ago
T

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.

Resolvedresolved 3 d ago
T

Telnyx·Telephony tokens 503s error

A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.

Resolvedresolved 4 d ago
T

Telnyx·Unexpected wireless voice usage and charges

Resolved

Resolvedresolved 3 d ago
T

Telnyx·Wireless session drops in DC2

NAT errors resulted in user-plane issues for some users.

Resolvedresolved 4 d ago

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.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.

RSS
https://outages.cc/feed.xml?providers=telnyx
Slack
/feed subscribe https://outages.cc/feed.xml?providers=telnyx

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane