Retell AI Outage History

Retell AI is up right now

Retell 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.

Source: https://status.retellai.com

Minor August 7, 2026

Some inbound calls failing to connect

Detected by Pingoru
Aug 07, 2026, 09:55 PM UTC
Resolved
Aug 07, 2026, 10:22 PM UTC
Duration
26m
Affected: Phone Call
Timeline · 3 updates
  1. 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.

  2. monitoring Aug 07, 2026, 10:16 PM UTC

    Service should be back to normal. We are continuing to monitor to ensure stability.

  3. resolved Aug 07, 2026, 10:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 29, 2026

Inbound calling not connecting

Detected by Pingoru
Jul 29, 2026, 02:00 PM UTC
Resolved
Jul 29, 2026, 03:42 PM UTC
Duration
1h 41m
Affected: Phone Call
Timeline · 4 updates
  1. investigating Jul 29, 2026, 03:26 PM UTC

    We identified that certain number's inbound is not connecting, investigating. Outbound is not impacted.

  2. 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.

  3. monitoring Jul 29, 2026, 03:39 PM UTC

    This has been fixed, we are monitoring.

  4. resolved Jul 29, 2026, 03:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 14, 2026

Batch calls failing

Detected by Pingoru
Jul 14, 2026, 03:42 PM UTC
Resolved
Jul 14, 2026, 04:32 PM UTC
Duration
49m
Timeline · 3 updates
  1. investigating Jul 14, 2026, 03:42 PM UTC

    Outbound batch calls are failing. We are investigating the issue

  2. investigating Jul 14, 2026, 04:32 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jul 14, 2026, 04:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 1, 2026

TTS provider 11labs v3 model is down

Detected by Pingoru
Jul 01, 2026, 09:45 PM UTC
Resolved
Jul 01, 2026, 10:53 PM UTC
Duration
1h 8m
Timeline · 2 updates
  1. identified Jul 01, 2026, 09:45 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Jul 01, 2026, 10:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 22, 2026

Chats and calls unavailable for GPT-4o and 4o-mini

Detected by Pingoru
Jun 22, 2026, 07:00 AM UTC
Resolved
Jun 22, 2026, 09:03 AM UTC
Duration
2h 3m
Affected: Web CallSMS chatPhone CallAPI chat
Timeline · 3 updates
  1. 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.

  2. monitoring Jun 22, 2026, 08:16 AM UTC

    A fix is being deployed; we are actively monitoring.

  3. resolved Jun 22, 2026, 09:03 AM UTC

    The incident has been resolved

Read the full incident report →

Minor June 12, 2026

Platform voice Grace and Nico not working

Detected by Pingoru
Jun 12, 2026, 07:30 AM UTC
Resolved
Jun 12, 2026, 04:44 PM UTC
Duration
9h 13m
Affected: Web CallPhone Call
Timeline · 2 updates
  1. investigating Jun 12, 2026, 04:31 PM UTC

    The platform voice, Grace and Nico, are not working

  2. resolved Jun 12, 2026, 04:44 PM UTC

    The issue is resolved now

Read the full incident report →

Minor May 28, 2026

Certain calls are not being picked up in time

Detected by Pingoru
May 28, 2026, 03:00 PM UTC
Resolved
May 28, 2026, 04:30 PM UTC
Duration
1h 29m
Affected: Web CallPhone Call
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Major May 25, 2026

Calls returning concurrency_limit_reached

Detected by Pingoru
May 25, 2026, 11:00 PM UTC
Resolved
May 25, 2026, 11:41 PM UTC
Duration
40m
Affected: Web CallPhone Call
Timeline · 1 update
  1. 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.

Read the full incident report →

Major May 25, 2026

Call/chat history, analytics and QA dashboard down

Detected by Pingoru
May 25, 2026, 09:09 PM UTC
Resolved
May 25, 2026, 09:40 PM UTC
Duration
30m
Affected: AlertingAnalyticsDashboardQA
Timeline · 5 updates
  1. 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.

  2. investigating May 25, 2026, 09:12 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 25, 2026, 09:13 PM UTC

    We are continuing to investigate this issue.

  4. 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.

  5. resolved May 25, 2026, 09:40 PM UTC

    The issue has been fixed and all services are back to working.

Read the full incident report →

Minor April 13, 2026

KB Retrieval and QA Failure

