Resolved -
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.
Oct 21, 00:15 BST
Update -
Twilio 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 Twilio's services have recovered however we are experiencing some service disruptions due to the AWS outage affecting the US-1 Region.
Recovery is progressing, and Twilio 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.
Oct 20, 23:33 BST
Update -
Twilio 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 Twilio's services have recovered however they are experiencing some service disruptions due to the AWS outage affecting the US-1 Region.
Recovery is progressing, and Twilio 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.
Oct 20, 22:38 BST
Update -
Twilio 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 their services have recovered however we are experiencing some service disruptions due to the AWS outage affecting the US-1 Region.
Recovery is progressing, and Twilio 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 remains impacted, with continued latency errors and invocation failures. Twilio 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.
Oct 20, 21:24 BST
Update -
Twilio 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.
Twilio 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. Twilio 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.
Oct 20, 20:42 BST
Update -
Twilio 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. Twilio's 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. Twilio 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.
Oct 20, 18:54 BST
Update -
Twilio 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. Twilio 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 affected include Programmable Voice, Flex & Task Router, Studio, Functions, and Assets, with varying degrees of recovery. Programmable Messaging is fully operational. Requests with a Twilio success code are queued for delivery upon recovery, while those with failure codes need resending post-restoration. Twilio anticipates 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.
Oct 20, 18:20 BST
Update -
Twilio 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, Twilio incident response team still has all hands on deck working on remediation.Twilio 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.
Oct 20, 16:42 BST
Update -
Twilio 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.
Oct 20, 15:31 BST
Identified -
Twilio are seeing partial recovery and is scaling systems to handle the influx of traffic. Programmable Messaging and Programmable Voice are fully recovered. However, Twilio 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.
Twilio have activated their incident response team and has all hands on deck working on remediation. They are partnering directly with AWS on the incident and have also escalated to their leadership. At this time, Twilio 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.
Oct 20, 13:59 BST
Update -
Twilio are seeing partial recovery and are scaling systems to handle the influx of traffic. However they 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.
Twilio have activated their incident response team and have all hands on deck working on remediation. Twilio are partnering directly with AWS on the incident and have also escalated to their leadership. At this time Twilio 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.
Oct 20, 11:52 BST
Update -
Twilio are seeing partial recovery and are scaling systems to handle the influx of traffic. However they 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. Twilio have activated their incident response team and have all hands on deck working on remediation. They are partnering directly with AWS on the incident and have also escalated to their leadership. At this time Twilio 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.
Oct 20, 11:29 BST
Update -
Twilio at this time are experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. Twilio have activated their incident response team and have all hands on deck working on remediation. Twilio are partnering directly with AWS on the incident and have also escalated to their leadership. At this time Twilio 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.
Oct 20, 09:45 BST
Update -
Twilio at this time are experiencing outages across multiple product lines due to an ongoing AWS incident( https://health.aws.amazon.com/health/status ) with their US1 Region. Twilio have activated their incident response team and have all hands on deck working on remediation. Twilio are partnering directly with AWS on the incident and have also escalated to their leadership. At this time Twilio 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.
Oct 20, 09:15 BST
Update -
We are continuing to investigate this issue.
Oct 20, 08:37 BST
Update -
Twilio are currently investigating elevated latency and timeout errors for Twilio Rest API, impacting the Multiple Twilio services. Their 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.
Oct 20, 08:33 BST
Investigating -
Twilio are currently investigating an elevated rate of HTTP 500 errors . Their engineers are working on the issue, and we will provide another update in 1 hour or as soon as more information becomes available
Oct 20, 08:23 BST