Telnyx

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-16 18:21 UTC

   [video.telnyx.com](http://video.telnyx.com "video.telnyx.com") is currently unavailable. We have identified an issue affecting the infrastructure hosting the service and are working to restore it. Recovery requires updates to our deployment process, which are in progress.

2. monitoring 2026-10-16 22:54 UTC

   We have restored DNS responses for video.telnyx.com and deployed the service to replacement infrastructure. Successful client connections and video traffic have resumed, and we are monitoring recovery. Some customers may continue to experience connection failures for a few hours...

3. resolved 2026-10-17 00:08 UTC

   This is resolved

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 01:57 UTC

   We’re investigating issues in updating the message status for SMS in our EU datacenter.

2. identified 2026-10-16 03:14 UTC

   We identified a downtime in one of our datastores in europe region

3. resolved 2026-10-16 23:32 UTC

   This is resolved

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-14 15:00 UTC

   Customers interacting with our AI Assistant widget through chat or email may have observed error responses between 14:30 and 15:00 UTC - 14th October 2026. Engineers were alerted to the issue, identified the root caused and resolved the issue. Please repeat your queries again in...

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 18:36 UTC

   We’re investigating issues with processing delays on the v2 API with the following - • Webhook Updates • Phone Number / Connection Settings Updates • Payment Processing

2. investigating 2026-10-13 18:54 UTC

   User number, connection, and outbound profile updates are extremely delayed, and customer payments are also heavily delayed.

3. monitoring 2026-10-13 19:46 UTC

   We’ve identified the issue and have released a fix. Queues are depleting and regular functionality is being restored. We’re monitoring the results.

4. resolved 2026-10-13 19:54 UTC

   This is resolved

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-13 17:25 UTC

   Customers may experience intermittent delays and errors when sending outbound messages. We are investigating the issue.

2. monitoring 2026-10-13 18:17 UTC

   We are monitoring outbound messaging for further delays or errors.

3. resolved 2026-10-13 19:59 UTC

   This incident is now resolved.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 08:31 UTC

   We are currently investigating this issue.

2. monitoring 2026-10-12 09:36 UTC

   Email sending through the Telnyx Email API was unavailable during the following periods: • 9th October, approximately 21:10–22:05 UTC. • 10th October at approximately 22:15 UTC until 12th October at 09:25 UTC. New send requests during these periods failed with **_gw_reject//...

3. resolved 2026-10-12 13:58 UTC

   We have confirmed reports that Email API deliverability has now improved. Email sending through the Telnyx Email API was unavailable during the following periods: - 9th October, approximately 21:10–22:05 UTC. - 10th October at approximately 22:15 UTC until 12th October at 09:25...

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-10 13:15 UTC

   Our monitoring has detected eSIM Provision Error for newly purchased eSIMs.

2. identified 2026-10-10 14:03 UTC

   We have identified root cause of this issue, and we are working on solving this

3. resolved 2026-10-10 15:17 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 17:38 UTC

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

2. monitoring 2026-10-07 13:03 UTC

   Message processing has returned to normal, and all queued messages have been delivered. SMS messages sent over 10DLC long code numbers to AT&T subscribers are now being delivered without delay. We are continuing to monitor traffic closely while our downstream partner and AT&T...

3. resolved 2026-10-07 19:30 UTC

   Message processing has returned to normal, and all queued messages have been delivered. SMS messages sent over 10DLC long code numbers to AT&T subscribers continue being delivered without delay after monitoring period.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-02 14:20 UTC

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

2. monitoring 2026-10-02 15:01 UTC

   Cloud Storage read and write operations should be fully available in us-west-1 region now.

3. resolved 2026-10-02 15:06 UTC

   All cloud storage operations in us-west-1 are fully available.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-28 17:09 UTC

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

2. identified 2026-09-28 17:14 UTC

   We have identified the cause and are working on a fix.

3. resolved 2026-09-28 17:21 UTC

   This is resolved

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 15:00 UTC

   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.

2. identified 2026-09-25 15:04 UTC

   Engineers have identified the root cause and are working to restore Telnyx AI Assistants service.

3. monitoring 2026-09-25 15:18 UTC

   Engineers have restored service and continue to monitor.

4. resolved 2026-09-25 15:54 UTC

   Engineers have resolved the issue and no further errors are observed at this time.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 16:42 UTC

   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.

2. resolved 2026-09-23 19:54 UTC

   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.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 14:16 UTC

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

2. resolved 2026-09-23 18:45 UTC

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

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 13:50 UTC

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

2. resolved 2026-09-23 14:40 UTC

   We implemented a fix and are monitoring the results. Pease monitor this status page for further updates -

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 13:49 UTC

   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.

2. monitoring 2026-09-23 14:39 UTC

   We have implemented a fix and are monitoring the results.

3. resolved 2026-09-23 15:50 UTC

   The issue is confirmed to be resolved.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-22 22:13 UTC

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

2. monitoring 2026-09-23 16:15 UTC

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

3. resolved 2026-09-23 19:48 UTC

   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.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 08:19 UTC

   Customers interacting with our AI Assistant widget through chat or email may observe errors at this time, engineering teams are working to restore the service.

2. identified 2026-09-22 08:36 UTC

   Engineers have identified the root cause and are working to restore Telnyx AI Assistants service.

3. monitoring 2026-09-22 08:59 UTC

   Engineers have restored service and continue to monitor.

4. resolved 2026-09-22 09:19 UTC

   Engineers have resolved the issue and no further errors are observed at this time.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-15 21:57 UTC

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

2. monitoring 2026-09-16 21:57 UTC

   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.

3. resolved 2026-09-18 16:26 UTC

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

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 15:27 UTC

   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.

2. monitoring 2026-09-15 15:48 UTC

   We have implemented a fix and are monitoring the results.

3. identified 2026-09-15 19:04 UTC

   We still investigating the root cause of the datastore latency

4. monitoring 2026-09-15 23:25 UTC

   We have deployed changes to reduce the intermittent latency affecting outbound message sending and are monitoring service performance.

5. resolved 2026-09-16 07:26 UTC

   The elevated latency affecting messaging outbound requests has been resolved. We are continuing to monitor the service.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. investigating 2026-09-14 14:53 UTC

   We are investigating errors from the OpenAI compatible /models and /chat/completions endpoints

2. monitoring 2026-09-14 14:57 UTC

   The fix has been deployed and we are monitoring

3. resolved 2026-09-14 15:00 UTC

   This is resolved

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-10 20:27 UTC

   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.

2. resolved 2026-09-10 20:30 UTC

   The issue affecting API Gateway requests in our dc2-gce location has been resolved, and service has returned to normal.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-10 16:26 UTC

   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.

2. identified 2026-09-10 18:00 UTC

   We have identified the root cause and are implementing a fix to remediate it.

3. monitoring 2026-09-10 18:42 UTC

   We have implemented a fix and are monitoring the recovery process.

4. resolved 2026-09-10 21:15 UTC

   StatefulActor operations are now fully available.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 16:00 UTC

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

2. resolved 2026-09-11 01:43 UTC

   This issue is now resolved.

3. monitoring 2026-09-11 04:04 UTC

   This issue was resolved today at 16.05 UTC and we’re now monitoring

4. resolved 2026-09-11 04:20 UTC

   This issue is now resolved.

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 14:53 UTC

   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.

2. monitoring 2026-09-09 15:54 UTC

   This issue has been mitigated at this time and is being monitored by our team.

3. resolved 2026-09-10 15:59 UTC

   This issue is marked as resolved

Excerpts are shortened. Read the full incident on Telnyx's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 21:29 UTC

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

2. identified 2026-09-08 21:33 UTC

   We have identified the root cause and are actively working on remediation.

3. monitoring 2026-09-08 21:41 UTC

   We have implemented a fix and are monitoring the recovery process.

4. resolved 2026-09-08 21:54 UTC

   Edge Compute StatefulActor ship runtime is now operational.

Excerpts are shortened. Read the full incident on Telnyx's status page.