Elevated Errors Affecting Multiple Products

All Twilio services impacted by the AWS outage affecting the US-1 Region have recovered and are operating as intended. This incident has been resolved.

We are observing recovery with the AWS outage affecting the US-1 Region and multiple Twilio services including Programmable Voice, Flex & TaskRouter, Studio, Programmable Messaging, WhatsApp, SendGrid / Marketing Campaigns, Verify, Lookup, Serverless Functions & Assets, and Event Streams.

We will be monitoring all services to ensure a full recovery and provide another update in 30 minutes or as soon as more information becomes available.

We continue seeing continued improvement across most products; however, AWS is still performing remediation actions, and intermittent errors may continue until their work is fully complete. The majority of our services have recovered however we are experiencing some service disruptions due to the AWS outage affecting the US-1 Region.

Recovery is progressing, and we are seeing improvement across most services.
Programmable Voice, Flex & TaskRouter, Studio, Programmable Messaging, WhatsApp, SendGrid / Marketing Campaigns, Verify, Lookup, Serverless Functions & Assets, and Event Streams have largely recovered, though occasional transient errors may still occur.

Twilio teams continue to work closely with AWS to address remaining connectivity and capacity issues and are monitoring the situation closely. We will provide another update within 60 minutes or as soon as additional information becomes available.

We are seeing continued improvement across most products; however, AWS is still performing remediation actions, and intermittent errors may continue until their work is fully complete. The majority of our services have recovered however we are experiencing some service disruptions due to the AWS outage affecting the US-1 Region.
Recovery is progressing, and we are seeing improvement across most services. Programmable Voice, Flex & TaskRouter, Studio, Programmable Messaging, WhatsApp, SendGrid / Marketing Campaigns, Verify, Lookup, Serverless Functions & Assets, and Event Streams have largely recovered, though occasional transient errors may still occur.
PSTN remains impacted, with continued latency errors when connecting calls.
Requests with a Twilio success code remain queued for delivery upon recovery, while those that resulted in failure codes will need to be resent once services are fully restored. We do not anticipate any data loss once recovery is complete. Twilio teams continue to work closely with AWS to address remaining connectivity and capacity issues and are monitoring the situation closely. We will provide another update within 60 minutes or as soon as additional information becomes available.

We are seeing continued improvement across most products; however, AWS is still performing remediation actions, and intermittent errors may continue until their work is fully complete. The majority of our services have recovered, however we are experiencing some service disruptions due to the AWS outage affecting the US-1 Region.

Recovery is progressing, and we are seeing improvement across most services. Programmable Voice, Flex & TaskRouter, Studio, Programmable Messaging, WhatsApp, SendGrid / Marketing Campaigns, Verify, and Lookup have largely recovered, though occasional transient errors may still occur.

Serverless – Functions and assets remains impacted, with continued latency errors and invocation failures. Event Streams is also facing delays in the delivery of some events. We are actively monitoring this service and working to resolve the issues.

Requests with a Twilio success code remain queued for delivery upon recovery, while those that resulted in failure codes will need to be resent once services are fully restored. We do not anticipate any data loss once recovery is complete. Twilio teams continue to work closely with AWS to address remaining connectivity and capacity issues and are monitoring the situation closely. We will provide another update within 60 minutes or as soon as additional information becomes available.

We continue to experience service disruptions due to the AWS outage affecting the US-1 Region. While recovery is well underway, full restoration is still in progress. Twilio teams are working closely with AWS to resolve remaining connectivity and capacity issues and to ensure ongoing stability across all regions.

We are seeing continued improvement across most products; however, AWS is still performing remediation actions, and intermittent errors may continue until their work is fully complete.

Key services impacted include Functions and Assets, which continue to experience invocation failures. Programmable Voice, Flex & TaskRouter, Studio, Programmable Messaging, and WhatsApp have largely recovered but may still encounter occasional transient errors. SendGrid / Marketing Campaigns customers may continue to see intermittent delays or errors when sending or managing campaigns. Verify traffic remains partially impacted, with a small portion (~0.1%) returning HTTP 503 errors and elevated latency. Lookup is recovering, but still shows increased latency.

Requests with a Twilio success code remain queued for delivery upon recovery, while those that resulted in failure codes will need to be resent once services are fully restored. We do not anticipate data loss once recovery is complete. Twilio has scaled systems to service current loads and continues to monitor the situation closely. We will provide an update within 60 minutes or as soon as more information becomes available.

We continue to experience service disruptions due to the AWS update affecting the US-1 Region. While recovery is underway, full restoration is still in progress. Our teams are working closely with AWS to resolve connectivity and stability issues. The impact extends to cross-region networking and US1 east, causing intermittent performance degradation.

