ElevenLabs Outage History

ElevenLabs is up right now

Pingoru has recorded 168 incidents for ElevenLabs: 168 in the last 12 months and 95 in the last 90 days.

Source: status.elevenlabs.io

168incidents recorded
168last 12 months
95last 90 days
5 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct30
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct3%
Pingoru began tracking ElevenLabs in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261023 of 720 (3%)
May 2026917 of 744 (2%)
June 2026618 of 720 (2%)
July 20261033 of 744 (4%)
August 20262721 of 744 (3%)
September 20263353 of 720 (7%)
October 20263016 of 591 (3%)

Incidents, newest first

Minor August 24, 2026 [EU (Enterprise-only)] Media not loading across several products 9h 53m Other APIs, Other Agents APIs, All features

Started Aug 24, 2026, 08:49 AM UTC· resolved Aug 24, 2026, 06:43 PM UTC

  1. investigating Aug 24, 2026, 08:49 AM UTC

    We’re currently experiencing issues loading media across several products, including Studio, Audiobooks, Image & Video, Music and Dubbing. We are actively investigating the cause.

  2. identified Aug 24, 2026, 10:18 AM UTC

    We have located the cause of the elevated errors, and we are working on a fix.

  3. identified Aug 24, 2026, 11:42 AM UTC

    The error rate has decreased, although the issue has not been fully resolved yet. We are continuing to work toward a complete resolution.

  4. identified Aug 24, 2026, 02:53 PM UTC

    We are currently working to deploy a targeted fix to resolve the existing issues of media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. We will pass further updates as we track the deployment of this fix.

  5. identified Aug 24, 2026, 05:12 PM UTC

    Work is still underway to release a fix to resolve media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. Until the fix is fully rolled out, common symptoms may include failures when exporting media in Studio, Dubbing, and other products. We'll continue to pass further updates as we track the deployment of this fix.

  6. resolved Aug 24, 2026, 06:43 PM UTC

    Our engineers have traced media loading error rates as they have returned to baseline. Studio, Audiobooks, Image & Video, Music and Dubbing products should now functional normally.

Read the full incident report →

Minor August 24, 2026 [Global (United States)] Media not loading across several products 9h 53m Other APIs, Other Agents APIs, All features

Started Aug 24, 2026, 08:49 AM UTC· resolved Aug 24, 2026, 06:43 PM UTC

  1. investigating Aug 24, 2026, 08:49 AM UTC

    We’re currently experiencing issues loading media across several products, including Studio, Audiobooks, Image & Video, Music and Dubbing. We are actively investigating the cause.

  2. identified Aug 24, 2026, 10:18 AM UTC

    We have located the cause of the elevated errors, and we are working on a fix.

  3. identified Aug 24, 2026, 11:42 AM UTC

    The error rate has decreased, although the issue has not been fully resolved yet. We are continuing to work toward a complete resolution.

  4. identified Aug 24, 2026, 02:53 PM UTC

    We are currently working to deploy a targeted fix to resolve the existing issues of media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. We will pass further updates as we track the deployment of this fix.

  5. identified Aug 24, 2026, 05:12 PM UTC

    Work is still underway to release a fix to resolve media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. Until the fix is fully rolled out, common symptoms may include failures when exporting media in Studio, Dubbing, and other products. We'll continue to pass further updates as we track the deployment of this fix.

  6. resolved Aug 24, 2026, 06:43 PM UTC

    Our engineers have traced media loading error rates as they have returned to baseline. Studio, Audiobooks, Image & Video, Music and Dubbing products should now functional normally.

Read the full incident report →

Minor August 24, 2026 [India (Enterprise-only)] Media not loading across several products 9h 53m Other APIs, Other Agents APIs, All features

