Wireless Maintenance Europe Site (FR5)
The Wireless team will be performing planned maintenance on network elements serving our European site. Devices roaming in Europe may experience a brief data interruption while sessions re-establish, not expected to last more than 5 minutes per device. No action is required from customers.
The latest update from Telnyx.
State
Scheduled
Started
Ongoing for
1 h 52 min
Worst impact
Maintenance
Timeline
1 updateScheduled
1 h 52 min 100%
Updates
Times in UTCAs posted by Telnyx
The Wireless team will be performing planned maintenance on network elements serving our European site. Devices roaming in Europe may experience a brief data interruption while sessions re-establish, not expected to last more than 5 minutes per device. No action is required from customers.
Telnyx in the last 90 days
Full historyIncidents in 90 days
30
Days with an incident
21
Median duration
2 h 39 min
This incident
Not comparable
Other Telnyx incidents
All incidents
Telnyx·Data Connectivity Issues - IMSI1
Telnyx Wireless SIMs on IMSI1 could not start new data sessions, or lost data service at times. The incident started around 15:45 UTC on November 3, 2026. Telnyx reports that the incident is resolved and that data connectivity is restored. If a device is still affected, toggling airplane mode or rebooting may help it reattach to the network.
Telnyx·10DLC Traffic Towards Tier 1 Carriers Delayed
Telnyx 10DLC traffic to Tier 1 carriers AT&T, T-Mobile, and Verizon was delayed. Telnyx reports that the issue is resolved. The outage lasted about 11 hours and 37 minutes.
Telnyx·Data Connectivity Issues IMSI1
Telnyx Wireless SIMs with IMSI1 had data connectivity problems in some regions. Affected devices could not start a new data session and existing sessions could drop. Telnyx reports that the incident is resolved, and it lasted about four hours and fifty eight minutes.
Telnyx·Messaging Latency
Telnyx reported latency in messaging webhooks, and later also increased API latency and delivery times for a subset of messaging. Telnyx made a fix and monitored the results. The incident is resolved and lasted about 2 hours and 43 minutes.
Telnyx·Telnyx’s Support AI Assistant (TAIA) — Service interruption
Customers interacting with Telnyx’s Support AI Assistant through the chat or email widget may have observed error responses between 14:15 and 15:00 UTC on November 3, 2026. This issue has been resolved.
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