Provider
TelnyxIncident detail
SDK Client Credential API Failure
Resolved incidentCritical
Timeline window
to
Outage alerts
Get alerted the next time Telnyx breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Telnyx posted, oldest to newest, exactly as it appeared on their official status page.
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.
Keep exploring
More from Telnyx
Neighboring incidents on Telnyx's timeline and the rest of their record on OutageDeck.