Started Aug 24, 2026, 08:49 AM UTC· resolved Aug 24, 2026, 06:43 PM UTC

  1. investigating Aug 24, 2026, 08:49 AM UTC

    We’re currently experiencing issues loading media across several products, including Studio, Audiobooks, Image & Video, Music and Dubbing. We are actively investigating the cause.

  2. identified Aug 24, 2026, 10:18 AM UTC

    We have located the cause of the elevated errors, and we are working on a fix.

  3. identified Aug 24, 2026, 11:42 AM UTC

    The error rate has decreased, although the issue has not been fully resolved yet. We are continuing to work toward a complete resolution.

  4. identified Aug 24, 2026, 02:53 PM UTC

    We are currently working to deploy a targeted fix to resolve the existing issues of media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. We will pass further updates as we track the deployment of this fix.

  5. identified Aug 24, 2026, 05:12 PM UTC

    Work is still underway to release a fix to resolve media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. Until the fix is fully rolled out, common symptoms may include failures when exporting media in Studio, Dubbing, and other products. We'll continue to pass further updates as we track the deployment of this fix.

  6. resolved Aug 24, 2026, 06:43 PM UTC

    Our engineers have traced media loading error rates as they have returned to baseline. Studio, Audiobooks, Image & Video, Music and Dubbing products should now functional normally.

Read the full incident report →

Minor August 24, 2026 [Singapore (Enterprise-only)] Media not loading across several products 9h 53m Other APIs, Other Agents APIs, All features

Started Aug 24, 2026, 08:49 AM UTC· resolved Aug 24, 2026, 06:43 PM UTC

  1. investigating Aug 24, 2026, 08:49 AM UTC

    We’re currently experiencing issues loading media across several products, including Studio, Audiobooks, Image & Video, Music and Dubbing. We are actively investigating the cause.

  2. identified Aug 24, 2026, 10:18 AM UTC

    We have located the cause of the elevated errors, and we are working on a fix.

  3. identified Aug 24, 2026, 11:42 AM UTC

    The error rate has decreased, although the issue has not been fully resolved yet. We are continuing to work toward a complete resolution.

  4. identified Aug 24, 2026, 02:53 PM UTC

    We are currently working to deploy a targeted fix to resolve the existing issues of media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. We will pass further updates as we track the deployment of this fix.

  5. identified Aug 24, 2026, 05:12 PM UTC

    Work is still underway to release a fix to resolve media loading within Studio, Audiobooks, Image & Video, Music and Dubbing. Until the fix is fully rolled out, common symptoms may include failures when exporting media in Studio, Dubbing, and other products. We'll continue to pass further updates as we track the deployment of this fix.

  6. resolved Aug 24, 2026, 06:43 PM UTC

    Our engineers have traced media loading error rates as they have returned to baseline. Studio, Audiobooks, Image & Video, Music and Dubbing products should now functional normally.

Read the full incident report →

Minor August 18, 2026 Inbound Twilio calls experiencing intermittent connection failures 3m Telephony

Started Aug 18, 2026, 12:39 PM UTC· resolved Aug 18, 2026, 12:43 PM UTC

  1. identified Aug 18, 2026, 12:39 PM UTC

    From ~07:00 UTC, a small percentage of inbound Twilio calls failed to connect due to a configuration error on our side. Affected callers were unable to connect to an agent; outbound calls and other traffic were unaffected. The change has been rolled back and calls have been connecting normally since ~11:00 UTC. No customer action needed.

  2. resolved Aug 18, 2026, 12:43 PM UTC

    Inbound calls are currently operational.

Read the full incident report →

Minor August 18, 2026 [EU (Enterprise-only)] Inbound Twilio calls experiencing intermittent connection failures 3m Telephony

Started Aug 18, 2026, 12:39 PM UTC· resolved Aug 18, 2026, 12:43 PM UTC

  1. identified Aug 18, 2026, 12:39 PM UTC

    From ~07:00 UTC, a small percentage (<1%) of inbound Twilio calls failed to connect due to a configuration error on our side. Affected callers were unable to connect to an agent; outbound calls and other traffic were unaffected. The change has been rolled back and calls have been connecting normally since ~11:00 UTC. No customer action needed.

  2. resolved Aug 18, 2026, 12:43 PM UTC

    Inbound calls are currently operational.

