**Telnyx experienced a 40-hour major outage affecting the Client Credential API**, causing HTTP 503 errors that prevented telephony token creation and validation, resulting in Voice SDK authentication failures, failed registrations, and new call setup failures. Existing active calls were largely unaffected. The root cause was a backend capacity issue, resolved by scaling up service pods and increasing CPU and memory allocation, after which 503 errors ceased and the service stabilized.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with