Retell AI

Affected: Web Call, Phone Call

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-17 01:15 UTC

   We are aware of issues with some calls and are investigating.

2. resolved 2026-09-17 01:35 UTC

   The issue has been found and resolved. About 22% of calls may have been affected and been ended early, or have no audio. A postmortem will be published by EOD 09-17.

3. postmortem 2026-09-17 02:30 UTC

   **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 it began to assign live calls to workers. This change...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-05 23:10 UTC

   Starting at 4:10 PM, web and outbound calls began failing, while inbound calls experienced connection delays. We are actively investigating the issue and will provide an update as soon as more information is available.

2. resolved 2026-09-06 00:19 UTC

   The issue affecting web, outbound, and inbound calls has been resolved. All calling services are operating normally.

3. postmortem 2026-09-06 03:35 UTC

   ### 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 triggered. Between roughly 10:00 and 16:00 PST the impact grew...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-07 21:55 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 2026-08-07 22:16 UTC

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

3. resolved 2026-08-07 22:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-29 14:55 UTC

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

2. identified 2026-07-29 15:35 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 2026-07-29 15:39 UTC

   This has been fixed, we are monitoring.

4. resolved 2026-07-29 15:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-14 15:42 UTC

   Outbound batch calls are failing. We are investigating the issue

2. investigating 2026-07-14 16:32 UTC

   We are continuing to investigate this issue.

3. resolved 2026-07-14 16:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-01 21:45 UTC

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

2. resolved 2026-07-01 22:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-06-24 16:31 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-06-24 18:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, SMS chat, Phone Call, API chat

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-22 07:00 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 2026-06-22 08:16 UTC

   A fix is being deployed; we are actively monitoring.

3. resolved 2026-06-22 09:03 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-12 07:30 UTC

   The platform voice, Grace and Nico, are not working

2. resolved 2026-06-12 16:44 UTC

   The issue is resolved now

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-28 15:00 UTC

   Certain calls are experiencing no pickup, or being dropped due to web socket connection issues. We are investigating now.

2. resolved 2026-05-28 16:30 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.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Alerting, Analytics, Dashboard, QA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-25 21:09 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 2026-05-25 21:12 UTC

   We are continuing to investigate this issue.

3. investigating 2026-05-25 21:13 UTC

   We are continuing to investigate this issue.

4. identified 2026-05-25 21:33 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 2026-05-25 21:40 UTC

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

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-08 03:00 UTC

   agent publishing and get agent was broken for ~1 hour - returned server error. Calling was not affected

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: QA, Knowledge Base

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-04-13 23:47 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 2026-04-14 00:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-16 18:41 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 2026-03-16 19:14 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 2026-03-16 19:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-16 04:39 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 2026-03-16 04:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-03-04 22:34 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.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-04 14:30 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...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-20 21:43 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 2026-02-21 00:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-10 22:12 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 2026-02-10 22:18 UTC

   Calls and concurrency should be back to normal.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-27 22:30 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.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-22 23:37 UTC

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

2. resolved 2026-01-22 23:48 UTC

   The issue appears to be resolved and multilingual transcription is recovering. We'll keep monitoring to ensure stability.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-09 08:30 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 2026-01-09 09:58 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 2026-01-09 10:17 UTC

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

4. resolved 2026-01-09 10:26 UTC

   The issue has been fixed

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-30 21:20 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 2025-12-30 21:20 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-12-30 22:00 UTC

   The fix is being pushed to the production, we are observing and monitoring the current system status.

4. resolved 2025-12-30 22:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: API, Web Call, Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-12-16 15:10 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 2025-12-16 15:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-12-10 19:30 UTC

   For 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 providers. We are working on adding more fallback routes to...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-26 18:48 UTC

   We have observed that calls through retell Telnyx numbers are having issues.

2. resolved 2025-11-26 18:52 UTC

   This has been resolved now. This is related to an elastic IP issue, which is mitigated now.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-10-28 19:28 UTC

   From 11:10 AM – 11:34 AM PST, we observed that inbound calls were experiencing connection issues and timeouts. We have identified the issue as being caused by a brief outage with our telephony provider. The issue has since been resolved and all services are operating normally.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 19:02 UTC

   Starting from Oct 20 1am PST, the AWS outage has caused some login issues, and call history and analytics issues. Regular calls are NOT impacted. Once the AWS outage is over, we will backfill the analytics.

2. monitoring 2025-10-20 23:51 UTC

   The AWS outage has been resolved. We are going to backfill analytics, and keep a close eye on it.

3. resolved 2025-10-21 00:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-10-09 21:40 UTC

   From 1:14pm - 1:47PM PST, we observed that some calls were running into connection issues, and experience timeouts on operations. We identified the issue to be AWS blocking the auto scaling of the instances, causing our call servers got overloaded for a while. We have been...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-10-02 13:30 UTC

   Incident range: 6:30am - 11am PST impact: around 7% of the calls are having abnormally high latency post mortem: Some AWS automatic patches to our transcription clusters caused the container to lost GPU access, and used CPU for transcription, causing extra long latency there....

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-08-26 17:26 UTC

   We experienced a temporary disruption where some outbound calls did not connect as expected. This was due to a telephony sip server provider issue related to elevated system load. The issue was transient and lasted from 8:00 AM to 9:30 AM PDT. The SIP server provider implemented...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-08-25 19:15 UTC

   Starting from 10:25am to 11:23am, for some customers concurrency was not resetting correctly, causing some calls to fail to connect. We are mitigating the issue by manually resetting concurrency, so the dashboard may not reflect the actual current value. We identified the root...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-08-08 04:40 UTC

   19:42: there start to be reports on single / multi prompt agents having issues with function parameter being empty. 21:25: issue was identified and a hotfix is being rolled out. We are keep monitoring the issue.