Read the full incident report →

Minor August 18, 2026 [Global (United States)] Inbound Twilio calls experiencing intermittent connection failures 3m Telephony

Started Aug 18, 2026, 12:39 PM UTC· resolved Aug 18, 2026, 12:43 PM UTC

  1. identified Aug 18, 2026, 12:39 PM UTC

    From ~07:00 UTC, a small percentage (<1%) of inbound Twilio calls failed to connect due to a configuration error on our side. Affected callers were unable to connect to an agent; outbound calls and other traffic were unaffected. The change has been rolled back and calls have been connecting normally since ~11:00 UTC. No customer action needed.

  2. resolved Aug 18, 2026, 12:43 PM UTC

    Inbound calls are currently operational.

Read the full incident report →

Minor August 18, 2026 [India (Enterprise-only)] Inbound Twilio calls experiencing intermittent connection failures 3m Telephony

Started Aug 18, 2026, 12:39 PM UTC· resolved Aug 18, 2026, 12:43 PM UTC

  1. identified Aug 18, 2026, 12:39 PM UTC

    From ~07:00 UTC, a small percentage (<1%) of inbound Twilio calls failed to connect due to a configuration error on our side. Affected callers were unable to connect to an agent; outbound calls and other traffic were unaffected. The change has been rolled back and calls have been connecting normally since ~11:00 UTC. No customer action needed.

  2. resolved Aug 18, 2026, 12:43 PM UTC

    Inbound calls are currently operational.

Read the full incident report →

Minor August 18, 2026 [Singapore (Enterprise-only)] Inbound Twilio calls experiencing intermittent connection failures 3m Telephony

Started Aug 18, 2026, 12:39 PM UTC· resolved Aug 18, 2026, 12:43 PM UTC

  1. identified Aug 18, 2026, 12:39 PM UTC

    From ~07:00 UTC, a small percentage (<1%) of inbound Twilio calls failed to connect due to a configuration error on our side. Affected callers were unable to connect to an agent; outbound calls and other traffic were unaffected. The change has been rolled back and calls have been connecting normally since ~11:00 UTC. No customer action needed.

  2. resolved Aug 18, 2026, 12:43 PM UTC

    Inbound calls are currently operational.

Read the full incident report →

Minor August 3, 2026 Elevated error rates on TTS, STT APIs 1m Speech to Text, Text to Speech

Started Aug 03, 2026, 09:34 AM UTC· resolved Aug 03, 2026, 09:36 AM UTC

  1. identified Aug 03, 2026, 09:34 AM UTC

    Between 06:39 and 07:13 UTC on August 3, a network issue at our upstream cloud provider caused elevated error rates and intermittent connection timeouts on Text-to-Speech and Speech-to-Text requests. At peak, approximately 2% of Speech-to-Text and 1% of Text-to-Speech requests were affected; retried requests generally succeeded. The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

  2. resolved Aug 03, 2026, 09:36 AM UTC

    The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

Read the full incident report →

Minor August 3, 2026 [EU (Enterprise-only)] Elevated error rates on TTS, STT APIs 1m Text to Speech, Speech to Text

Started Aug 03, 2026, 09:34 AM UTC· resolved Aug 03, 2026, 09:36 AM UTC

  1. identified Aug 03, 2026, 09:34 AM UTC

    Between 06:39 and 07:13 UTC on August 3, a network issue at our upstream cloud provider caused elevated error rates and intermittent connection timeouts on Text-to-Speech and Speech-to-Text requests. At peak, approximately 2% of Speech-to-Text and 1% of Text-to-Speech requests were affected; retried requests generally succeeded. The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

  2. resolved Aug 03, 2026, 09:36 AM UTC

    The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

