Posh AI incident

Voice Assistants Degraded Performance

Minor Resolved View vendor source →

Posh AI experienced a minor incident on February 29, 2024 affecting Voice Assistants, lasting 13h 26m. The incident has been resolved; the full update timeline is below.

Started
Feb 29, 2024, 01:19 PM UTC
Resolved
Mar 01, 2024, 02:46 AM UTC
Duration
13h 26m
Detected by Pingoru
Feb 29, 2024, 01:19 PM UTC

Affected components

Voice Assistants

Update timeline

  1. investigating Feb 29, 2024, 01:19 PM UTC

    Voice Assistants are experiencing issues where the bot is cutting itself off without voice input from the caller, particularly in the intro message (start intent). This is not happening on every call nor for every bot, but many are impacted. We are investigating this.

  2. identified Feb 29, 2024, 02:10 PM UTC

    The issue has been identified and we are awaiting support from our partner, Twilio. We know they are investigating as they've confirmed that with us, and we should hear from them again in ~20 minutes with an update.

  3. identified Feb 29, 2024, 02:56 PM UTC

    We have been in active conversation with Twilio for 20 minutes. Still investigating a fix.

  4. identified Feb 29, 2024, 05:10 PM UTC

    Twilio has escalated this issue internally, we continue to actively engage with Twilio and expect another update from their engineering team in approximately 30 minutes.

  5. identified Feb 29, 2024, 07:00 PM UTC

    Twilio continues to investigate and has provided Posh a potential workaround that we are actively implementing.

  6. identified Feb 29, 2024, 10:23 PM UTC

    We tested a fix earlier, but unfortunately that did not resolve the issue. Posh is actively engaged with Twilio to continue investigating and will be throughout the evening. We will continue to provide updates as information becomes available.

  7. monitoring Mar 01, 2024, 12:43 AM UTC

    We have seen very few errors in the last 40 minutes. We are continuing to monitor the issue and work with Twilio.

  8. resolved Mar 01, 2024, 02:46 AM UTC

    We haven't seen any further issues - last issue we observed was 3 hours ago. We are resolving this incident now, and we will continue working with Twilio to better understand the cause and how to prevent reoccurrence.