Aurelian - Notice history

We are observing broad recovery. We will continue to monitor for regressions from Twilio or AWS' side and update accordingly.

We are seeing signs of recovery from Twilio and AWS and are gradually reintroducing traffic to the AI agent.

AI Call Handling has been restored to normal functionality.

We are observing significant signs of recovery from AWS and Twilio. We are beginning to route traffic back to our AI and monitoring to ensure full functionality has been restored.

AWS indicates that they have identified the cause and are working on a fix. We are continuing to monitor and will provide additional updates as they become available. Calls are continuing to be redirected directly to the center.

We are continuing to monitor Twilio for updates. It appears there is a major AWS outage that is the source of the issues. We will provide updates as Twilio and AWS make them available. Calls are continuing to be directly passed through to the center.

Twilio has confirmed they are experiencing elevated error rates on their APIs. We believe our kill switch should be working as intended and calls should be transferring through to the center. Please text me directly if you are experiencing any active connectivity issues at 908-938-2970 - James

Summary:

From 10:16 PST to 10:46 PST, a subset of calls experienced an issue where Aurelian's AI could not properly "hear" the caller. Our internal systems alerted us to this issue around 10:28 PST and we were able to quickly identify the misbehaving service and recover it. We observed the system fully recover by 10:46 PST.

As follow up, Aurelian will review our failover mechanisms to automatically recover from similar events, and will implement failsafes to better detect and transfer callers that this occurs to.