Read the full incident report →

Minor August 3, 2026 [Global (United States)] Elevated error rates on TTS, STT APIs 1m Text to Speech, Speech to Text

Started Aug 03, 2026, 09:34 AM UTC· resolved Aug 03, 2026, 09:36 AM UTC

  1. identified Aug 03, 2026, 09:34 AM UTC

    Between 06:39 and 07:13 UTC on August 3, a network issue at our upstream cloud provider caused elevated error rates and intermittent connection timeouts on Text-to-Speech and Speech-to-Text requests. At peak, approximately 2% of Speech-to-Text and 1% of Text-to-Speech requests were affected; retried requests generally succeeded. The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

  2. resolved Aug 03, 2026, 09:36 AM UTC

    The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

Read the full incident report →

Minor August 3, 2026 [India (Enterprise-only)] Elevated error rates on TTS, STT APIs 1m Text to Speech, Speech to Text

Started Aug 03, 2026, 09:34 AM UTC· resolved Aug 03, 2026, 09:36 AM UTC

  1. identified Aug 03, 2026, 09:34 AM UTC

    Between 06:39 and 07:13 UTC on August 3, a network issue at our upstream cloud provider caused elevated error rates and intermittent connection timeouts on Text-to-Speech and Speech-to-Text requests. At peak, approximately 2% of Speech-to-Text and 1% of Text-to-Speech requests were affected; retried requests generally succeeded. The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

  2. resolved Aug 03, 2026, 09:36 AM UTC

    The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

Read the full incident report →

Minor August 3, 2026 [Singapore (Enterprise-only)] Elevated error rates on TTS, STT APIs 1m Text to Speech, Speech to Text

Started Aug 03, 2026, 09:34 AM UTC· resolved Aug 03, 2026, 09:36 AM UTC

  1. identified Aug 03, 2026, 09:34 AM UTC

    Between 06:39 and 07:13 UTC on August 3, a network issue at our upstream cloud provider caused elevated error rates and intermittent connection timeouts on Text-to-Speech and Speech-to-Text requests. At peak, approximately 2% of Speech-to-Text and 1% of Text-to-Speech requests were affected; retried requests generally succeeded. The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

  2. resolved Aug 03, 2026, 09:36 AM UTC

    The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

Read the full incident report →

Minor July 31, 2026 SIP call failures 15h 51m Telephony

Started Jul 31, 2026, 03:08 AM UTC· resolved Jul 31, 2026, 07:00 PM UTC

  1. investigating Jul 31, 2026, 03:08 AM UTC

    Starting at ~1:00 UTC, calls to a portion of phone numbers imported into the ElevenLabs Agent Platform are failing. We are currently working to isolate the root cause and restore full functionality.

  2. identified Jul 31, 2026, 04:00 AM UTC

    We've identified a likely contributing factor related to infrastructure resource constraints affecting SIP call routing. We're currently validating a fix.

  3. resolved Jul 31, 2026, 05:29 AM UTC

    The issue has been resolved. Call routing is now fully restored, and we're assessing follow-ups to improve proactive alerting and prevent recurrence.

  4. investigating Jul 31, 2026, 06:18 AM UTC

    Following the earlier fix, we're seeing renewed inbound call routing failures for a portion of phone numbers. We're currently investigating.

  5. identified Jul 31, 2026, 09:06 AM UTC

    Our team has identified a potential cause of the call outages and is currently validating a fix. We will share further updates as soon as we have more information.

  6. identified Jul 31, 2026, 11:10 AM UTC

    Our team is actively working to add additional logging to our systems and identify the root cause of the issue. In the meantime, the immediate workaround is to remove the affected number and re-add it, if possible.

  7. identified Jul 31, 2026, 01:01 PM UTC

    Our team is still actively working to restore all calls and phone numbers to their normal working state.

  8. identified Jul 31, 2026, 01:26 PM UTC

    We have identified the root cause of the failed SIP calls and prepared a fix.

  9. identified Jul 31, 2026, 02:33 PM UTC

    Calls should be back to normal for the EU and India residencies. The US residency may still experience some downtime, but our team is working to resolve the issue.

  10. identified Jul 31, 2026, 06:02 PM UTC

    Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.

  11. resolved Jul 31, 2026, 07:15 PM UTC

    After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.