Detected by Pingoru
Apr 13, 2026, 11:47 PM UTC
Resolved
Apr 14, 2026, 12:15 AM UTC
Duration
28m
Affected: QAKnowledge Base
Timeline · 2 updates
  1. 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.

  2. resolved Apr 14, 2026, 12:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 16, 2026

Batch calls not sent

Detected by Pingoru
Mar 16, 2026, 06:41 PM UTC
Resolved
Mar 16, 2026, 07:21 PM UTC
Duration
40m
Affected: Phone Call
Timeline · 3 updates
  1. 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.

  2. 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".

  3. resolved Mar 16, 2026, 07:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 16, 2026

Custom LLM calls failing to start

Detected by Pingoru
Mar 16, 2026, 04:39 AM UTC
Resolved
Mar 16, 2026, 04:54 AM UTC
Duration
14m
Affected: Web CallPhone Call
Timeline · 2 updates
  1. 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.

  2. resolved Mar 16, 2026, 04:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 4, 2026

MiniMax TTS issue

Detected by Pingoru
Mar 04, 2026, 10:34 PM UTC
Resolved
Mar 04, 2026, 10:34 PM UTC
Duration
—
Affected: Web CallPhone Call
Timeline · 1 update
  1. 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.

Read the full incident report →

Notice March 4, 2026

Small portion of community voice not working

Detected by Pingoru
Mar 04, 2026, 02:30 PM UTC
Resolved
Mar 04, 2026, 02:30 PM UTC
Duration
—
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor February 20, 2026

Telynx - SIP Trunking Service Degradation

Detected by Pingoru
Feb 20, 2026, 09:43 PM UTC
Resolved
Feb 21, 2026, 12:00 AM UTC
Duration
2h 16m
Affected: Phone Call
Timeline · 2 updates
  1. 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/

  2. resolved Feb 21, 2026, 02:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 10, 2026

Calls failing to start and concurrency stuck

Detected by Pingoru
Feb 10, 2026, 10:12 PM UTC
Resolved
Feb 10, 2026, 10:18 PM UTC
Duration
5m
Affected: Phone Call
Timeline · 2 updates
  1. 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.

  2. resolved Feb 10, 2026, 10:18 PM UTC

    Calls and concurrency should be back to normal.

Read the full incident report →

Minor January 27, 2026

Scheduled batch calls not running

Detected by Pingoru
Jan 27, 2026, 10:30 PM UTC
Resolved
Jan 27, 2026, 10:30 PM UTC
Duration
—
Timeline · 1 update
  1. 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.

Read the full incident report →

Major January 22, 2026

Multilingual transcription issues

Detected by Pingoru
Jan 22, 2026, 11:37 PM UTC
Resolved
Jan 22, 2026, 11:48 PM UTC
Duration
11m
Affected: Web CallPhone Call
Timeline · 2 updates
  1. investigating Jan 22, 2026, 11:37 PM UTC

    We're aware of issues affecting multilingual transcription and are actively investigating.

  2. 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.

Read the full incident report →

Major January 9, 2026

Outbound Calling Service Degradation

Detected by Pingoru
Jan 09, 2026, 08:30 AM UTC
Resolved
Jan 09, 2026, 10:26 AM UTC
Duration
1h 56m
Affected: Phone Call
Timeline · 4 updates
  1. 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.

  2. 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.

  3. monitoring Jan 09, 2026, 10:17 AM UTC

    The issue should have been resolved, we are closely monitoring the status.

  4. resolved Jan 09, 2026, 10:26 AM UTC

    The issue has been fixed

Read the full incident report →

Major December 30, 2025

ASR configuration bug

Detected by Pingoru
Dec 30, 2025, 09:20 PM UTC
Resolved
Dec 30, 2025, 10:04 PM UTC
Duration
44m
Timeline · 4 updates
  1. 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.

  2. investigating Dec 30, 2025, 09:20 PM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. resolved Dec 30, 2025, 10:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 16, 2025

Call and API failures due to Stripe outage

Detected by Pingoru
Dec 16, 2025, 03:10 PM UTC
Resolved
Dec 16, 2025, 03:40 PM UTC
Duration
30m
Affected: APIWeb CallPhone Call
Timeline · 2 updates
  1. 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.

  2. resolved Dec 16, 2025, 07:56 PM UTC

    This incident has been resolved.

Read the full incident report →