Cresta Outage History

13 incidents recorded over the last 365 days, 13 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.

Every Recorded Cresta Incident

Cresta incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 3, 2026Cresta Documentation Site Login IssuesA fix has been implemented, and users should now be able to log in and access restricted content on docs.cresta.com. We are monitoring the site to confirm that access remains stable. Please contact Support if the issue…1h 3mResolved
Oct 23, 2026Intermittent Cresta Director sign-in issuesThe Cresta Director sign-in issues affecting some users have been resolved. Cloudflare has mitigated the associated network connectivity issue and continues to monitor its network.1h 52mResolved
Oct 20, 2026Live transcription disruption for some Five9 customersEvent delivery has returned to normal, and the live transcription disruption has recovered. We will continue monitoring. Please contact Cresta Support if you continue to experience issues on new calls.59 minResolved
Oct 8, 2026Auto Summarization/Notes OutageBetween 1:45 PM EST and 3:30 PM EST, some customers experienced errors with auto summaries not generating due to a backend service issue. Our team identified the root cause and applied a fix. The issue has been…0 minResolved
Sep 29, 2026Intermittent AI Agent and Agent Assist issues in US West 2On September 29, 2026, from approximately 4:30–5:50 PM EDT, some customers in US West 2 experienced intermittent issues with AI Agent and Agent Assist – Voice. Symptoms included some calls failing to process and delays…0 minResolved
Sep 24, 2026Delayed transcription for some US West 2 customersWe have resolved an issue that caused some customers to experience delayed transcription in US West due to temporary GPU capacity constraints. The issue affected Deepgram transcription capacity in us-west-2-prod…2h 29mResolved
Sep 4, 2026AI Agent responses and transfers may fail for some customersOn September 4, 2026, from approximately 6:47 AM to 7:34 AM PDT, some Cresta AI Agent customers experienced delayed or failed responses, including calls that did not transfer to live representatives. Engineering…32 minResolved
Jul 31, 2026Delayed or missing post-call summaries and transcriptsWe have resolved an issue that caused some customers to experience delayed or missing post-call summaries and increased after-call work. The issue affected Fireworks AI infrastructure used by our post-call…3h 17mResolved
Jun 29, 2026OpenAI-backed AI feature disruptionBetween approximately 10:26 AM and 11:42 AM ET on June 29, some OpenAI-backed AI features experienced elevated failures across multiple production environments. Impacted features may have included AI Agent responses…-199 minResolved
Jun 22, 2026Cresta Director Platform Intermittent AvailabilityEarlier today, some customers may have experienced intermittent issues accessing parts of the platform. Service has been restored and traffic has remained stable. Based on current information, this appears to have…3h 50mResolved
Mar 18, 2026Insights Performance Degradation (us-east-1)This incident has been resolved.1h 29mResolved
Feb 23, 2026(us-east-1 region) Transcription latency and delayed summariesBetween 12:00 PM ET and 4:00 PM ET on February 23, 2026, some customers in us-east-1-prod experienced elevated transcription latency, which could cause live transcripts to lag, summaries to take longer to generate, and…0 minResolved
Jan 5, 2026Transcription Service Intermittently AvailableThe post-mortem for this incident is available on our Help Center under Service Notifications. You can access it directly via this link…7h 0mResolved

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 Cresta 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 Cresta 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 Cresta 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 Cresta outage in this window ran 7h, against a mean recovery of 1h 53m. If you depend on Cresta 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.