Read the full incident report →

Minor July 31, 2026 [EU (Enterprise-only)] SIP call failures 15h 51m Telephony

Started Jul 31, 2026, 03:08 AM UTC· resolved Jul 31, 2026, 07:00 PM UTC

  1. investigating Jul 31, 2026, 03:08 AM UTC

    Starting at ~1:00 UTC, calls to a portion of phone numbers imported into the ElevenLabs Agent Platform are failing. We are currently working to isolate the root cause and restore full functionality.

  2. identified Jul 31, 2026, 04:00 AM UTC

    We've identified a likely contributing factor related to infrastructure resource constraints affecting SIP call routing. We're currently validating a fix.

  3. resolved Jul 31, 2026, 05:29 AM UTC

    The issue has been resolved. Call routing is now fully restored, and we're assessing follow-ups to improve proactive alerting and prevent recurrence.

  4. investigating Jul 31, 2026, 06:18 AM UTC

    Following the earlier fix, we're seeing renewed inbound call routing failures for a portion of phone numbers. We're currently investigating.

  5. identified Jul 31, 2026, 09:06 AM UTC

    Our team has identified a potential cause of the call outages and is currently validating a fix. We will share further updates as soon as we have more information.

  6. identified Jul 31, 2026, 11:12 AM UTC

    Calls should be back to normal for the EU and India residencies. The US residency may still experience some downtime, but our team is working to resolve the issue. In the meantime, the immediate workaround is to remove the affected number and re-add it, if possible.

  7. identified Jul 31, 2026, 01:01 PM UTC

    Our team is still actively working to restore all calls and phone numbers to their normal working state.

  8. identified Jul 31, 2026, 02:33 PM UTC

    We have identified the root cause of the failed SIP calls and prepared a fix.

  9. identified Jul 31, 2026, 06:02 PM UTC

    Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.

  10. resolved Jul 31, 2026, 07:00 PM UTC

    After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.

Read the full incident report →

Minor July 31, 2026 [Global (United States)] SIP call failures 15h 51m Telephony

Started Jul 31, 2026, 03:08 AM UTC· resolved Jul 31, 2026, 07:00 PM UTC

  1. investigating Jul 31, 2026, 03:08 AM UTC

    Starting at ~1:00 UTC, calls to a portion of phone numbers imported into the ElevenLabs Agent Platform are failing. We are currently working to isolate the root cause and restore full functionality.

  2. identified Jul 31, 2026, 04:00 AM UTC

    We've identified a likely contributing factor related to infrastructure resource constraints affecting SIP call routing. We're currently validating a fix.

  3. resolved Jul 31, 2026, 05:29 AM UTC

    The issue has been resolved. Call routing is now fully restored, and we're assessing follow-ups to improve proactive alerting and prevent recurrence.

  4. investigating Jul 31, 2026, 06:18 AM UTC

    Following the earlier fix, we're seeing renewed inbound call routing failures for a portion of phone numbers. We're currently investigating.

  5. identified Jul 31, 2026, 09:06 AM UTC

    Our team has identified a potential cause of the call outages and is currently validating a fix. We will share further updates as soon as we have more information.

  6. identified Jul 31, 2026, 11:12 AM UTC

    Calls should be back to normal for the EU and India residencies. The US residency may still experience some downtime, but our team is working to resolve the issue. In the meantime, the immediate workaround is to remove the affected number and re-add it, if possible.

  7. identified Jul 31, 2026, 01:01 PM UTC

    Our team is still actively working to restore all calls and phone numbers to their normal working state.

  8. identified Jul 31, 2026, 02:33 PM UTC

    We have identified the root cause of the failed SIP calls and prepared a fix.

  9. identified Jul 31, 2026, 06:02 PM UTC

    Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.

  10. resolved Jul 31, 2026, 07:00 PM UTC

    After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.

