Retell AI

retellai.com (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 4 incidents, 3 major or critical
Rewrites caught: None so far
Next deprecation: None announced

Retell AI incidents per day, last 90 days

Select a day to jump to its incidents below.

How Retell AI reports incidents

Compared with the 152 vendors that have enough incidents to compare. Each tick is one vendor; lower is better on every line.

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

First posted only after it was over

32% 16 of the 50 incidents we have in full detail

The first update already said resolved. Typical vendor: 6%.

Retell AI: higher than most vendors.

Time to resolve

50 min median; 9 in 10 within 2 h 17 min

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Retell AI: lower than most vendors.

Major or critical incidents

0.9 a month 11 in the last 365 days

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Retell AI: around the middle.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Dependencies

What Retell AI relies on and who relies on Retell AI, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Retell AI depends on

Provider	Evidence	Signal
AWS	blamed in 3 incidents; together in 1 outage event “…AWS outage causing some login issues, and history and analytics issue. Calls are NOT impacted. This incident has been resolved. Starting from Oct 20 1am PST, the AWS outage has caused some login issue…” incident	Strong
Telnyx	blamed in 3 incidents “…Telnyx Inbound Calling Down This incident has been resolved. Telnyx Inbound Calling is down We are currently investigating an issue with Telnyx where inbound UDP packets appear to be dropped intermitt…” incident	Strong
Cloudflare	blamed in 1 incident; together in 1 outage event “…otential workarounds. 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	Likely
Auth0	blamed in 1 incident “…spaces 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 We…” incident	Likely
Stripe	blamed in 1 incident “…Call and API failures due to Stripe outage This incident has been resolved. For around 30 minutes, calls and API requests failed due to an issue with Stripe. The outage occurred between 7:10 and 7:40…” incident	Likely
OpenAI	integration affected in 1; together in 1 outage event “…OpenAI TTS Issue This incident has been resolved.…” incident	Weak
Twilio	integration affected in 1 “…Outbound Call Showing Different Number March 3rd: we started to resume Twilio outbound calls with some accounts March 9th: we are resuming Twilio outbound calls across the platform…” incident	Weak

Outage events: AWS us-east-1, Oct 20, 2025, Cloudflare, Jul 14, 2025, OpenAI, Dec 11, 2024 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.