Rewindex

ChangesTelnyxSDK Client Credential API Failure

Telnyx: Critical incident: SDK Client Credential API Failure

Major incidentcritical (vendor)Changed Detected status.telnyx.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Telnyx removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: SDK Client Credential API Failure
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-08-04 17:19 UTC
AddedResolved time#5
Before: not present
After: 2026-08-06 09:29 UTC
AddedUpdateinvestigating#6
Before: not present
After: customers may receive HTTP 503 responses from the Client Credential API, which can prevent telephony token creation or validation. This may cause Voice SDK authentication failures, failed registrations, and new call setup failures. Existing active calls are likely unaffected unless they require a fresh token/API call.
AddedUpdatemonitoring#7
Before: not present
After: We identified a capacity issue in the backend service that manages telephony tokens and client SDK credentials. This caused intermittent failures for some credential-related API requests. We increased the number of service pods and raised CPU and memory allocation to better handle request volume. Since making these changes, we are no longer seeing the related 503 errors at the API gateway. The service is currently stable, and we will continue monitoring closely while the incident remains in the monitoring phase.
AddedUpdateresolved#8
Before: not present
After: We identified and mitigated a capacity issue in the backend service that manages telephony tokens and client SDK credentials. This caused intermittent HTTP 503 responses for some credential-related API requests. After increasing service capacity and resource allocation, the service remained stable throughout the monitoring period. We will continue reviewing capacity settings to help prevent recurrence.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

Tuesday, August 4

1 incident change

All Telnyx changesTelnyx profileMarkdownJSON