2. resolved 2025-08-08 05:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-07-24 15:15 UTC

   Starting from around 6:30am, elevenlabs TTS is having a full scale outage: https://status.elevenlabs.io/incidents/01K0YAV1N4W7EZW1BMQCQJ4YJR Our platform traffic starts to fallback to other providers, and the volume of traffic started to break other TTS providers, and that's why...

2. resolved 2025-07-24 17:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-07-14 22:20 UTC

   Our telephony SIP provider confirmed there's an ongoing outage that led to phone call not connecting. We are escalating now, and is trying potential workarounds.

2. identified 2025-07-14 22:23 UTC

   Telephony provider confirmed that this is related to an outage with Cloudflare DNS, which they use in certain internal components. A change is being applied to mitigate. related incident: https://www.cloudflarestatus.com/incidents/28r0vbbxsh8f

3. identified 2025-07-14 22:25 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2025-07-14 22:28 UTC

   The fix has been applied and phone calls are back to normal at the moment, we are keep monitoring.

5. monitoring 2025-07-14 22:28 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-07-14 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-07-14 10:00 UTC

   3am: a culprit release was deployed, leading to some of the conversation flow agents stay silent after a function. It happens when a function and response is happening at same time, and is due to a message order issue before feeding to LLM. 8am: a fix is being deployed 8:30am:...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Dashboard

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-06-25 23:11 UTC

   Users are currently unable to sign up or create new workspaces on our platform. This issue stems from reaching the organization creation limit in Auth0, which is blocking new account provisioning. We are actively working with Auth0 to increase the limit

2. identified 2025-06-26 02:02 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2025-06-26 02:03 UTC

   The issue has been resolved, and new users can now sign up. Users who encountered sign-up issues today can proceed and log into the system without any problems.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-06-21 16:30 UTC

   9:30am: Incident started, where agents are not proactively responding to users when it has a low interruption setting. The behavior seen can include - Custom LLM not requesting responses - Retell agents not responding to user response 10:48am: A fix is being pushed, we start to...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-06-19 02:09 UTC

   We have identified and fixed issues affecting transfer phone number with static number and missing call objects in custom tool invocations. Both issues have been fully resolved after 1 hour and 20 minutes of downtime.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-13 17:15 UTC

   We have identified that starting from 9:30am PDT, all Telnyx inbound calls are very choppy. With the current investigation, it indicates that this is a telephony issue, and we have escalated to our telephony carriers and partners, awaiting their response and fix. Telnyx outbound...

2. monitoring 2025-06-13 19:51 UTC

   The choppy issue seems resolved. We will keep monitoring and will help telephony partners find the root cause to help them prevent this from happening again.

3. resolved 2025-06-13 21:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-06-09 22:52 UTC

   3:15pm PDT: There starts to have a resource initialization problem with single prompt agents, causing the concurrency counter to pile up and not get cleared, and caused subsequent calls to get rejected 3:30pm PDT: a fix is starting to get rolled out, and we are resetting...

2. resolved 2025-06-09 23:14 UTC

   4:12pm: The fix has been deployed, and we've cleared the concurrency counter again to remove all the effects from the issue.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-05-22 04:34 UTC

   The issue is identified and is being mitigated. A fix is rolling out.

2. resolved 2025-05-22 04:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-05-20 00:33 UTC

   Due to a technical issue, some calls experienced failures when performing cold transfers with agent numbers or warm transfers. This led to unexpected call drop-offs during transfer attempts. A fix is currently being deployed to resolve the issue. Impact window: May 19, 1:44 PM...

2. resolved 2025-05-20 01:47 UTC

   This incident has been resolved. We are working internally to add more test cases to prevent this from happening.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-05-18 21:00 UTC

   Due to a technical issue, the recordings for calls initiated between 2:04 PM and 3:00 PM were lost. All other functionalities — including the calls themselves, transcripts, and logs — were fully unaffected.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Phone Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-05-15 23:53 UTC

   Telnyx Inbound Calling is down We are currently investigating an issue with Telnyx where inbound UDP packets appear to be dropped intermittently, resulting in call failures. Our team is actively working with Telnyx to escalate and resolve the issue. Update: Inbound traffic has...

2. resolved 2025-05-16 01:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-08 23:22 UTC

   2am: some calls have not been connected when background speech denoising is enabled 10am: rolled out some fixes which resolved the issue. 3:30pm: received some new reports that calls are not connected. Currently investigating, seems to be related to the network settings of new...

2. monitoring 2025-05-09 00:14 UTC

   We've identified the issue with the subnet configuration, and a fix has been applied, and traffic should be back to normal now. We are keeping a close eye now on the issue. The feature is turned back on now.

3. resolved 2025-05-09 03:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Affected: Web Call, Phone Call

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-24 09:50 UTC

   Please switch to English or a specific language for now—we’re investigating the issue.

2. investigating 2025-04-24 09:51 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-04-24 16:21 UTC

   A fix is being patched.

4. resolved 2025-04-24 17:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-04-23 18:30 UTC

   LLM API returned 200 errors on certain valid inputs. This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-03-31 15:00 UTC

   Telnyx temporarily banned our account at 8:15 AM PDT 03/31/2025 due to a scammer being reported on the platform, which triggered a traceback event. We’ve implemented KYC measures along with several detection protocols, and have reported all remediation steps to Telnyx. The ban...

Excerpts are shortened. Read the full incident on Retell AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-03-15 04:11 UTC

   TTS provider openai is down, we've monitoring the issue and will update you once it's resolved. If you have TTS fallback set up, it will be used now. Otherwise you might want to change the TTS provider in the agent setting in the interim of incident.

2. resolved 2025-03-15 04:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Retell AI's status page.