Our monitoring systems have detected a potential issue with One Console Voice SIP Domain regional pages. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

[in progress] Customers trying access SIP Domains details created on au1 and ie1 regions are facing an error that prevents the details from being displayed on OneConsole. We expect to provide another update in 1 hour or as soon as more information becomes available.

Our monitoring systems have detected a potential issue with a small percentage of text to speech messages could be dropped. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

We're seeing failures on text-to-speech, using Google Standard model are intermittently failing. We expect to provide another update in 1 hours or as soon as more information becomes available.

Text-to-speech using Google Standard model are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

Our monitoring systems have detected a potential issue with Conversation intelligence v2 Dynamo db failures. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

Some customers experienced issues retrieving transcripts between 15:04 and 15:46 UTC due to an issue with one of our Transcript Store services, this is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

Our monitoring systems have detected a potential issue with Credit cards will not be charged for PAYG. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

Our engineering team has identified an issue affecting customer low balance notifications and the automatic balance recharge feature. We are actively working to deploy a fix. We will provide an update in 1 hour, or sooner if additional information becomes available.

We are still investigating an issue affecting customer low balance notifications and the automatic balance recharge feature. We are actively working to deploy a fix. We will provide an update in 2 hours, or sooner if additional information becomes available.

Our engineering team has identified an issue affecting customer low balance notifications and the automatic balance recharge feature. We are actively working to deploy a fix. We will provide an update in 1 hour, or sooner if additional information becomes available.

Our engineers have implemented a fix and we are now seeing billing processing as expected. We are monitoring system performance and will provide another update in 2 hours or as soon as more information becomes available.

Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 2 hours or as soon as more information becomes available.

Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 1 hour or as soon as more information becomes available.

[in progress] Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 4 hours or as soon as more information becomes available.

Few customers may have experienced failures in Messaging Insights between May 7, 2026 23:45 UTC and May 8, 2026 00:20 UTC, caused by a AWS outage. The impact has been mitigated.

Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available.

We are continuing to work on a fix for this issue.

Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

Our monitoring systems have detected a potential issue with Flex. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

We are currently investigating a service disruption that is causing SIP registration failures with 503/32008 errors on iOS Bria Softphone, while the same configurations work on PC and Android devices. The current workaround is to use a PC or Android device for SIP registration. We expect to provide another update in 2 hours or as soon as more information becomes available.

Our monitoring systems have detected a potential issue with the Phone Numbers API. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

We are currently investigating elevated latency for Twilio Phone Numbers API search. Customer may experience timeouts when searching for numbers via api. Our engineering team is actively working on the issue, and we will provide another update in 1 hour or as soon as more information becomes available.

Searches performed via the Twilio Phone Numbers API are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

Twilio WhatsApp was degraded for 61 minutes between 4:30AM and 5:31AM Pacific Time on 04/30/1990. During this period of time customers may have experienced a delay in message delivery and an increase in 63012 errors in Twilio. The issue has now been resolved.