Retell AI Outage History

27 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Retell AI status100.00% uptime history

Every Recorded Retell AI Incident

Retell AI incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 25, 2026Speech-to-speech calls failing due to a provider permission issueBetween 1:45 PM PDT Oct 24th and 4:50 PDT Oct 25th, a permission issue with openAI speech-to-speech model caused calls using speech-to-speech agents to fail or go silent. Access has been restored and speech-to-speech…0 minResolved
Sep 17, 2026Call service disruption**Status: resolved.** All times are PST. ## Summary On September 16 at 5:37 PM we deployed a planned improvement to call handling. The improvement was not meant to be active yet, but the deployment turned it on, and…19 minResolved
Sep 5, 2026Web Calls and Phone Calls Disruption### Summary On September 5, a rare race condition in our custom LLM call path caused call scheduling queues across our fleet to stall. Because the failure also made containers appear underutilized, autoscaling never…29 minResolved
Aug 7, 2026Some inbound calls failing to connectThis incident has been resolved.26 minResolved
Jul 29, 2026Inbound calling not connectingThis incident has been resolved.1h 41mResolved
Jul 14, 2026Batch calls failingThis incident has been resolved.49 minResolved
Jul 1, 2026TTS provider 11labs v3 model is downThis incident has been resolved.1h 8mResolved
Jun 24, 2026partial outage affecting incoming and ongoing call connectionsThis incident has been resolved.1h 33mResolved
Jun 22, 2026Chats and calls unavailable for GPT-4o and 4o-miniThe incident has been resolved2h 3mResolved
Jun 12, 2026Platform voice Grace and Nico not workingThe issue is resolved now9h 13mResolved
May 28, 2026Certain calls are not being picked up in timeThis 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.1h 29mResolved
May 25, 2026Call/chat history, analytics and QA dashboard downThe issue has been fixed and all services are back to working.30 minResolved
May 8, 2026Agent reading and publishing brokenagent publishing and get agent was broken for ~1 hour - returned server error. Calling was not affected0 minResolved
Apr 13, 2026KB Retrieval and QA FailureThis incident has been resolved.28 minResolved
Mar 16, 2026Batch calls not sentThis incident has been resolved.40 minResolved
Mar 16, 2026Custom LLM calls failing to startThis incident has been resolved.14 minResolved
Mar 4, 2026MiniMax TTS issueBetween 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…0 minResolved
Mar 4, 2026Small portion of community voice not workingThere 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…-231 minResolved
Feb 20, 2026Telynx - SIP Trunking Service DegradationThis incident has been resolved.2h 16mResolved
Feb 10, 2026Calls failing to start and concurrency stuckCalls and concurrency should be back to normal.5 minResolved
Jan 27, 2026Scheduled batch calls not runningScheduled 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…0 minResolved
Jan 22, 2026Multilingual transcription issuesThe issue appears to be resolved and multilingual transcription is recovering. We'll keep monitoring to ensure stability.11 minResolved
Jan 9, 2026Outbound Calling Service DegradationThe issue has been fixed1h 56mResolved
Dec 30, 2025ASR configuration bugThis incident has been resolved.44 minResolved
Dec 16, 2025Call and API failures due to Stripe outageThis incident has been resolved.30 minResolved
Dec 10, 2025Transcription error for non English trafficFor around 20 minutes, there was a spike of transcription error for certain non English traffic (notably multilingual, Spanish, etc). English traffic was not impacted. This has been identified as outages from underlying…-71 minResolved
Nov 26, 2025Telnyx calls encountering telephony provider permission deniedThis has been resolved now. This is related to an elastic IP issue, which is mitigated now.3 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Retell AI incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Retell AI Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Retell AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Retell AI outage in this window ran 9h 13m, against a mean recovery of 1h 4m. If you depend on Retell AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.