Read the full incident report →

Minor July 31, 2026 [India (Enterprise-only)] SIP call failures 15h 51m Telephony

Started Jul 31, 2026, 03:08 AM UTC· resolved Jul 31, 2026, 07:00 PM UTC

  1. investigating Jul 31, 2026, 03:08 AM UTC

    Starting at ~1:00 UTC, calls to a portion of phone numbers imported into the ElevenLabs Agent Platform are failing. We are currently working to isolate the root cause and restore full functionality.

  2. identified Jul 31, 2026, 04:00 AM UTC

    We've identified a likely contributing factor related to infrastructure resource constraints affecting SIP call routing. We're currently validating a fix.

  3. resolved Jul 31, 2026, 05:29 AM UTC

    The issue has been resolved. Call routing is now fully restored, and we're assessing follow-ups to improve proactive alerting and prevent recurrence.

  4. investigating Jul 31, 2026, 06:18 AM UTC

    Following the earlier fix, we're seeing renewed inbound call routing failures for a portion of phone numbers. We're currently investigating.

  5. identified Jul 31, 2026, 09:06 AM UTC

    Our team has identified a potential cause of the call outages and is currently validating a fix. We will share further updates as soon as we have more information.

  6. identified Jul 31, 2026, 11:12 AM UTC

    Calls should be back to normal for the EU and India residencies. The US residency may still experience some downtime, but our team is working to resolve the issue. In the meantime, the immediate workaround is to remove the affected number and re-add it, if possible.

  7. identified Jul 31, 2026, 01:01 PM UTC

    Our team is still actively working to restore all calls and phone numbers to their normal working state.

  8. identified Jul 31, 2026, 02:33 PM UTC

    We have identified the root cause of the failed SIP calls and prepared a fix.

  9. identified Jul 31, 2026, 06:02 PM UTC

    Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.

  10. resolved Jul 31, 2026, 07:00 PM UTC

    After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.

Read the full incident report →

Minor July 31, 2026 [Singapore (Enterprise-only)] SIP call failures 15h 51m Telephony

Started Jul 31, 2026, 03:08 AM UTC· resolved Jul 31, 2026, 07:00 PM UTC

  1. investigating Jul 31, 2026, 03:08 AM UTC

    Starting at ~1:00 UTC, calls to a portion of phone numbers imported into the ElevenLabs Agent Platform are failing. We are currently working to isolate the root cause and restore full functionality.

  2. identified Jul 31, 2026, 04:00 AM UTC

    We've identified a likely contributing factor related to infrastructure resource constraints affecting SIP call routing. We're currently validating a fix.

  3. resolved Jul 31, 2026, 05:29 AM UTC

    The issue has been resolved. Call routing is now fully restored, and we're assessing follow-ups to improve proactive alerting and prevent recurrence.

  4. investigating Jul 31, 2026, 06:18 AM UTC

    Following the earlier fix, we're seeing renewed inbound call routing failures for a portion of phone numbers. We're currently investigating.

  5. identified Jul 31, 2026, 09:06 AM UTC

    Our team has identified a potential cause of the call outages and is currently validating a fix. We will share further updates as soon as we have more information.

  6. identified Jul 31, 2026, 11:12 AM UTC

    Calls should be back to normal for the EU and India residencies. The US residency may still experience some downtime, but our team is working to resolve the issue. In the meantime, the immediate workaround is to remove the affected number and re-add it, if possible.

  7. identified Jul 31, 2026, 01:01 PM UTC

    Our team is still actively working to restore all calls and phone numbers to their normal working state.

  8. identified Jul 31, 2026, 02:33 PM UTC

    We have identified the root cause of the failed SIP calls and prepared a fix.

  9. identified Jul 31, 2026, 06:02 PM UTC

    Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.

  10. resolved Jul 31, 2026, 07:00 PM UTC

    After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.

