Incoming Call Routing is not working due to a Twilio outage

Following the completion of our monitoring period, we performed a post-incident analysis and found that a small subset of customers experienced failed SMS and delayed voice notifications due to queuing issues at our primary provider (between 06:52 and 09:22 UTC). This prevented our automatic failover from triggering, as notifications remained queued rather than failing immediately. Our incident response team has ensured that all notifications of pending alerts were processed successfully. All services are now fully operational and stable. No further issues have been detected. Thank you for your patience throughout this incident.

We have completed our monitoring period and confirmed that Incoming Call Routing is stable and functioning as expected. No further issues have been detected, and all services are now fully operational. Thank you for your patience throughout this incident.

As of now, call routing functionality has been restored and is working again. We are currently monitoring the service for stability over the next 30 minutes and will provide further updates if necessary. Thank you for your patience as we ensure full recovery.

We have identified that Incoming Call Routing is currently unavailable because our provider, Twilio, is experiencing a major outage (https://status.twilio.com) due to an ongoing AWS incident (https://health.aws.amazon.com/health/status). This means users are unable to route incoming calls at this time. We are closely monitoring Twilio and AWS updates and will restore full service as soon as the upstream issue is resolved. We apologize for the inconvenience and appreciate your patience.

Important Outbound voice alert notifications are not affected.