Telnyx Outage History

We are investigating delays in the delivery of SMS messages sent over 10DLC long code numbers to AT&T subscribers, beginning October 6 at around 15:00 UTC. Messages are being accepted but may be delivered later than expected to AT&T handsets. Messages to other carriers are not affected. Our team is working with our downstream partner and AT&T to identify the cause and restore normal processing. We will provide further updates as more information becomes available.

All cloud storage read and write operations in us-west-1 might be temporarily unavailable. We're actively working on resolving the issue.

We are investigating issues with Kimi K2.6 using our Chat Completions endpoint. Voice Assistants using K2.6 are unaffected.

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.

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.

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.

Users are experiencing elevated API timeouts and 500 errors when interacting with our messaging products.

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

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.

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 are investigating errors from the OpenAI compatible /models and /chat/completions endpoints

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.

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.

Our engineers are currently investigating an issue which is causing one-way/degraded audio on inbound and outbound calls.

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.

Edge Compute StatefulActor deployments are currently unavailable. We are actively investigating the issue.

We are investigation degradation for GLM-5.3 inference

Telnyx object storage read and write operations are intermittently unavailable. We are currently investigating the issue.

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 are investigating the issue at the moment. Updates to follow.

Investigating issues with Australian AI Assistants