Read the full incident report →

Minor July 17, 2026 Conversation History Not Showing Recent Calls (EU Residency) - All Conversation are appearing with a delay 44m Conversations

Started Jul 17, 2026, 08:37 AM UTC· resolved Jul 17, 2026, 09:22 AM UTC

  1. investigating Jul 17, 2026, 08:37 AM UTC

    Conversations are not appearing in Conversation History, making it difficult to view or track recent calls.

  2. monitoring Jul 17, 2026, 09:05 AM UTC

    We have fixed the issue, all the conversations should become visible. We are monitoring the situation.

  3. resolved Jul 17, 2026, 09:22 AM UTC

    The issue has been resolved. All the previous conversations should be visible now.

Read the full incident report →

Minor July 14, 2026 Speech Engine Conversation Failures 9h 56m Conversations

Started Jul 14, 2026, 11:52 AM UTC· resolved Jul 14, 2026, 09:48 PM UTC

  1. identified Jul 14, 2026, 11:52 AM UTC

    We've identified a recent release that is causing Speech Engine conversations to fail. We are currently working to address the issue.

  2. resolved Jul 14, 2026, 09:48 PM UTC

    We've taken steps to mitigate the Speech Engine failures and have confirmed that performance has returned to baseline.

Read the full incident report →

Minor July 9, 2026 WhatsApp outbound message failures 5h 1m Integrations

Started Jul 09, 2026, 05:33 PM UTC· resolved Jul 09, 2026, 10:34 PM UTC

  1. identified Jul 09, 2026, 05:33 PM UTC

    Customers using WhatsApp to initiate outbound messages will see failed conversations. We've identified the problem and a fix is being rolled out.

  2. resolved Jul 09, 2026, 10:34 PM UTC

    The fix has been released. Outbound WhatsApp messaging is operating normally.

Read the full incident report →

Minor July 8, 2026 Increased Error Rate in US Region – UI, Conversations, Quality, Speech to Text and 6 more

Started Jul 08, 2026, 05:04 PM UTC· resolved Jul 08, 2026, 05:04 PM UTC

  1. resolved Jul 08, 2026, 05:04 PM UTC

    We experienced an increased error rate across multiple services between 17:04 UTC to 17:13 UTC on July 8th in the US region. We are investigating why this happened to prevent recurrence.

Read the full incident report →

Minor July 7, 2026 Image and Video Generation Errors 1h 33m ElevenCreative

Started Jul 07, 2026, 01:39 PM UTC· resolved Jul 07, 2026, 03:13 PM UTC

  1. investigating Jul 07, 2026, 01:39 PM UTC

    We are experiencing an increased error rate for generating images and videos. This will impact all services that rely on image and video generation, including Flows and Templates. We are looking into this and will post updates as they become available.

  2. resolved Jul 07, 2026, 03:13 PM UTC

    We have implemented a fix for the heightened image and video generation error rate. We have not seen any further issues after implementing the fix.

Read the full incident report →

Minor June 25, 2026 Agent Tool Creation and Update Does not Save 2h 9m UI

Started Jun 25, 2026, 02:54 PM UTC· resolved Jun 25, 2026, 05:04 PM UTC

  1. identified Jun 25, 2026, 02:54 PM UTC

    Currently, creating and updating agent tools when the tool has the Post, Put, and Patch methods in the tool configuration does not allow the tool to save. Our engineers have identified the core issue and are currently working to implement a fix.

  2. resolved Jun 25, 2026, 05:04 PM UTC

    Our engineers were able to push a fix to resolve the failure to save when editing or creating Agent tools that include the Put, Patch, or Post methods in their configuration. We have validated that the tools are now able to be saved, and confirm full resolution.

Read the full incident report →