Web App - Operational
Web App
Previous page
Next page
Real-Time Call Processor - Operational
Real-Time Call Processor
Post-Call Processor - Operational
Post-Call Processor
OpenAI → Realtime API - Operational
OpenAI → Realtime API
OpenAI → Chat Completions API - Operational
OpenAI → Chat Completions API
Telnyx → Voice API - Operational
Telnyx → Voice API
Telnyx → Outbound Messaging API - Operational
Telnyx → Outbound Messaging API
Telnyx → Number Searching API - Operational
Telnyx → Number Searching API
Telnyx → Number Ordering API - Operational
Telnyx → Number Ordering API
ElevenLabs → Text to Speech API - Operational
ElevenLabs → Text to Speech API
Deepgram → Text to Speech API - Operational
Deepgram → Text to Speech API
All impacted services have now fully recovered.
We have brought additional capacity online and are seeing improvements for some GPT-5.6 Sol API traffic.We continue to mitigate elevated errors affecting Chat Completions and Responses and are monitoring recovery
We have identified that users are experiencing elevated errors for the impacted services.
We are working on implementing a mitigation.
Our engineering team is continuing to investigate. Calls are still being answered and we're working on getting the portal back up ASAP. Thank you for your patience.
The issue has been resolved. A root cause analysis will be shared shortly.
Latency has returned to baseline levels.
Due to issues with Amazon Web Services, calls may be stuck processing longer than usual.
The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.
Between 06:39 and 07:13 UTC on August 3, a network issue at our upstream cloud provider caused elevated error rates and intermittent connection timeouts on Text-to-Speech and Speech-to-Text requests. At peak, approximately 2% of Speech-to-Text and 1% of Text-to-Speech requests were affected; retried requests generally succeeded. The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.
We have applied the mitigation and are monitoring the recovery.
We are investigating the issue for the listed services.
This incident has been resolved.
A fix has been implemented and traffic has returned to normal. We are monitoring the results.
We are continuing to investigate an issue. STT batch requests may have returned 5xx errors, and some STT websockets may have experienced high latency, starting at 16:03 UTC.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate this issue.
We are currently investigating an issue where some batch requests are returning 400 errors due to remote content download errors. Retrying the request one or more times often succeeds.
Jul 2026 to Sep 2026
Next