Key services impacted include Programmable Voice, Flex & TaskRouter, Studio, Functions, Assets, and Programmable Messaging, with varying degrees of recovery. For WhatsApp, a small number of MMS messages are experiencing delays, while non-MMS traffic appears to be functional and delivering on time. Requests with a Twilio success code are queued for delivery upon recovery, while those with failure codes need resending post-restoration. We anticipate no data loss once recovery is achieved. Twilio has scaled systems to service current loads and continues to monitor the situations. We will provide an update within 60 minutes or as soon as we have more information.

We continue to experience service disruptions due to the AWS update affecting the US-1 Region. While recovery is underway, full restoration is still in progress. Our teams are working closely with AWS to resolve connectivity and stability issues. The impact extends to cross-region networking and US1 east, causing intermittent performance degradation.

Key services impacted include Programmable Voice, Flex & TaskRouter, Studio, Functions, Assets, and Programmable Messaging, with varying degrees of recovery. For WhatsApp, a small number of MMS messages are experiencing delays, while non-MMS traffic appears to be functional and delivering on time. Requests with a Twilio success code are queued for delivery upon recovery, while those with failure codes need resending post-restoration. We anticipate no data loss once recovery is achieved. Twilio has scaled systems to service current loads and continues to monitor the situations. We will provide an update within 60 minutes or as soon as we have more information.

We continue to experience service disruptions due to the AWS update affecting the US-1 Region. While recovery is underway, full restoration is still in progress. Our teams are working closely with AWS to resolve connectivity and capacity issues. The impact extends to cross-region networking and US1 east, causing intermittent performance degradation.

Key services impacted include Programmable Voice, Flex & Task Router, Studio, Functions, Assets, and Programmable Messaging with varying degrees of recovery. Requests with a Twilio success code are queued for delivery upon recovery, while those with failure codes need resending post-restoration. We anticipate no data loss once recovery is achieved. Twilio has scaled systems to service current loads and continues to monitor the situations. We will provide an update within 60 minutes or as soon as we have more information.

We are still experiencing outages across multiple product lines due to an ongoing AWS incident (https://health.aws.amazon.com/health/status ) with their US1 Region. AWS has confirmed EC2 is impacted as well.

Our incident response team still has all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

We are still experiencing outages across multiple product lines due to an ongoing AWS incident (https://health.aws.amazon.com/health/status ) with their US1 Region. AWS has confirmed EC2 is impacted as well.

As mentioned earlier, our incident response team still has all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

We are continuing our investigation and have discovered Programmable Messaging - Whatsapp and RCS media are affected by the Elevated Errors Affecting Multiple Products. We will provide another update in 60 minutes or as soon as more information becomes available.

We have confirmed with AWS that they are experiencing issues, which is delaying recovery. We are working closely with AWS triage team to resolve the issue. We will provide another update in 60 minutes or as soon as more information becomes available.

We are continuing our investigation and have discovered Programmable Messaging Conversation is affected by Elevated Errors Affecting Multiple Products. We will provide another update in 60 minutes or as soon as more information becomes available.

We have confirmed with AWS that they are experiencing issues, which is delaying recovery. We are working closely with AWS triage team to resolve the issue. We will provide another update in 60 minutes or as soon as more information becomes available.

We have confirmed with AWS that they are experiencing issues, which is delaying recovery. We are working closely with AWS triage team to resolve the issue. We will provide another update in 60 minutes or as soon as more information becomes available.

We are seeing partial recovery and are scaling systems to handle the influx of traffic. Programmable Messaging and Programmable Voice are fully recovered. However we are still experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. AWS has confirmed EC2 is impacted as well.

We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

We are seeing partial recovery and are scaling systems to handle the influx of traffic. Programmable Messaging and Programmable Voice are fully recovered. However we are still experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. AWS has confirmed EC2 is impacted as well.

We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

We are seeing partial recovery and are scaling systems to handle the influx of traffic. However we are still experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. AWS has confirmed EC2 is impacted as well.

We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

We are seeing partial recovery and are scaling systems to handle the influx of traffic. However we are still experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. AWS has confirmed EC2 is impacted as well.

We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

We are seeing partial recovery and are scaling systems to handle the influx of traffic. However we are still experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. AWS has confirmed EC2 is impacted as well.

We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

We are seeing partial recovery and are scaling systems to handle the influx of traffic. However we are still experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

At this time we are experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

At this time we are experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 60 minutes or as soon as more information becomes available.

At this time we are experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. We have activated our incident response team and have all hands on deck working on remediation. We are partnering directly with AWS on the incident and have also escalated to their leadership. At this time we do not recommend trying to take any failover action to alternative Regions. We will provide another update in 30 minutes or as soon as more information becomes available.

We are currently investigating elevated latency and timeout errors for Twilio Rest API, impacting the Multiple Twilio services. Our engineering team is actively working on the issue, and we will provide another update in 60 minutes or as soon as more information becomes available.