Telnyx had 106 outages in the last 2 years totaling 1024h 36m of downtime — averaging 4.4 incidents per month.
There were 106 Telnyx outages since February 22, 2026 totaling 1024h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
All cloud storage read and write operations in us-west-1 might be temporarily unavailable. We're actively working on resolving the issue.
Cloud Storage read and write operations should be fully available in us-west-1 region now.
All cloud storage operations in us-west-1 are fully available.
We are investigating issues with Kimi K2.6 using our Chat Completions endpoint. Voice Assistants using K2.6 are unaffected.
We have identified the cause and are working on a fix.
This is resolved
Customers interacting with our AI Assistant widget through chat or email may observe error responses at this time, engineering teams are working to restore the service.
Engineers have identified the root cause and are working to restore Telnyx AI Assistants service.
Engineers have restored service and continue to monitor.
Engineers have resolved the issue and no further errors are observed at this time.
We are investigating delayed MMS delivery to AT&T destinations. Messages are being delivered, but with delays. SMS to AT&T and MMS to other carriers are unaffected. We are working with our downstream partner to identify the cause of the delay.
MMS delivery to AT&T destinations from 10DLC long codes returned to normal latency as of 18:30 UTC. Messages delayed during the incident were ultimately delivered; no resend is required.
We are aware of an issue affecting data connectivity on IMSI1 for SIMs while roaming. Affected devices may repeatedly lose their data session or fail to reconnect on certain networks. We are still investigating and working on a fix. This is a network-side issue, no action is required on affected devices (rebooting or re-provisioning will not change the behaviour while we work the fix). We will post updates as we make progress and confirm once the issue is fully resolved. Thank you for your patience.
This incident has been resolved. The issue affecting roaming data connectivity for some SIMs has been corrected, and service has returned to normal. Affected devices have re-established their data sessions and are operating as expected. No action is required on your end. Thank you for your patience while we resolved this.
Users are experiencing elevated API timeouts and 500 errors when interacting with our messaging products.
We implemented a fix and are monitoring the results. Pease monitor this status page for further updates -
Our engineering team is investigating this with priority. This may also impact 2FA login to the portal. Updates will be provided on this status page.
We have implemented a fix and are monitoring the results.
The issue is confirmed to be resolved.
We are investigating an elevated rate of MMS send failures (error 40008) affecting 10DLC senders assigned to 501(c)(3) tax-exempt campaigns. Not all traffic in this segment is affected; we are working to identify the exact scope. SMS 501(c)(3) traffic is not impacted as well as SMS and MMS traffic on normal 10DLC routes.
Our downstream partner has implemented a fix for an issue causing MMS messages from 10DLC senders on 501(c)(3) tax-exempt campaigns to be falsely rejected with error 40008. Error rates have returned to normal levels since the fix was applied. We are currently monitoring live traffic.
Our downstream partner's fix for MMS messages from 10DLC senders on 501(c)(3) tax-exempt campaigns being falsely rejected with error 40008 has been confirmed. Error rates have remained at normal levels throughout the monitoring period.
We are currently investigating reports of encoding issues affecting a subset of outbound SMS messages to T-Mobile. End users may be receiving messages with garbled or unreadable text. We are actively investigating with our downstream partner and will provide an update as soon as we have more information.
Our downstream partner has deployed a fix for garbled message bodies on 10DLC SMS to T-Mobile destinations. The issue impacted 10DLC senders assigned to 501(c)(3) tax-exempt campaigns predominantly. Test messages to T-Mobile destinations are now delivering intact.
Our downstream partner's fix for garbled message bodies on 10DLC SMS to T-Mobile destinations has been confirmed. Impact was limited to 10DLC senders assigned to 501(c)(3) tax-exempt campaigns. Both test and live traffic to T-Mobile destinations are delivering intact. An RCA will follow.
We’re noticing higher response times on our v2 API related to outbound message sending. We’re investigating the issue and will provide updates on resolution.
We have implemented a fix and are monitoring the results.
We still investigating the root cause of the datastore latency
We have deployed changes to reduce the intermittent latency affecting outbound message sending and are monitoring service performance.
The elevated latency affecting messaging outbound requests has been resolved. We are continuing to monitor the service.
We are investigating errors from the OpenAI compatible /models and /chat/completions endpoints
The fix has been deployed and we are monitoring
This is resolved
Between approximately 5:00pm and 5:10pm UTC, some API Gateway requests in our dc2-gce location returned errors. The issue has been resolved and service has returned to normal.
The issue affecting API Gateway requests in our dc2-gce location has been resolved, and service has returned to normal.
We're experiencing site-related difficulties which impact the deployment and invocation of StatefulActor objects on Edge Compute. We're currently investigating the root cause.
We have identified the root cause and are implementing a fix to remediate it.
We have implemented a fix and are monitoring the recovery process.
StatefulActor operations are now fully available.
Our engineers are currently investigating an issue which is causing one-way/degraded audio on inbound and outbound calls.
This issue is now resolved.
This issue was resolved today at 16.05 UTC and we’re now monitoring
This issue is now resolved.
Our engineering teams are currently investigating an issue contributing to failed/delayed call recording deliveries. Impact was also observed with faxing and conference establishment, beginning around 14:00UTC.
This issue has been mitigated at this time and is being monitored by our team.
This issue is marked as resolved
Edge Compute StatefulActor deployments are currently unavailable. We are actively investigating the issue.
We have identified the root cause and are actively working on remediation.
We have implemented a fix and are monitoring the recovery process.
Edge Compute StatefulActor ship runtime is now operational.
Some outbound messages may experience delivery delays. We are investigating and will update as we learn more.
We have applied a fix and are seeing significant improvement in delivery delays for outbound messages. We are monitoring to confirm the issue is fully resolved.
This is resolved
We are investigation degradation for GLM-5.3 inference
We are monitoring GLM-5.3 performance
This is resolved
Telnyx object storage read and write operations are intermittently unavailable. We are currently investigating the issue.
We have identified the root cause and are working on remediation.
The incident has been resolved, the systems recovering.
We are investigating issues with Telnyx Ultra voices not returning from the voices endpoint. This is preventing customers from saving AI Assistants with a Telnyx Ultra voice.
We have identified the issue and are working on a fix
The fix has been deployed and we are monitoring
This is resolved
We are investigating the issue at the moment. Updates to follow.
The issue has been resolved.
We have identified the root cause and are actively working on remediation. Telnyx storage read and write operations are unavailable across all regions.
The incident has been resolved and all cloud storage services are operational.
Investigating issues with Australian AI Assistants
We have identified the root cause and are working on a fix
This incident has been resolved
We experienced SIM data loss in Australia, issue was mitigated, we're monitoring situation.
Issue was resolved
Network connectivity issues caused by underlying vendor
Vendor is actively working to restore connectivity. Programmable Wireless services are affected in all supported regions.
A workaorund was implemented to bypass the impacted AWS service. This enabled data sessions to be re-established. A maintenance window is schedule on Friday morning UTC to move the connectivity back from the workaround solution to the AWS Direct Connects.
Closing