Retell AI Outage History
Retell AI is up right nowRetell AI had 30 outages in the last 2 years totaling 27h 56m of downtime — averaging 1.2 incidents per month.
There were 30 Retell AI outages since October 9, 2025 totaling 27h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
Web Calls and Phone Calls Disruption
Timeline · 3 updates
Some inbound calls failing to connect
Timeline · 3 updates
- identified Aug 07, 2026, 09:55 PM UTC
Due to issues with an upstream provider, we are seeing connection issues for a portion of inbound calls. This is not widespread.
- monitoring Aug 07, 2026, 10:16 PM UTC
Service should be back to normal. We are continuing to monitor to ensure stability.
- resolved Aug 07, 2026, 10:22 PM UTC
This incident has been resolved.
Inbound calling not connecting
Timeline · 4 updates
- investigating Jul 29, 2026, 03:26 PM UTC
We identified that certain number's inbound is not connecting, investigating. Outbound is not impacted.
- identified Jul 29, 2026, 03:35 PM UTC
The issue was identified as a datacenter issue from underlying telephony provider, where 2 out of 3 datacenters failed to deliver webhook to Retell backend server.
- monitoring Jul 29, 2026, 03:39 PM UTC
This has been fixed, we are monitoring.
- resolved Jul 29, 2026, 03:42 PM UTC
This incident has been resolved.
Batch calls failing
Timeline · 3 updates
- investigating Jul 14, 2026, 03:42 PM UTC
Outbound batch calls are failing. We are investigating the issue
- investigating Jul 14, 2026, 04:32 PM UTC
We are continuing to investigate this issue.
- resolved Jul 14, 2026, 04:32 PM UTC
This incident has been resolved.
TTS provider 11labs v3 model is down
Timeline · 2 updates
- identified Jul 01, 2026, 09:45 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Jul 01, 2026, 10:53 PM UTC
This incident has been resolved.
partial outage affecting incoming and ongoing call connections
Timeline · 2 updates
- monitoring Jun 24, 2026, 04:31 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 24, 2026, 06:05 PM UTC
This incident has been resolved.
Chats and calls unavailable for GPT-4o and 4o-mini
Timeline · 3 updates
- identified Jun 22, 2026, 08:01 AM UTC
Due to a recent regression, AI calls and chats powered by GPT-4o and GPT-4o mini are currently unavailable. Our team is working to restore service as quickly as possible.
- monitoring Jun 22, 2026, 08:16 AM UTC
A fix is being deployed; we are actively monitoring.
- resolved Jun 22, 2026, 09:03 AM UTC
The incident has been resolved
Platform voice Grace and Nico not working
Timeline · 2 updates
- investigating Jun 12, 2026, 04:31 PM UTC
The platform voice, Grace and Nico, are not working
- resolved Jun 12, 2026, 04:44 PM UTC
The issue is resolved now
Certain calls are not being picked up in time
Timeline · 2 updates
- investigating May 28, 2026, 04:37 PM UTC
Many calls are experiencing high latency, no pickup, or being dropped due to web socket connection issues. We are investigating now.
- resolved May 28, 2026, 05:52 PM UTC
This incident has been resolved. It was due to a connection issue in one of the data centers for the telephony provider. We are adding more fallback routes there.
Calls returning concurrency_limit_reached
Timeline · 1 update
- investigating May 25, 2026, 11:00 PM UTC
Due to an error in the code, the concurrency of orgs are incorrectly calculated and returning concurrency_limit_reached for many calls.
Call/chat history, analytics and QA dashboard down
Timeline · 5 updates
- investigating May 25, 2026, 09:09 PM UTC
Due to a database outage, call/chat history, analytics and QA dashboard down are currently completely down. We are working with the database team to fix the issue.
- investigating May 25, 2026, 09:12 PM UTC
We are continuing to investigate this issue.
- investigating May 25, 2026, 09:13 PM UTC
We are continuing to investigate this issue.
- identified May 25, 2026, 09:33 PM UTC
We are rolling out a fix to direct the traffic to our database replica while the provider is investigating the issue. Note that no call or chat data were lost.
- resolved May 25, 2026, 09:40 PM UTC
The issue has been fixed and all services are back to working.
Agent reading and publishing broken
Timeline · 1 update
- resolved May 08, 2026, 04:50 PM UTC
agent publishing was broken for ~1 hour - returned server error. Calling was not affected
KB Retrieval and QA Failure
Timeline · 2 updates
- monitoring Apr 13, 2026, 11:47 PM UTC
The KB retrieval and QA experienced an issue due to an unintended code change. The issue has been resolved, and we are actively monitoring the systems to ensure continued stability.
- resolved Apr 14, 2026, 12:15 AM UTC
This incident has been resolved.
Batch calls not sent
Timeline · 3 updates
- investigating Mar 16, 2026, 06:41 PM UTC
Starting ~13:32 UTC (8:32 AM PT), batch calls were not being sent due to an internal issue that was triggered in our system. We've identified the root cause and are actively working on a fix.
- monitoring Mar 16, 2026, 07:14 PM UTC
A fix is being deployed and we are monitoring to ensure recovery. As a side effect, batch calls that were missed are being marked as "sent".
- resolved Mar 16, 2026, 07:21 PM UTC
This incident has been resolved.
Custom LLM calls failing to start
Timeline · 2 updates
- identified Mar 16, 2026, 04:39 AM UTC
19:38 PST: custom LLM calls started failing to start due to a bad release. Other types of calls are not impacted. 21:35 PST: a fix is being rolled out, we are keep monitoring the issue.
- resolved Mar 16, 2026, 04:54 AM UTC
This incident has been resolved.
MiniMax TTS issue
Timeline · 1 update
- resolved Mar 04, 2026, 10:34 PM UTC
Between 1:25–2:08pm PT, a provider-side rate-limit configuration issue caused some TTS requests to be silently dropped. This issue has been resolved, and we are adding detection to make sure a fallback will be triggered if this happens again.
Small portion of community voice not working
Timeline · 1 update
- resolved Mar 04, 2026, 06:21 PM UTC
There was an accidental change in the logic of account cleanup that led to the deletion of small portion of community voice resources, which caused those agents with the voice having issues. We have fixed the logic, and have been running a backfill to detect and add back those resources.
Telynx - SIP Trunking Service Degradation
Timeline · 2 updates
- identified Feb 20, 2026, 09:43 PM UTC
We are currently experiencing service degradation affecting SIP trunking through our upstream provider, Telnyx. This may result in call connection issues. https://status.telnyx.com/
- resolved Feb 21, 2026, 02:01 AM UTC
This incident has been resolved.
Calls failing to start and concurrency stuck
Timeline · 2 updates
- identified Feb 10, 2026, 10:12 PM UTC
There were call initialization issues between 1:35pm and 1:43pm PST. Calls are back online now, but concurrency for some users may be stuck. We are working on a fix.
- resolved Feb 10, 2026, 10:18 PM UTC
Calls and concurrency should be back to normal.
Scheduled batch calls not running
Timeline · 1 update
- resolved Jan 28, 2026, 02:52 AM UTC
Scheduled batch calls did not run from 2:35 PM to 5:15 PM PST. The service has now recovered. Any batch calls whose scheduling window still included 5:15 PM were executed at that time. Batch calls whose scheduling window was fully missed were not executed.
Multilingual transcription issues
Timeline · 2 updates
- investigating Jan 22, 2026, 11:37 PM UTC
We're aware of issues affecting multilingual transcription and are actively investigating.
- resolved Jan 22, 2026, 11:48 PM UTC
The issue appears to be resolved and multilingual transcription is recovering. We'll keep monitoring to ensure stability.
Outbound Calling Service Degradation
Timeline · 4 updates
- investigating Jan 09, 2026, 09:26 AM UTC
Outbound calls are currently experiencing issues. Some users report receiving multiple calls from a single dial attempt, or agents being unable to hear audio. We are investigating the root cause.
- identified Jan 09, 2026, 09:58 AM UTC
The root cause has been traced to our telephony stack provider. The issue has been escalated to their support team, who are actively triaging the incident.
- monitoring Jan 09, 2026, 10:17 AM UTC
The issue should have been resolved, we are closely monitoring the status.
- resolved Jan 09, 2026, 10:26 AM UTC
The issue has been fixed
ASR configuration bug
Timeline · 4 updates
- investigating Dec 30, 2025, 09:20 PM UTC
A recent code change introduced an issue in the ASR module that may cause some agents to go offline. We are working on a fix actively.
- investigating Dec 30, 2025, 09:20 PM UTC
We are continuing to investigate this issue.
- monitoring Dec 30, 2025, 10:00 PM UTC
The fix is being pushed to the production, we are observing and monitoring the current system status.
- resolved Dec 30, 2025, 10:04 PM UTC
This incident has been resolved.
Call and API failures due to Stripe outage
Timeline · 2 updates
- monitoring Dec 16, 2025, 04:59 PM UTC
For around 30 minutes, calls and API requests failed due to an issue with Stripe. The outage occurred between 7:10 and 7:40 PST. This has been identified as an outage from our payment provider (Stripe). We are continuing to monitor the situation.
- resolved Dec 16, 2025, 07:56 PM UTC
This incident has been resolved.