Telnyx: SDK Client Credential API Failure
Affected components: San Jose, CAAshburn, VALondon, UKChicago, ILSydney, Australia
Timeline of updates
- investigating
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.
- monitoring
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.
- resolved
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.
Changes Rewindex caught on this incident
Impact, status and times are the vendor’s own, as last archived. View on status.telnyx.com (opens in new tab).